Projects That Take Weeks: How to Plan One Without Losing It
The move. The job hunt. The course you signed up for. Not one task and not one day, and that is exactly why it stalls.
The move. The job hunt. The course you enrolled on in January. The kitchen you started.
It is not one task, and it will not be finished in one day. It has fifty small parts, some of which depend on other people, and it has already been stalled for three weeks at a step you cannot quite name.
Planning a big project is a different job from planning a task. A task needs breaking down; a project needs a place to live, one visible next action, and a way to be picked up again after a gap - because with ADHD the thing that kills a multi-week project is almost never the work. It is the resuming.
A project is not a big task
Breaking a task into steps works because you do the steps now, in one sitting, while everything is still in your head.
A project spans weeks. You will put it down repeatedly, and every time you do, the context goes with it: what you had decided, who you were waiting for, why that tab is open, what "sort the thing" meant. The steps are rarely the hard part. Rebuilding the picture, over and over, is what makes it exhausting - and eventually it becomes easier not to open it at all.
So a project plan is not mainly a list of steps. It is a way of storing context for a future version of you who will remember nothing.
Give each project one page
One page per project - a note, a document, a sheet of paper. Everything about it lives there: the goal in one sentence, the milestones, the next action, who you are waiting on, and the loose notes and links you would otherwise scatter.
Not five apps and a folder of unnamed screenshots. One page you can open and understand in ninety seconds. That is the whole system, and it works because it removes the search that usually precedes the work.
Keep the project list separate from the task list
A to-do list holds actions. A project list holds a handful of names: move house, job hunt, course, kitchen.
Mixing them is what makes a task list terrifying, because "move house" cannot be ticked, so it just sits there radiating dread. Keep at most four or five live projects and let the rest be explicitly parked - and yes, that means saying out loud that three of them are not happening this month.
One next action per project, written as a physical thing
This is the single most useful line on the page. Not "sort out the insurance" but ring the number on the letter and ask what cover I have.
If the next action is vague, the project is stalled by definition - the vagueness is the stall. Whenever you put the project down, write the next action before you close the page, in enough detail that a tired version of you could act on it without thinking.
Leave a note to future you before you stop
Two lines, every time you stop working: where I got to, what I decided, what is next.
This is the highest-value habit in the whole article, because it is the missing context that makes resuming so expensive. Novelists talk about stopping mid-sentence so the next session has an obvious entry point; it works for the same reason here. Sixty seconds of writing saves twenty minutes of archaeology, and it is the difference between a project that pauses and a project that dies.
Milestones with dates, not a schedule
Do not build a plan with forty dated steps. It will be wrong by Tuesday and abandoning it will feel like failing the project.
Instead pick three or four milestones - flat found, notice given, boxes packed, keys handed over - and give each a rough date, working backwards from the deadline if there is one, which is where backward planning earns its place. Milestones survive a chaotic fortnight; a detailed schedule does not.
Track what you are waiting on
Half of any project is sitting with other people: the quote, the reply, the reference, the approval.
Those items are not stalled by you, but they will disappear if they are not written down, and then reappear as a crisis a month later. Keep a short waiting-for list on the same page, with dates, and chase from that rather than from memory.
Book the project, not the intention
"I'll work on it this week" is not a plan. Two hours on Wednesday morning is.
Put it in the calendar as a block with a defined next action attached, since a booked slot with an unclear task will be lost to something urgent. And book the review of it too - ten minutes in your weekly review to reread the page, update the next action and check the waiting-for list, is what keeps a project alive between sessions.
Parking is a legitimate move
Some projects should stop for now, and doing that explicitly is very different from letting them rot.
Write the note - paused until March, next action: ring the builder - and take it off the live list. An explicitly parked project costs nothing. A silently abandoned one keeps charging you every time you remember it, which is the same reason finishing or dropping things deliberately matters more than it sounds.
The short version
Multi-week projects fail at the resuming, not the doing. Give each one a single page, keep the project list separate from the task list, cap it at four or five live projects, write one physical next action, and leave a two-line note to future you every single time you stop. Milestones with rough dates rather than a schedule, a waiting-for list for everything sitting with other people, a booked block and a ten-minute weekly reread - and park the rest out loud.
Read more
Frequently asked questions
Why do big projects stall even when I know what to do?
Because a project spans weeks, so you put it down repeatedly, and each time the context goes with it - what you had decided, who you were waiting for, what a vague step actually meant. The work is rarely the hard part; rebuilding the picture over and over is, and eventually it becomes easier not to open the project at all. That is why a project plan is mainly a way of storing context, not a list of steps.
How do I plan a project that will take several weeks?
Give it one page holding everything: the goal in a sentence, three or four milestones with rough dates, one concrete next action, a waiting-for list and the loose notes. Keep it separate from your daily to-do list, cap yourself at four or five live projects, book an actual block for the work rather than an intention, and reread the page for ten minutes each week to update the next action.
What is the single most useful habit for long projects?
Leaving a two-line note to your future self before you stop: where you got to, what you decided, what is next. Resuming is the expensive part, and sixty seconds of writing saves twenty minutes of working out where you were. It is the difference between a project that pauses and a project that quietly dies.
How many projects should I have going at once?
Four or five live ones at most, and everything else explicitly parked with a note saying when you will look at it again and what the next action will be. An explicitly parked project costs nothing; a silently abandoned one keeps charging you attention every time you remember it. Saying out loud that three projects are not happening this month is a plan, not a failure.
