Long Projects at Work with ADHD: Turning a Quarter into Weeks
Three-month deadlines read as no deadline to an ADHD brain. Dated milestones, the ugly-draft rule, weekly demos and getting through the last 10 per cent.
The project was assigned in the first week of the quarter. It is due in the last. For nine weeks it sat in your task list as one line, and for nine weeks you did other things, because other things were due Tuesday. Now there are three weeks left, the thing is enormous, and the panic that finally gets you moving is also making you sloppy.
ADHD and long-term projects at work are a bad match by default. A deadline that is far away is, to an ADHD brain, not a deadline. It is a rumour. The urgency that drives attention does not arrive until the end, and by then the project needs more hours than the calendar has.
The fix is not discipline. It is converting one three-month deadline into twelve one-week deadlines, each with something visible at the end of it. Here is how.
Why three-month deadlines feel like no deadline
Time blindness is the usual explanation and it is accurate: distant dates do not register as real, so twelve weeks away and never are the same distance. There is a second mechanism that matters more for projects. ADHD attention follows interest, urgency, novelty and challenge. A long project has novelty for about a week, then nothing until the urgency arrives at the end. The middle is a desert.
Big projects also hide their first step. Build the onboarding program is not a task; it is a wish. Nobody can start a wish, so it waits behind every small task that has a clear first move. Our post on time blindness and why deadlines are difficult covers the first mechanism. Everything below is about manufacturing the urgency, novelty and first steps that the project does not supply on its own.
Milestones with dates, owners and a visible tracker
Spend the first two hours of any long project on planning, before you do anything that feels like work. The plan is the project; the rest is typing.
- Write the finished thing in one sentence, as if describing it to the person who will receive it. If you cannot, the project is not defined, and that is a question for your manager now, not in week eleven.
- Work backwards from the deadline and list the five to eight things that must be true along the way. Those are milestones. Each gets a date, and the dates are spread evenly, not bunched at the end.
- Give every milestone an owner, even when every owner is you. If any depend on other people, email them this week with the date. Their lateness is now visible instead of absorbed.
- Put the milestones somewhere you will see without opening anything: a wall, a whiteboard, a pinned note at the top of your task tool. A tracker you have to open is a tracker you will not open.
- Book the time. Each milestone gets calendar blocks in the week before its date. Unbooked work is work that will be done at midnight.
The milestones are the point. Each one is a small deadline close enough to feel real, and each one produces something you can show.
The first ugly draft rule
The single biggest cause of a stalled project is trying to make the first version good. Many people with ADHD are perfectionists in the specific sense that starting badly feels intolerable, so they do not start. The rule: the first version of everything is allowed to be bad, and it is due in the first week.
An ugly draft of a report is a document with every heading and one rough sentence under each. An ugly draft of a presentation is a deck of titled slides with no content. An ugly draft of a system is a sketch on paper. None of these take more than an hour, and all of them turn a wish into an object that can be improved.
Once the ugly draft exists, every later session is editing, and editing is easier to start than creating. If a week passes and there is still no ugly draft, that is the moment to ask for help rather than to try harder. Our answer on what therapy for ADHD does about procrastination that feels immovable describes what that help looks like.
Weekly demo to someone, even if it is yourself
Milestones give you dates. A demo gives the dates teeth. Every week, at a fixed time, you show someone what exists so far. Not a status update. The actual thing: the draft, the deck, the spreadsheet, the prototype.
- Best: your manager or the person who will receive the project. Fifteen minutes on Friday afternoon. They get early sight of problems, you get a deadline that arrives weekly.
- Good: a colleague who is also on a long project. You demo to each other. Nobody wants to show an empty file to a peer.
- Acceptable: yourself, on camera. Record a two-minute walkthrough of this week's progress and save it. It sounds silly and it works, because explaining the thing out loud exposes what is missing.
- Keep the demo even when there is little to show. Showing nothing is uncomfortable, and that discomfort is the mechanism.
The demo also produces a weekly record of progress, which is the material for your next performance review, and a trail of early feedback that stops a project drifting in a direction nobody wanted.
Handling the mid-project boredom cliff
Somewhere around week five, the novelty is gone, the deadline is still far, the interesting problems are solved and what remains is the grind. This is where most long projects quietly die. Expect it, name it, and plan for it in advance.
- Reintroduce novelty on purpose. Change where you work on it, switch tools, work on it with someone, or start a different section than the obvious next one.
- Shorten the loop. For two weeks, make the milestones daily rather than weekly and the demos to yourself every evening.
- Pair the boring section with something you want. The tedious data-cleaning block happens at the good coffee place.
- Rotate. Keep one small, satisfying side task available for when the project is unbearable, with a timer so it stays a break rather than becoming the new project.
- Tell someone the cliff has arrived. Saying it out loud makes it a known project phase rather than evidence that you are failing.
Finishing: the last 10 per cent and the handover, and this week
The last ten per cent of a project is formatting, proofreading, the summary nobody reads, the handover notes and the sending. It is boring, it is unavoidable and it takes longer than it looks. Many people with ADHD get to ninety-five per cent and stop, because the interesting work is done and finishing feels like admin. Treat the last ten per cent as its own milestone with its own date, booked for a full day, a week before the real deadline.
Make a finishing checklist once and reuse it: final read-through out loud, numbers checked against source, file named properly, handover note with what is done and what is open, sent to the right people, and the calendar block for follow-up questions. Then stop. Done beats perfect, and perfect is what week twelve looks like at 2 a.m.
For this week, if a long project is sitting in your list as one line: write the one-sentence description, set five dated milestones on a wall, produce the ugly draft in one hour, and book the first Friday demo. If you are mid-project and stalled, see the struggle with task initiation and procrastination for the restart.
This article is for educational purposes only and is not medical advice, diagnosis, or treatment. Always consult a licensed healthcare professional about your individual situation. If you are in crisis or thinking about self-harm, call or text 9-8-8, Canada’s Suicide Crisis Helpline, at any time.
Finding Focus uses AI tools to help research and draft some articles. Every article is edited and fact-checked by the Finding Focus team before publication. See our editorial and medical review policy.
