Getting organized

How to Break Down a Big Task When Every Step Feels Overwhelming

By Interval · 12 min read

In this article

“Move house” fits comfortably on one line. The actual work doesn't. It includes dates, boxes, bookings, documents, decisions, other people, and a kettle that somehow needs to remain available until the last possible moment.

To break down a big task, define the finished result, divide it into a few meaningful stages, identify dependencies, and turn the next stage into concrete actions. You don't need to map every small step immediately. Detail the near-term work and leave later stages broad until you know more.

A bright room with bookshelves and desks by the windows
Photo by Clay Banks on Unsplash · License

This guide uses a house move as a worked example. The same approach can help with a report, an application, a room reset, or an event. The aim is a usable project map, not a list so long that it becomes another source of overwhelm.

Decide whether you're looking at a task or a project

A task is something you can act on directly. A project requires several actions to reach an outcome. “Email the moving company for availability” is a task. “Move house” is a project, even if your app calls both of them tasks.

When a project sits on a daily list as one checkbox, you may keep avoiding it because the next action isn't specified. You may also work on it for hours and feel you've done nothing because the single checkbox remains incomplete.

The Getting Things Done workflow offers a useful distinction between clarifying an outcome and choosing the action that follows. You don't need specialist project software to separate those levels.

If your only difficulty is getting into the first action, see how to start a task. This article goes further: it helps you map the whole project enough to understand sequence, responsibility, and what finished means.

Define a finish line you can recognize

Before listing steps, write what needs to be true at the end. Avoid vague outcomes such as “be organized” or “sort everything out”. Those don't tell you when to stop.

For the move, a practical finish line might be: belongings are in the new home, essential services are arranged, keys are handed over appropriately, and the first-night essentials are accessible. Decorating every room doesn't need to be part of the same project.

For a report, finished might mean the document is checked, approved by the relevant person, and sent to the intended audience. For an application, it might include confirmation of receipt, not merely completing the form.

Check the finish line with other people when their expectations matter. A shared misunderstanding at this stage can create far more work than a missing checkbox. Ask what is required, what is optional, and who decides whether the result is acceptable.

Put the boundaries around the project

Write the deadline, major constraints, available help, and what is outside scope. These details shape the plan before you divide the work.

For a move, constraints might include access dates, building rules, transport, budget, care responsibilities, and the availability of helpers. Use actual agreements and official instructions where relevant; this example isn't a substitute for legal or tenancy advice.

Outside scope could include buying new furniture, digitizing old photos, or reorganizing every book. Those may be attractive projects, but including them can make moving feel impossible. Put them on a separate later list if you want to keep them.

Boundaries aren't a lack of ambition. They make the current promise understandable. A project that can absorb every related idea will never have a stable workload.

Divide the outcome into a few stages

Use stages that represent meaningful changes in the project. For the move, they might be arrangements, preparation, packing, moving day, and settling the essentials. Five stages are an example, not a required number.

For a written report, stages might be requirements, evidence, draft, review, and delivery. For a room reset, they might be deciding what stays, removing what doesn't, arranging storage, and putting items away.

Don't start by listing hundreds of tiny actions. First make sure the stages cover the outcome. If a stage is vague, ask what it produces. “Preparation” becomes more useful when you know it should produce a booked vehicle, packing materials, and a plan for access.

A university guide to time management can provide useful background on planning ahead. The stage-based approach here is an editorial planning tool, not a claim that a particular number of stages has been experimentally proven best.

Find the dependencies before scheduling everything

A dependency is something that needs to happen before another action can proceed. You may need confirmed access before booking transport. You may need the report's data before checking its conclusions. You may need an answer before choosing an option.

Mark only the dependencies that affect order or timing. You don't need a complex diagram for a personal project. A note such as “book after access date confirmed” can be enough.

Identify external waiting time early. Another person's response may take longer than your own action. Asking for the information now can be more important than completing a small easy task that doesn't unlock anything.

Keep your action separate from the outcome you can't control. “Request confirmation” is yours to do. “Receive confirmation” is something to track. Give the waiting item an appropriate follow-up point instead of leaving it invisible.

Turn the next stage into concrete actions

Once the broad map exists, detail the stage you're about to work on. Write actions with a verb, an object, and an endpoint. “Get organized” isn't an action. “Put the moving documents in one folder” is.

For the arrangements stage, your list might include checking the access date, asking two suitable transport providers for availability, confirming building access requirements, and agreeing who will handle which responsibilities.

Each action should be small enough to attempt in a realistic session. If “compare moving options” is still too broad, start by writing the requirements that matter: dates, amount to move, access constraints, and available budget.

The Leicestershire Partnership NHS Trust's ADHD strategies include making large tasks more manageable. Small actions can support accessibility, but they don't need to be so tiny that checking them off takes longer than doing them.

A worked project map for moving house

Here is an illustrative map, not a universal moving checklist. Adapt it to your housing, location, responsibilities, and agreements.

  1. Arrangements: confirm dates and access, choose appropriate transport, agree help, and record important contacts.
  2. Preparation: gather suitable packing materials, identify what won't move, and separate documents or items that need special handling.
  3. Packing: pack nonessential areas first, label boxes clearly, and keep daily essentials available.
  4. Moving day: follow the agreed access plan, track essential items, complete relevant handover steps, and check what remains.
  5. Essential setup: make sleeping, eating, hygiene, and necessary work or care possible before tackling decorative projects.

Now detail only the first stage. “Confirm dates” may mean reading the existing agreement and asking one unresolved question. “Choose transport” may require knowing the amount to move and the access restrictions. Those dependencies influence the order.

Packing stays broad until arrangements are clearer. You can still do a useful independent action, such as identifying a small group of unwanted items, but you don't need to invent every packing session now.

As the project progresses, the map changes. A helper becomes unavailable or the access time changes. Update the affected stage and dependencies rather than rebuilding the entire plan from scratch.

The map is useful because it shows what's next, what's waiting, and what's deliberately outside the current stage. It doesn't need to predict every detail of moving day to reduce uncertainty today.

Choose the right size for an action

An action is probably too large if you still have to make several major decisions before beginning it. It's probably too small if recording it creates more friction than it removes and you don't need the reminder.

“Pack the kitchen” may be too large for a short evening. “Pack the spare mugs and label the box” has a clearer boundary. “Pick up tape, hold tape, tear tape” is unnecessary detail for most people, though a more detailed checklist may be useful for a specific accessibility need.

Let the level of detail match the person and the situation. Familiar tasks need less explanation. New, stressful, or safety-sensitive sequences may need clearer instructions and checks.

If a step repeatedly stalls, split it at the actual obstacle. Maybe it isn't the packing that's hard; it's deciding what to keep. Create a separate decision task rather than dividing the physical action into smaller motions.

Estimate stages with uncertainty in mind

Early estimates are provisional. Use similar past work where available and name unknowns. Don't assign precise durations to unfamiliar steps simply because a scheduling tool asks for a number.

The planning fallacy research highlights why an idealized sequence can produce optimistic predictions. A project plan should include ordinary friction, waiting, checking, and transitions.

For the move, packing one cupboard can help you estimate other comparable cupboards. It won't necessarily predict how long sorting sentimental papers will take. Different types of work deserve different assumptions.

Leave space before the deadline for unresolved issues. If the schedule only works when every estimate is correct, it isn't a robust plan. Reduce scope, start an important dependency earlier, or seek help where possible.

Put only current actions into the daily plan

The project map can hold the whole outcome. Today's list should show the pieces you're actually choosing to do. Copying every future step into today's view recreates the overwhelm the breakdown was meant to reduce.

Choose actions based on consequence, dependencies, and available capacity. One request that unlocks the next stage may matter more than several easy packing tasks. Use the prioritization guide if the next stage contains too many competing actions.

Keep the broader map accessible but not constantly in front of you. You want confidence that the rest is recorded, not a reminder of the entire project every time you complete a small step.

In Interval, a project note can hold the stages while tasks represent the current actions. The notes and planning features support that arrangement. A paper project page and a short daily list can do the same job.

Track waiting and ownership

For shared work, every important action needs a clear owner. “Someone should book the van” isn't an assignment. Confirm who is handling it, what information they need, and when an update is useful.

Keep waiting items visible in a separate part of the project note. Record what was requested, from whom, and the next reasonable follow-up. You don't need to check the inbox every few minutes to prove that you're managing the dependency.

When another person completes a step, update the plan rather than continuing to work from an old assumption. Shared projects fail when different people hold different versions of the next action.

Use the team's agreed communication method where one exists. A personal planner can help you manage your responsibility, but it shouldn't silently replace the shared source of truth.

Make progress visible without counting every motion

A long project can feel static when the final outcome is still far away. Mark stage results as they become true: transport confirmed, documents gathered, draft ready for feedback, or essentials packed.

These milestones are more informative than a raw checkbox total. Completing twenty tiny tasks doesn't necessarily mean the critical dependency is resolved. Conversely, one difficult decision can move the project forward substantially.

At the end of a work session, leave a brief status note and the next action. “Spare room packed except desk drawer; next gather cables” is enough. This makes the next session easier to enter.

Research on specific plans for unfinished work provides context for why having a concrete route forward can be useful. It doesn't remove the need to revisit a plan when circumstances change.

When the breakdown itself feels overwhelming

Hide later detail and return to the stage level. You may have created too much granularity too early. Keep the next few actions visible and leave future stages as short headings.

Ask whether the project contains several separate outcomes. “Move house and redesign my life” needs boundaries. “Write the report and rebuild the department's information system” probably contains more than one project too.

If the difficulty is emotional rather than organizational, a smaller checklist may not be enough. Ask for practical support or appropriate professional help when needed. Breaking down a task is a planning aid, not a treatment for distress.

If the total scope genuinely exceeds the available time or resources, say so. No amount of decomposition makes an impossible commitment possible. The plan's value may be showing exactly where a decision about scope or support is required.

Review at useful points

Review when a stage finishes, a dependency changes, or a deadline approaches. You don't need to reorganize the whole project every time you open the planner.

Ask what is now true, what is still uncertain, and what the next stage needs. Remove obsolete steps. A plan that preserves every original assumption becomes less useful as the project teaches you more.

For ongoing responsibilities, our weekly review checklist can provide a regular checkpoint. For a short urgent project, a brief review at the end of each work period may be more appropriate.

Keep review notes concise. The purpose is to support the next decision, not document every moment. A project can be well managed without a polished administrative trail for every small action.

A reusable project breakdown template

Copy these headings into whatever you already use:

  • Finished means: the concrete outcome and any necessary acceptance criteria.
  • Deadline and constraints: dates, resources, access, and important limits.
  • Outside this project: related ideas you're not promising now.
  • Stages: a few meaningful parts of the outcome.
  • Dependencies: what needs to happen before something else can proceed.
  • Next actions: the current stage's available steps.
  • Waiting for: external responses and follow-up points.
  • Next review: when the map needs another look.

Fill in only what helps. A small project may need four lines. A complex shared project may need more detail and a more formal tool. The template is a starting structure, not a requirement to turn every errand into project management.

For your current project, begin with the finish line and the next stage. You can add detail as it becomes useful. The plan should make the work easier to enter, not require finishing the plan before touching the work.

Questions about breaking down tasks

How many subtasks should I create?

Enough to make the current work clear, not enough to describe every future motion. Start with a few stages and detail the next one. Add steps when they resolve ambiguity or help you remember a necessary sequence.

Should I plan the whole project before starting?

Understand the outcome, major dependencies, and risks first. You can often begin a safe, useful action before every later detail is known. For regulated or safety-critical work, follow the appropriate planning requirements rather than this general template.

What if the project keeps growing?

Compare new ideas with the original finish line. Add them only through a deliberate scope decision. Otherwise, keep them for later. A useful project boundary allows you to finish something without completing every related possibility.

A big task becomes more manageable when you can see both the overall route and the next small piece. You don't have to carry both in your head at once.

Sources and further reading

Get it out and get on

Because planning shouldleave you with moreheadspace, not less.