Time blocking with ADHD: why it breaks and a looser version
Classic time blocking, where every hour of the day gets a specific task, tends to break for ADHD because task length is hard to estimate and one overrun collapses every block after it. A looser version works better: give each task an earliest start time and a deadline instead of an exact slot, so the day has structure without demanding precision it cannot deliver.
What time blocking promises
Time blocking sounds reasonable on paper: assign each task a slot, 9 to 9:30 for email, 9:30 to 10:15 for the report, 10:15 to 10:30 for a break, and the day runs like a schedule instead of a scramble. For some people it works exactly like that. For a lot of ADHD adults, it works for about ninety minutes before the first task runs long, and then every block after it is wrong, which turns a tool meant to reduce decision making into a source of constant, visible failure.
Why the blocks collapse
The core assumption behind time blocking is that you can estimate how long a task will take. That estimate is exactly the skill many ADHD adults struggle with most, not from lack of trying but because the internal sense of time passing is unreliable. A task estimated at twenty minutes might take fifty, or might take eight, and either way the tidy grid of blocks stops matching reality almost immediately. Watching your own schedule fall apart in real time, block by block, over the course of a morning is demoralizing in a specific way that no-schedule chaos actually is not.
The looser version: windows instead of slots
Instead of assigning each task an exact start and end time, give it two boundaries: an earliest time it can start, and a deadline by which it needs to be done. Between those two points, the task can happen whenever it happens. This keeps the useful part of time blocking, which is that some tasks should not start before a certain point and some genuinely need to be done by a certain point, while dropping the part that breaks, which is pretending you know exactly how long each task will take.
A worked morning under each system
Classic time blocking: 8:00 to 8:30 answer emails, 8:30 to 9:15 write the proposal draft, 9:15 to 9:30 quick break, 9:30 to 10:00 call the supplier. Emails take until 8:50. Now the proposal draft, the break, and the call are all pushed, and by 10:00 the schedule bears no resemblance to what is written down.
Window version: emails have no formal window since they can happen anytime before noon. The proposal draft has an earliest start of 8:00, since you want it done before other things pile up, and a deadline of noon, since it is due at 1. The supplier call has to happen between 9 and 11, since that is the supplier's business hours. When emails run long, nothing else breaks, because nothing else was pinned to an exact minute. The call still has to happen in its window, and the proposal still has to be done by noon, but the specific order and pacing within those constraints stays flexible.
The hidden cost of watching a schedule fail in real time
Beyond the practical disruption, there is a second cost to classic time blocking that gets less attention: the emotional toll of watching a plan visibly collapse block by block. Each missed block is a small, repeated piece of evidence that the plan, and by extension you, failed at something, even though the real cause was an unrealistic time estimate rather than a lack of effort. A looser structure avoids generating that steady stream of small failures, since there is rarely a specific minute to have missed in the first place.
When to still use a hard time
Not every task should get a loose window. A task with a genuinely fixed external time, a meeting someone else scheduled, a flight, a call the other party set, should keep that exact time, since it is not actually negotiable. The looseness applies to tasks you control the timing of, not tasks where the timing is set by the world.
This pairs closely with how much buffer time to add between tasks and appointments, since a window with too little slack between it and the next commitment recreates the same collapse problem in miniature. If the underlying issue is really about matching tasks to your energy rather than the clock, planning around energy instead of only the clock takes that further. And the Pomodoro-style version of this same estimation problem is covered in why the Pomodoro Technique fails some ADHD brains.
Setting a window instead of a slot
Any task in Drifta can carry this exact structure: an earliest start time, a deadline, or both, set on the task's edit screen. The task stays quiet until its window opens, and reminders only get firmer once the deadline is close or has passed, which is a closer match to how a real, imprecise day actually unfolds than a rigid hour by hour grid ever was.
Common questions
Is time blocking ever worth trying with ADHD?
Yes, for a small number of anchor events, like a meeting or an appointment, where the time is fixed by someone else. Applying it to every task in the day is where it usually breaks, since most personal tasks do not actually have a fixed external time.
What is the biggest single reason time blocking fails?
Time estimation. A block sized for twenty minutes that actually takes fifty pushes every following block later, and by the third overrun the whole schedule is fiction. Loose windows absorb that kind of overrun instead of being destroyed by it.
What should replace the blocks that get abandoned?
A rough order instead of exact times: this, then this, then this, with real times attached only to tasks that truly have one, like a scheduled call. Order without precision survives a slower-than-planned morning far better than an exact schedule does.
This article shares practical organizing ideas. It is not medical advice. For diagnosis or treatment questions, talk with a qualified clinician.