Monday morning: a sensible plan for the week. Wednesday lunchtime: the plan is a historical document. By Friday you're not even annoyed anymore; it's just what happens. And the productivity advice keeps insisting that with better planning, more discipline, a finer-grained system, next week will be different.
Let me offer the perspective of someone who planned professionally for twenty years: next week will not be different, and that's fine, because the plan's job was never what you think it was.
Two reasons the plan dies
The first killer is the planning fallacy, and it lives inside you. Humans systematically underestimate how long things take, even things they've done before, even when they know about the planning fallacy. Your Monday plan wasn't a neutral forecast; it was the best-case version of every task, stacked end to end with no allowance for friction. It was optimistic on the day it was written.
The second killer arrives from outside. A week is long enough for the world to interfere: the urgent request, the meeting that spawns three actions, the small crisis that eats Thursday. None of it was knowable on Monday, and all of it had to go somewhere, which meant on top of a plan that had budgeted for none of it. So the plan wasn't wrecked by your weakness. It was wrecked by arithmetic: optimistic estimates plus unplanned arrivals, compounding across five days. Any plan built that way dies. Yours just died on schedule.
My twist: the plan's job is to make the drift visible
Here's what two decades of programme management actually teaches about plans, and it's not how to make ones that survive. No programme plan survives. The plan's real job is to be the thing reality diverges from visibly, so you find out early, while responding is still cheap. A programme without a plan doesn't avoid drift; it just discovers the drift at the end, when nothing can be done. The plan is an instrument for detecting change, not preventing it.
Apply that to your week and everything reframes. The Monday plan "failing" by Wednesday isn't failure; it's the plan doing its one true job, telling you loudly that the week has changed shape. The mistake isn't planning. It's treating the plan as a promise, then spending the week feeling guilty about a broken promise no one could have kept. Plan in order to notice. Replan the moment you've noticed. Guilt has no role in the mechanism.
Practically, that means planning at a resolution where replanning is cheap: the week holds shape, the day holds detail (the Sunday version of this argument is here), and a blown Wednesday costs you a two-minute Thursday replan instead of a ruined week.
How ka-do handles it
Ka-do assumes the drift, structurally. The window holds the week's honest shape without pretending to schedule it hour by hour. Each morning's plan is built from that day's facts, so Wednesday's chaos is simply Thursday's input, not Thursday's shame. The zones move themselves as the days pass, which means the picture stays true through the drift; nothing has to be reconciled back to a Monday artefact. And when new work lands mid-week, it lands against a visible capacity, so you can see immediately what it displaces instead of discovering it on Friday.
What ka-do won't do is score you against Monday's plan. No burn-down of your own week, no red variance report. The plan isn't a promise here, so there's nothing to have broken.
Honesty clause: my weeks still don't go to plan. This week didn't. The difference is that the divergence now shows up Tuesday morning as information, instead of Friday evening as a verdict.
The one-line version
Your week never goes to plan because plans are optimistic and weeks are hostile. That's not the plan failing. Noticing it early is the plan working. It's also why timeboxing keeps collapsing unless the tool expects the drift instead of pretending the week will hold still.
Ka-do plans at the resolution where replanning is cheap. Try it free →