How to break tasks into subtasks you can actually start
Turn a large personal task into a short sequence of clear actions, then fix the first step when you get stuck.
Updated 2026-10-07
To break a task into subtasks, describe what finished looks like, then write the actions that produce that result. A useful subtask names an action and a clear stopping point. Put background information in a note so you do not have to reread a paragraph just to find the next action.
You can use this approach on paper or in a task app. In To-Do List for Chrome, the feature overview describes subtasks, notes and due dates, with personal lists on the new-tab page. If you still need to install it, follow the Chrome new-tab setup guide.
Start with a finish line
"Get ready for the trip" can stay on a list for days because it does not identify a finished result. "Pack my bag for Friday's two-night trip" gives the task a boundary. Booking transport or planning activities can remain separate tasks.
Write one sentence that answers: what will exist or be different when this task is done? For a presentation, that might be "A slide deck ready to send for review." For a study task, it could be "Practice questions completed and mistakes marked for another attempt."
If you cannot describe completion yet, make the first subtask a decision: "Choose which chapter to review" or "Confirm what the presentation needs to cover." Planning that decision is more useful than inventing a detailed checklist around an unclear goal.
Write actions you can check off
Use a verb and an observable result. "Clothes" is a category. "Put two changes of clothes in the bag" is an action with a clear stopping point.
This illustrative packing example shows how a broad task can become a sequence. It is a sample checklist, not a tested packing recommendation for every trip.
Parent task: "Pack my bag for Friday's two-night trip."
- Check the forecast for the destination and write down any rain or cold-weather needs.
- Put two changes of clothes and sleepwear in the bag.
- Pack toiletries and any personal essentials from my own packing note.
- Put the charger and travel documents in the bag.
- Check the bag against the note and close it.
The first action supplies information for the second. The last action defines completion. Adapt the contents to your trip rather than treating this example as a universal list.
Stop dividing a step when you can start it without making another planning decision. You do not usually need separate entries for opening a cupboard, picking up a shirt and placing it in a bag. If "Pack toiletries" still leaves you unsure what to do, add the missing items to a note or make that step more specific.
Understood's guide to breaking down work also recommends making steps specific and recording where other people's input is needed. The same check applies to a personal task: identify anything you must obtain before you can continue.
Choose between a subtask, a note and a separate list
If every detail gets a checkbox, the next action can become hard to find. Choose where each piece of information belongs by asking what you need to do with it.
- Use a subtask for an action needed to finish the parent task, such as "Download the booking confirmation."
- Put supporting information in a note, such as the booking reference and the documents to bring.
- Give a different outcome its own task or list. "Plan the weekend activities" has actions separate from packing a bag.
- Use a due date for a genuine completion deadline, such as packing the bag before departure.
These are ways to organize your own information, not claims about automatic sorting. The product site describes multiple lists, subtasks, notes and due dates. You decide which structure fits the task.
A due date records a deadline. It does not establish that this extension will send a notification. If you need an alert at a particular time, arrange it in a tool that explicitly supports alerts.
Repair the first step that keeps stalling
If a subtask sits untouched, reread its wording before adding more tasks. The problem may be missing information or a decision that the action hides.
For example, "Buy a replacement charger" sounds specific, but you may not know which charger fits. Replace it with "Find the device model and required charging specification." After that, you can write the buying step with the information you need.
If you are waiting for someone, record the dependency in a note: "Waiting for the destination address." Add your own follow-up action when appropriate, such as "Ask for the address before booking transport." The list records your plan; it does not manage dependencies or contact anyone for you.
When you return to the list, read the first unfinished action and ask whether you can do it with the information and materials available. If you can, begin there. If you cannot, write the missing decision or request as the next action. You can revise the remaining subtasks as the task becomes clearer.