How I Break Down a Big Project With ADHD (When 'Just Break It Down' Doesn't Work)

There's a specific project on my hard drive right now that I've "started" about eleven times. Each start looks identical: I open a blank doc, type the project name as a heading, stare at it for a while, feel the whole thing press down on me at once, and close the tab. Then I tell myself I'll plan it properly this weekend, when I have time to sit down and really think it through. The weekend arrives. The doc is still just a heading.

If you have ADHD, you know this isn't a time problem. I had the time. I had the skills to do every individual piece. What I couldn't do was turn the big, shapeless thing into a list of moves small enough to actually make. And every productivity article I read gave me the same advice — break it into smaller steps! — which is a bit like telling someone who's drowning to simply swim.

So this is the workflow I use instead. Not the generic version. The one that accounts for why breaking a project down is itself the part that keeps breaking.

Why "Just Break It Down" Doesn't Work for ADHD

Here's the trap nobody names: deciding the steps is a second project.

"Break it into smaller steps" treats the breaking-down as free — a quick, mechanical thing you do before the real work. But deciding what the steps even are requires exactly the skills ADHD makes unreliable. You have to hold the whole project in your head, imagine the path from here to done, judge what comes first, and sequence it all — while a working memory that drops things mid-thought tries to keep thirty moving parts in the air at once.

That's not a motivation gap. ADDitude's overview of executive function disorder in adults describes it plainly: the hallmark is trouble "analyzing, planning, organizing, scheduling, and completing tasks." Planning and organizing are the breakdown. So "just break it down" asks the one skill that's impaired to quietly do all the work before you're allowed to begin — and then acts surprised when you freeze.

This is why the advice backfires. You sit down to "break it into steps," the planning itself overwhelms you, and now you've failed at the easy part before you even reached the task. The overwhelm doesn't come from the project being hard. It comes from trying to hold the entire unstructured thing in a brain that can't hold it. Fix the holding problem and the project stops looking like a cliff.

The Rule: Plan the First Domino, Not the Whole Chain

The reframe that finally unstuck me: you don't need the plan. You need the next move.

For years I thought a project required a complete, correct map before I could start — every step laid out in the right order, no gaps. That belief is a procrastination engine, because building a perfect map of something you've never done is impossible, so you never finish mapping, so you never start. The map becomes the avoidance.

But you don't walk a project by seeing the whole route. You walk it by taking a step you can actually take right now, which reveals the next one. You only ever need the first domino close enough to flick. So I stopped trying to decompose the entire project in one sitting and started doing just enough to find a single, enterable first action. Everything below is in service of that — getting one real move in front of me, and getting the other twenty-nine out of my face until it's their turn.

How I Break Down a Project, Step by Step

This takes about ten minutes, and I do it as a timed session — not as an open-ended "sit and think about the project," which is just the staring-at-the-heading trap with extra steps.

1. Get it out of your head and onto the screen

Before anything gets ordered or judged, I empty the project out of my head into one place — every piece, task, worry, and "oh, and I'll need to…" — in whatever messy order they fall out. Not a clean outline. A brain dump.

This is the load-bearing step, and it's the one people skip. The overwhelm is largely your working memory buckling under the weight of holding the whole project at once; the second it's written down, your brain can stop white-knuckling it and start looking at it. You cannot organize a thing you're simultaneously trying not to forget. Dump first, think second.

2. Cut until the first step is embarrassingly small

Now I pick the one thing that could plausibly come first and I shrink it until it's almost insulting.

Here's my test: if the step still makes me flinch, it's not a step — it's a smaller project. "Write the introduction" makes me flinch, so it's out. "Open the doc and type three bad sentences I'll delete later" does not. "Do the taxes" is a project; "find last year's return and put it on the desk" is a step. The goal isn't a reasonable first action. It's one so small that refusing to do it would feel ridiculous. You're not trying to make progress yet — you're trying to make starting undeniable. Once you've got a step that tiny, actually beginning it is a separate skill, and task paralysis has its own playbook for the moment you're staring at even the small thing and still can't move.

3. Sequence by what you can enter, not the "right" order

Every planning template wants you to order tasks logically — research, then outline, then draft, then edit. That's fine for brains that run on logic. Mine runs on momentum.

So I don't ask "what's the correct first step?" I ask "which of these could I start in the next five minutes?" and I put that first, even if it's technically step four. Order is overrated; entry is everything. A logically perfect sequence you can't begin is worth less than a slightly wrong one that gets you moving, because once you're moving, the real order usually reveals itself anyway. Pick the domino nearest your hand, not the one the textbook says goes first.

4. Show one step. Hide the rest.

This is the part that keeps the breakdown from re-overwhelming me the second I finish it. A list of thirty steps is just the original cliff rendered in bullet points — look at all of it and the same dread comes right back.

So the full breakdown goes into my task manager and then out of sight. Focusmo connects to the seven apps I might keep that list in — Things 3, Todoist, TickTick, Apple Reminders, Microsoft To Do, Google Tasks, or Obsidian — so the plan lives somewhere real but closed. What stays in front of me is exactly one line: the current step. Everything ADHD knows about object permanence says the hidden steps won't haunt you — and that's the point. You'll meet them one at a time, when each becomes the only thing on screen.

5. Put each step in a container

A step with no edges will still expand to fill the whole day or evaporate entirely. So I give the current one a container: a fixed length and a witness.

A personal project usually has no boss, no deadline, and no one waiting — which sounds like freedom and functions like quicksand, because nothing outside you says go now or that's enough. So I manufacture the pressure the project doesn't supply. I start a focus session for the single step — a visible countdown, say twenty-five minutes — and I keep a check-in scheduled so that partway in, Focusmo asks what I'm actually working on. The timer gives the step an edge; the check-in is the gentle external nudge that a brain running on borrowed accountability needs when no one else is in the room. If you want a container shaped around your own focus patterns rather than a generic block, the free ADHD Focus Planner turns a few questions into a schedule built around when you actually focus.

6. Re-break on contact

The breakdown you make at the start is wrong. Not a little wrong — wrong in the way every plan is wrong once it meets reality, because you planned it from the one position where you knew the least about the work: before you'd done any of it.

So I don't try to get the whole map right up front. I break down only the next chunk, work it, and when I hit the fuzzy part further along, I stop and re-break that with everything I've since learned. Planning becomes a thing I do repeatedly in small doses, not one heroic session I have to nail. This also kills the perfectionism that used to masquerade as diligence — the endless "let me just plan it properly first" that was really fear wearing a planner's outfit. A rough plan you're walking beats a perfect one you're still drawing.

The Part Nobody Warns You About: Finishing

Breaking a project down gets you moving, but a project isn't a start — it's a start plus a long, unglamorous middle. The ADHD risk shifts around step seven: the novelty wears off, a shinier idea shows up, and the half-built thing joins the graveyard of other half-built things. Getting through the messy middle to actually finished is its own skill, and the breakdown feeds it — because when the "I've made no progress" feeling hits (it will, around the middle, every time), you have a receipt.

That's the quiet benefit of working this way on a Mac. Focusmo tracks my activity locally, so when the voice insists the project is going nowhere, I look at the record instead of trusting the feeling: the sessions logged, the steps closed, the thing visibly further along than it was Monday. A time-blind, novelty-hungry brain is a terrible judge of its own progress. The log is a better one, and seeing real movement is often the only thing that carries a project across the dull middle to done.

The Takeaway

"Just break it into smaller steps" fails for ADHD because the breaking-down is the hard part — it leans on exactly the planning and organizing that executive dysfunction makes unreliable, so the advice hands the broken tool the job and walks away. The fix isn't trying harder to plan. It's planning less, and differently: dump the project out of your head so your working memory can stop straining, cut the first step until it's too small to refuse, sequence by what you can enter rather than what's "correct," hide everything but the current move, give that move a timer and a check-in, and re-break the next chunk only when you reach it.

You don't need to see the whole staircase. You need one step small enough to take, and a way to keep the other twenty-nine from staring at you while you take it.

If you want the container part handled for you — focus sessions to box each step, check-ins so a solo project still has a witness, task-manager integrations to park the breakdown out of sight, and local activity tracking so you can see the project actually moving — try Focusmo. It's a free Mac menu-bar app built for brains that can do every piece of a project but freeze at the whole.