How to Break Down a Big Goal: Three Steps from Overwhelming to Startable

If “build my portfolio” has been sitting on your list for three weeks while you stare at it, the problem isn’t willpower. It’s that it isn’t a task — it’s a goal. Goals can’t be executed. Only smaller units can.

Breaking things down isn’t a grand methodology. Three steps.

Step 1 — Write the end state as a sentence

Before cutting anything, define what “done” means. What’s the end of “build my portfolio”? Something like: “a public site with six works, and the link is on my résumé.” A sentence you can judge as finished or not.

Without an end state, the pieces you cut scatter without direction — and worse, you won’t know when you’re done. (This is exactly the W and O steps of WOOP.)

Step 2 — Place three to five milestones

Put intermediate checkpoints between here and the end state. For the portfolio:

1. Six works selected
2. Write-ups finished for each work
3. Site skeleton deployed (even empty)
4. Content in, site public
5. Résumé and profiles updated with the link

The rule: each milestone must be a state you can judge as reached or not. “Design in progress” is not a milestone; “main page design locked” is. Three to five is the sweet spot — more becomes management overhead, fewer leaves the gaps overwhelming again.

Step 3 — Break down only the first milestone into tasks

This is where most people go wrong. The urge is to decompose everything at once — but you only break down the stretch to the first milestone.

“Six works selected” as executable pieces:

• Collect every past work into one list (30 min)
• Cut to twelve candidates
• Set criteria, lock six

The test for an executable piece: if reading it raises the question “so what do I actually do?”, it’s not one yet. Most good pieces fit inside half a day.

Why not plan the later milestones now? Because what you learn crossing the first stretch changes the plan for the rest. Pre-made plans mostly get thrown away, and the energy spent making disposable plans is subtracted from the energy to start. Breakdown isn’t a one-time event — it repeats at each milestone.

Common mistakes

• Decomposing everything upfront. See above. First stretch only.
• Cutting too fine. Pieces like “open laptop” turn the list itself into work. Half-day units are small enough.
• A flat pile of pieces. When fragments accumulate without structure, overwhelm returns. Every piece should visibly belong to a milestone.
• Not doing the first piece today. A breakdown is completed by execution, not by the list. Once you’ve cut it, do the smallest piece on the spot — a started project and an unstarted one are different objects entirely.

Where the structure stays visible

Holding these three layers — goal, milestones, pieces — in your head or in a flat list is harder than it sounds. With a tool that shows the layers, breaking down becomes a habit instead of overhead.

fecit, the app we’re building, carries the three layers natively: projects hold the goal, milestones under them show m/n progress automatically, and tasks split into sub-tasks you can order and branch as a graph. Open a big task and the AI can propose a sub-task breakdown to start from.

Whatever your tool: take the big thing you’ve been staring at for three weeks. One end sentence, three or four milestones, and the first piece of the first stretch — that’s enough for today.