You have probably built a task system before. Possibly several. The notebook with the colour-coded sections. The app with the beautiful nested projects. The whiteboard that worked brilliantly for eleven days. Each collapsed the same undramatic way: a Tuesday where you didn’t open it, then a Wednesday, and by Friday looking at it felt worse than not having it at all.
That isn’t a discipline problem. It’s a design problem. Most productivity systems assume the difficult bit is deciding what to do, so they optimise for organising — folders, tags, priorities, nested subtasks. For ADHD brains the difficult bit is almost never deciding. It’s the gap between deciding and doing, and no amount of tagging closes that gap.
So let’s build the other kind. Four parts, one job each, designed for the version of you who is tired and behind and slept badly.
Why do task systems keep collapsing?
That quietly disqualifies most productivity advice. A system that mostly helps you know things is solving a problem you don’t have.
The second reason is mechanical rather than motivational. Most systems need daily upkeep to stay accurate. Skip it for three days and the system starts lying to you — tasks you already did, dates that have passed, priorities from a version of your life that no longer exists. Reading a list that lies feels awful, so you avoid opening it, so it lies more. The collapse isn’t caused by the missed Tuesday; it’s caused by what the system did with it.
Third: things genuinely disappear when you can’t see them. If a task lives inside a folder inside a project inside an app you have to remember to open, it may as well not exist. This is how working memory tends to behave in ADHD — not a filing failure, a visibility failure. A good system is mostly a machine for keeping four or five things visible.
What does a working ADHD task system actually look like?
Four parts. Build them from paper, one app, or five you already have — the parts matter more than the tools.
Part 1: capture — one place, five seconds, zero decisions
Capture is where most systems break first, because most apps make you file a thought before you can save it. Which project? What due date? By the time you’ve answered, the thought is gone and you’re doing admin.
The rule: capture must be faster than the thought is fleeting. One inbox, no categorising, no tags. It’s allowed to fill with junk — junk in a box beats gold that evaporated. Practically: a home-screen widget, a lock-screen shortcut, a pinned note, or a capture app that doesn’t make you sign in before you can type. Anything with a login screen between you and the thought is not a capture tool.
In the next 24 hours: pick one capture spot and put it on your home screen. For one day everything goes there and nothing gets sorted — you’re testing speed, not building a database.
Part 2: schedule — pick three, not twelve
Now the second list: what’s actually happening today. Three things. Not three categories — three specific, finishable things. You’re allowed to do more; you’re not allowed to plan more.
Three works because a long list stops reading as a list at all. It reads as one enormous undoable object — the exact feeling that ends in scrolling on the sofa.
Anchor those three to events rather than clock times. “Email after coffee” survives contact with reality; “email at 10:15” is a small trap, because a 2019 review found time perception is consistently altered in ADHD — the gap between “that felt like ten minutes” and the actual forty isn’t something willpower fixes. Anchoring to things that already happen (coffee, lunch, the school run, logging off) borrows structure you don’t have to generate.
In the next 24 hours: tonight, move three things — three — into a “today” list. Everything else stays in the inbox where you can’t see it.
Part 3: focus — the timer is a starting device, not a productivity tool
Here’s the reframe that makes timers useful: a timer’s job isn’t to make you efficient. It’s to make the first minute survivable by putting a wall around it. You’re not agreeing to finish the tax return — you’re agreeing to eight minutes of it, after which you’re free.
So the number matters, and 25 minutes isn’t sacred. Set it to a length you’d feel slightly silly refusing. Some days that’s twenty minutes; on bad days it’s five, and five genuinely counts. A timer you can set to whatever number actually gets you moving beats a rigid one you keep abandoning at minute three.
Second piece: somewhere to park distractions. Mid-task, your brain will produce an urgent thought about renewing your passport. Chase it and the session ends; suppress it and it keeps knocking. Write it down and carry on — parking costs four seconds, chasing costs the afternoon.
In the next 24 hours: pick one task, set a timer for a length that feels almost too easy, and stop when it goes off even if you want to keep going. Stopping while it’s still going well is what makes you willing to start tomorrow.
Part 4: reschedule — the part every system forgets
This is the part that decides whether your system is alive in a month. Not what happens when you finish a task — what happens to the ones you don’t.
Most tools mark them red, stamp them “overdue”, stack a badge count, break your streak. Do that for two weeks and the app stops being a task list and becomes a record of everything you failed at. Nobody opens that voluntarily. The undone pile needs to be neutral: still here, no colour, no counter, no guilt tax to re-engage. That’s why some task apps leave streaks and shame mechanics out on purpose — an untouched list should cost you nothing to come back to.
In the next 24 hours: find where your tool displays overdue items and turn the badge or the red off. If it won’t let you, that’s real information about the tool.
If you’d rather not assemble the four parts yourself, that’s roughly the shape Noodl was built around: a capture button and widget on the home screen, a Today list you reorder by hand, a focus timer you set from 5 to 120 minutes with a button to jot a stray thought without stopping the clock, and a Revisit bucket where anything you didn’t get to moves overnight — labelled “Ready when you are” rather than flagged red. It’s free, Android-only, works offline, and doesn’t ask for an account. It won’t make the tasks easier; nothing does. It just removes a few frictions between you and starting.
What makes a system survive a bad week?
One rule: it has to be rebuildable in sixty seconds. When it falls over, recovery should be open it, clear everything into the inbox, pick three. If recovery requires a two-hour weekly review, you won’t do the two-hour weekly review, and the system stays dead. Be sceptical of anything that only works when you’re already doing well.
And go easy on yourself about the tool churn. The average app loses about 77% of its daily users within three days of install — that’s everyone, not a personal failing. What it tells you is that activation energy is the whole ballgame. Between a powerful tool you open twice a week and a plain one you open twice a day, the plain one wins, and it isn’t close.
You’re allowed to have a system that’s mostly empty
If you’ve been carrying a quiet belief that a real system would be elaborate — nested projects, tidy tags, colour-coded contexts — put it down. Three things on a today list, a box for everything else, a timer, and a soft landing for what didn’t happen is a complete system.
You’re not bad at this. You’ve been handed tools built for brains that remember things they can’t see and start tasks they find boring, then quietly blamed yourself when those tools didn’t fit. Build the small ugly system that survives a bad week instead. It’ll still be there on the Tuesday you need it.