Somewhere along the way, this became a debate with teams. Time blockers say lists are wishful thinking: a pile of intentions with no relationship to the actual hours in your day. List people say blocking is a straitjacket: a beautiful calendar that shatters at the first interruption, leaving you rearranging coloured rectangles instead of working.
Both sides are right about the other's weakness. That should have been the clue that the question was wrong.
What each one actually is
Strip the tribalism away and look at the jobs. A to-do list is a storage and truth instrument. It answers "what's on my plate?" It's complete, cheap to maintain, and honest, because everything's there. What it can't answer is "when will any of this happen?", which is why a list of forty items and a free afternoon produces choice paralysis rather than progress. The list stores; it doesn't direct.
Time blocking is a commitment instrument. It answers "what am I doing at 10am?" by welding a task to an hour. That kills choice paralysis dead (the decision was pre-made) and it's why blocking's advocates swear by it for deep work. What it can't survive is contact with reality. The 10am block dies when the 9:30 call overruns, and now the whole afternoon's rectangles are wrong, and maintaining the calendar becomes its own job. The block directs; it can't flex.
Storage that can't direct, versus direction that can't flex. If those sound familiar, they should. It's the same two-jobs split from why your to-do list makes you feel worse, showing up one level higher. These were never competing systems. They're the two halves of one.
My twist: block the day, not the week, and let the list feed it
Twenty years of programme planning taught me where each instrument earns its keep. Lists are for the week: complete, honest storage of what's in play, with dates where dates are real. Blocks are for the day, and only the day, because a day is the largest unit of time you can commit hour-by-hour without reality making a fool of you. Block a week in advance and Tuesday's disruption wrecks forty rectangles. Block this morning and the blast radius is this morning.
So the flow is: the list holds the week, and each day you pull from it. A handful of tasks, sized against the hours you actually have, sequenced into something like blocks. The list stays true all week; the blocking is disposable, rebuilt each morning in minutes, cheap to abandon at 2pm when everything changes. You get blocking's decisiveness without its fragility, and the list's honesty without its paralysis.
How ka-do handles it
This is precisely the shape of the app. The list — the 1–2 week window — is the storage and the truth. Plan My Day is the blocking half: pull today's tasks from the window, weigh them by effort against the day you've actually got (including the meetings already sitting there), and get an honest verdict on whether it fits before you start. The day gets direction; the week keeps its flexibility; and when the day blows up, you replan the day, not the fortnight.
What ka-do won't do is make you choose a religion. There's no forced daily blocking ritual, no calendar that demands every hour be accounted for, and equally no pretence that a raw list is a plan. Some days you run Plan My Day properly; some days you just work the list. Both are supported on purpose. Productivity isn't uniform, and the instruments should serve the week you're actually having.
Honesty clause: in heavy build weeks I skip the daily planning and just swim in the list, and those are, not coincidentally, my scrappiest days. The mechanism works. The operator wobbles.
The one-line version
Lists store, blocks direct, and neither does the other's job. Keep the list for the week, block only the day, and stop picking sides in a fight between two halves of the same system. That's the right tool doing timeboxing properly rather than the calendar-only version that falls apart at the first interruption.
Ka-do keeps your week in a list and plans your day in one pass. Try it free →