How to finish big projects with ADHD: a worked breakdown
Define what done means, map the essential dependencies, and choose a small deliverable. Includes a worked report example and a restart-note template.
Name what finished means, map what it depends on, and choose one piece you can complete next. A project needs enough planning to expose missing inputs and review time. You do not need to decide every future work session before starting the first piece.
Why a big project can stall
- No obvious first step. "Launch the website" or "write the thesis" names a result without a first step. With no clear first action, starting stalls at the size of the whole thing.
- Feedback is far away. If nobody will see the work for weeks, you may have little indication of whether it is useful yet. A draft shared at an agreed checkpoint can give you something to respond to sooner.
- The finish keeps changing. “Make it better” has no stopping point. Without an agreed result, another round of polishing can look as necessary as the last.
- Context is missing when you return. Finding the latest draft, remembering an open question, or locating a review comment can consume the time you meant to spend working.
These are possible obstacles, not an explanation of how every ADHD brain works. The useful change depends on which one you are facing.
Define a finished result
Get specific about what finished looks like before you start the work. "The report is sent to my manager and the deck is approved" is concrete; "make progress on the report" is not. A number can be the picture too, like "the site is live and taking sign-ups." Donna calls this a success picture, the anchor everything else hangs from.
Check the result with anyone who accepts the work. If the report needs approval, “draft written” and “report finished” are different milestones. Keep the actual delivery date visible; backward deadline planning helps you allow time for the steps between them.
Map the essentials, then choose one piece
Make a short map of the required deliverables and their dependencies before detailing today's work. Here is an illustrative report project. The review window must be agreed with the reviewer before relying on it.
| Required piece | What must be available first | How you know it is complete |
|---|---|---|
| Checked figures | Current cost records and last quarter's figures | Each total has been checked against its source. |
| Draft explanation | Checked figures and the report requirements | Required sections explain the changes, with source links. |
| Review | A draft ready for the agreed reviewer | Comments or approval have been received. |
| Final report | Review decisions and any corrections | Checked PDF delivered to the project owner. |
This map reveals work you cannot skip without changing the agreement. It also lets you choose a piece that is ready to begin. If the figures are unavailable, requesting them may be the next task; drafting a confident explanation would be premature.
One piece worked through
For this example, choose “check the software-cost figures” as the next piece. Its completion criterion is specific: compare both quarter totals with the source records and leave links beside them. It does not include writing the report or redesigning its charts.
The first action is opening the current cost records. If you cannot access them, ask the owner for access before reserving time to compare totals. Once the figures are checked, you have an input the draft actually needs, rather than a vague note that you “worked on the report.”
| Within this piece | Outside this piece |
|---|---|
| Check the two software totals and record the source links. | Explain every category, redesign charts, or finalize the report. |
If the work reveals an error that affects the report, flag it. A scope boundary tells you when to raise a new problem; it is not a reason to ignore one.
Leave a restart note
Before stopping, leave enough context for the next attempt. This example makes the remaining uncertainty visible:
Last completed: checked this quarter's software total.
Next action: open last quarter's cost sheet and compare the software line.
Waiting on: confirmation that the renewal belongs in this quarter.
Recheck before continuing: whether the reviewer can still respond Thursday.
Copy a blank version if useful:
Last completed: ___
Next action and where to find it: ___
Waiting on: ___
Date, input, or decision to recheck: ___
After a longer pause, check whether the deadline, requirements, or inputs changed before following the old note. A return can be free of a streak penalty while still requiring a new agreement about delivery.
When a piece grows or stalls
The piece has become several pieces
Compare the work with its completion criterion. If checking totals now requires resolving missing records, name that dependency separately. Decide what can be finished with the available information and what needs an answer. Do not silently remove required work to keep the piece small.
A reviewer is blocking the next step
Ask for a response time and explain what depends on it. You might be able to work on an independent section while waiting. If there is no independent work, raise the effect on the delivery date instead of repeatedly checking for a reply.
Polishing never ends
Return to the agreed requirements. Is a necessary point missing, or are you choosing between two acceptable phrasings? Send a draft for review when it meets the agreed draft standard. If putting the explanation into words is the obstacle, the writing guide shows a rough note becoming a draft without pretending its placeholders are finished claims.
How Donna supports the process
You can describe the finished result to Donna and ask for a small commitment toward it. Donna uses Cycles for short commitments of tasks toward a goal, with a review of what moved. Within that work, you can ask for one next task sized to the time and energy you share.
There is no breakable streak to repair in Donna. Keep external deadlines and review agreements in your plan, and tell Donna what changed when you return. Its suggestions still need to be checked against the project's real requirements.
For the next attempt, choose a piece that has its inputs, give it a clear finish, and name the first action. If an input is missing, finding out when it will arrive is useful project work too.