Sunday night you build the perfect week. Monday 9 to 11, the report. 11 to noon, email. Tuesday morning, the proposal. The calendar looks beautiful, colour-coded, not a gap in sight.
Monday at 9.20 a production issue lands. At 11 you are still on it. The report block is gone, the email block too, and by 2pm you have abandoned the whole plan and gone back to working on impulse. On Tuesday the proposal never even gets opened.
Time blocking is one of the soundest ideas in productivity. It is also one of the most fragile in practice — and the reason is not the method, it is how almost everyone applies it.
What time blocking gets right
The idea is simple: instead of keeping tasks on a list and deciding at every moment what to do, you give each important task a slot on the calendar. A meeting with yourself.
That solves three problems at once.
It removes the repeated decision. A list requires you to choose what to do every time you finish something — and choosing is tiring. A block has already chosen for you.
It protects the important from the urgent. On a list, the urgent always wins. On a calendar, the important has a reserved place the urgent has to invade to take.
It creates the cue the important does not have. The meta-analysis on "when-then" plans pooled 94 studies and found a medium-to-large effect on goal attainment just from tying the action to a moment. A block on the calendar is exactly that: "when it is 9am, then the report".
Why the Sunday plan dies on Monday
You plan the day of a person who does not exist. This mistake has a name: the planning fallacy. In a classic study, students estimated how long they would take to finish their thesis. The average estimate was 34 days; the actual time, 56. More revealing: when asked for an estimate "if everything went as badly as it possibly could", the average was 49 days — still below what actually happened. It is not that we underestimate time. It is that even our worst case is optimistic.
You fill 100% of the day. With no margin, the first 20-minute delay knocks over every following block like dominoes. The plan becomes an hourly list of failures.
You treat a block as a promise. When the 9am block does not happen, it feels like failure — and a plan that generates guilt at 9.20 is a plan abandoned by 2pm.
Interruptions do not ask permission. Research on interrupted work shows people compensate for interruptions by speeding up, at the cost of more stress and more effort. A two-hour block protects you from ordinary noise, but does not survive the interruption that demands an immediate answer — and that one always comes.
How to do time blocking that survives the week
What the calendar does not do
Time blocking solves planning. It does not solve execution, and the difference shows up at exactly 9am, when the block starts and you are in the middle of something else. The calendar does not know you are busy. It does not ask whether it can start. It does not come back at 9.15 to insist, nor move the block to 2pm when you say "not now".
That part — the one that turns a planned block into a block that happened — is still done by you, in your head, every day. It is the part that fails.
What I wanted to change
I built perfect weeks for years and abandoned almost all of them on Monday. Not because the plan was bad, but because nobody showed up at block time to say "it's now" and, if I could not, to ask "then when?".
That is the piece I wanted to put into ASB: an assistant that holds your blocks, tells you when the time has come, accepts "not now" and comes back — instead of a beautiful calendar that just watches.