2026-10-13 · updated 2026-10-14

Time-blocking for chaos goblins: a flexible system for ADHD and real life

Classic time-blocking advice goes like this: plan every minute of your day on the calendar, then follow the plan. It works great for people whose days behave. For the rest of us, the plan dies at 9:40am when a meeting runs long, and then the whole calendar feels like a list of things you failed to do.

So here’s the version built for chaos: blocks that bend instead of break.

TL;DR: Block themes instead of specific tasks, leave about 30% of the day unscheduled, multiply every estimate by 1.5, move blown-up blocks instead of deleting them, and spend five minutes each evening redrafting tomorrow.

Why time-blocking works at all

Two reasons, both well supported.

1. It turns intentions into plans with a when and a where. Psychologists call these implementation intentions (“At 10am at my desk, I’ll draft the report”), and across many studies they reliably increase follow-through compared to just intending to do something.
2. It shows you the real math. A to-do list has infinite room. A calendar has 24 hours. Blocking things out exposes the moment you’ve signed up for 14 hours of work in an 8-hour day, before 4pm exposes it for you.

The problem isn’t time-blocking. It’s rigid time-blocking.

The planning fallacy is coming for you

People consistently underestimate how long their own tasks will take, even when they know their past tasks ran over. This is called the planning fallacy, and it’s one of the most replicated findings in the research on planning. With ADHD, add time blindness on top: a weaker felt sense of how much time has passed or is left.

That means a calendar packed edge to edge is guaranteed to fail. Not because you’re bad at this, but because the plan was physically impossible.

The flexible system

1. Block themes, not tasks

Instead of “9:00 to 9:45: reply to Sam’s email,” block “9:00 to 10:30: Admin.” Inside the theme, you choose the specific task when you get there, from a short list.

Theme blocks survive reality better. If the specific task you planned turns out to be blocked (waiting on someone, missing info), you can grab another task with the same flavor instead of losing the whole block.

Useful themes for most people:

• Deep work: the one hard thing. Writing, coding, studying, designing.
• Admin: email, messages, forms, bills.
• Meetings and calls: cluster them if you control your calendar.
• Errands and life: the dentist, groceries, that package.
• Recovery: lunch, a walk, actually nothing. This is a block, not a gap.

2. Leave 30% unscheduled

Treat about a third of your working day as buffer. It’s not lazy, it’s load-bearing. Buffer absorbs the meeting that ran long, the surprise request, the task that took twice as long, and the 20 minutes you spent staring at the wall before starting.

If 30% feels like way too much, try it for a week and count how often you used it. Most people use all of it.

3. Estimate, then multiply by 1.5

Write down how long you think a task will take, then add half again. A 40-minute task gets a 60-minute block. Over time, compare your estimates to what actually happened and adjust your multiplier. Some people land on 1.25, some (hi) land on 2.

4. Make deep work the first block you protect

Your hardest task gets the time of day when your brain works best, which for many people is the morning, but not for everyone. Know your peak and guard it. Put the phone in another room for that block (here’s how to nerf your phone so it stops ambushing you).

If starting is the hard part, try a body-doubled block: work alongside someone on a quiet call. Body doubling is weirdly effective for getting past the first ten minutes.

5. When a block blows up, move it, don’t delete it

This is the rule that makes the whole thing chaos-proof. When something eats your 2pm deep work block, drag it to the next open slot, or tomorrow. Deleting it tells your brain the task evaporated. Moving it keeps it real and visible.

If you’re moving the same block for the third day in a row, that’s information. The task is probably too big or too vague. Break it into a first step that takes 25 minutes or less.

6. The 5-minute evening reset

At the end of each day:

1. Look at what actually happened. No judgment. Just data.
2. Move anything unfinished to a new slot.
3. Draft tomorrow: pick the one deep-work task, place your theme blocks, keep the buffer.
4. Dump stray thoughts onto your list so they stop looping. A quick 2-minute triage turns that chaos into a short list.

The calendar is a draft, not a contract. You’re allowed to redraft it as many times as the day demands.

ADHD-specific tweaks

• Make time visible. A visual timer (the kind that shows a shrinking colored disk) or a clock in your eyeline helps with time blindness more than a calendar alone.
• Add transition blocks. Switching tasks costs ADHD brains extra. A 10-minute “landing” block between contexts (refill water, write down where you left off) makes the next block easier to start.
• Set start alarms, not just reminders. A calendar notification that says “Deep work in 5” plus one that says “Start now” beats a single nudge you’ll swipe away.
• Use color and keep it simple. One color per theme. If your system needs a manual, it’s too complicated to survive a bad week.
• Plan for low-energy days. Keep a short list of “low battery” tasks (filing, tidying, easy replies) so a bad brain day still has a useful block in it.

A sample flexible day

Roughly 30% of that day is buffer and recovery. That’s not slack. That’s the reason the rest of the plan actually happens.

Common failure modes

• Over-scheduling Monday. Monday-you is optimistic. Friday-you is real. Plan Monday like it’s Friday.
• Blocking every minute. If there’s no buffer, the first surprise breaks everything.
• Skipping the reset. Without the evening redraft, the calendar drifts out of sync with reality within two days, and you stop trusting it.
• Treating a moved block as failure. It isn’t. Moving blocks is the system working.

Start small: tomorrow, block just one deep-work session and one buffer. Add more once that feels normal.