Free task breakdown template: turn a big task into smaller steps

The blank task breakdown template

Copy these prompts into a note, document, or piece of paper. You can leave any field blank if it does not help the task in front of you.

• Parent task: What are you trying to get done?
• Done when: What visible result tells you this piece is complete?
• Step 1: The first concrete action.
• Step 2: The next action that becomes possible.
• Step 3: One more useful action, if you can already see it.
• Blocked by: Information, approval, material, or another person you are waiting for.
• Start now: The one step you will actually begin.
• Return note: Where you stopped and what should happen next.

Fill the template from the top down

Start with the outcome and the finish line. “Prepare the report” is the parent task; “draft sent to Sam for review” is a clearer definition of done. Then list only the actions you can already see.

Do not force yourself to map the whole project. If later steps depend on what you learn from step one, leave them open. A task breakdown should reduce uncertainty, not pretend uncertainty does not exist.

Worked example: prepare a short report

Parent task: prepare the monthly report. Done when: a draft with the agreed sections is ready for review.

A workable breakdown is short and observable. Each step should produce a result you can point to.

• Step 1: Open last month's report and duplicate the file.
• Step 2: Replace the date and reporting period.
• Step 3: Paste the current figures into the results section.
• Blocked by: final sales number from finance.
• Start now: duplicate last month's file.
• Return note: figures added; next, add the final sales number when received.

Worked example: clear a crowded kitchen counter

Parent task: clear the kitchen counter. Done when: the main work surface is available for cooking. Instead of turning the job into a whole-house organization project, keep the boundary local.

• Step 1: Throw away obvious rubbish.
• Step 2: Put dishes in the sink or dishwasher.
• Step 3: Group items that belong in another room into one basket.
• Step 4: Wipe the cleared surface.
• Start now: remove the obvious rubbish.
• Return note: counter clear; basket still needs to be put away.

Separate actions from dependencies

A hidden dependency is one of the most common reasons a step is not startable. “Submit the application” may actually require a reference number, a document from someone else, or a decision about which option to choose.

Write the dependency beside the step instead of repeatedly trying to do blocked work. If another person controls the next transition, a message asking for the missing input may be the real next action.

Know when to stop breaking the task down

Stop when the next action is specific enough to begin and small enough for the time or energy you have. You do not need to split every future step into tiny pieces before doing the first one.

If your list grows so long that it becomes harder to read than the original task, collapse it. Keep the near-term actions visible and move future ideas to a separate parking-lot note.

Turn the template into action

Once the first step is clear, begin it before adding more planning detail. When you stop, update the return note so the next session does not have to reconstruct your context.

If you would rather work through the same idea interactively, Towardly's free Next Step Builder can help you choose one action and save a simple plan without creating an account.