Time Blocking vs Kanban | Plan the Order, Not the Hour
Why a colour-coded calendar collapses by eleven o'clock, and how a board with a work-in-progress limit survives the day that went sideways.
Sunday evening, the week laid out in colours. Nine is deep work, half past ten is email, eleven is the proposal. At a quarter past nine a client calls, a server falls over, someone needs ten minutes. By eleven the plan is wreckage, and the day now carries a second load: the guilt of being behind a schedule you invented.
Time blocking was the advice for a decade. It fails for a reason that has nothing to do with discipline.
What rigid scheduling assumes
A block on a calendar is a prediction about the future, made by a person who is bad at predictions. That is not an insult, it is the estimation problem: a task you expect to take thirty minutes takes an hour, and every block after it is now wrong.
Two more costs follow.
No room for the actual day. Interruptions, a bad night's sleep, an hour when your head does not work. A schedule with no slack treats all of that as failure.
Repairing the plan becomes the job. Twenty minutes of dragging blocks around is twenty minutes of work about work, and it happens on exactly the days that were already hard.
A board pulls instead of pushing
A calendar pushes tasks into slots. A board lets you pull the next one when you are free, which is the only moment you actually know your capacity.
You decide the order, not the hour. Work sits in the first column, ranked. When you sit down, you pull the top card into the doing column and stay there until it is finished or the day interrupts you.
Interruptions cost nothing. The urgent call happens, the card stays where it is, and when you return the board is exactly as you left it. Nothing to reschedule.
A limit forces focus. Set the doing column to hold one card. That single number does more for concentration than any app feature: with one slot, starting something new means finishing or explicitly parking what you have.
Done is visible. A card moved into the last column is a thing that happened. A calendar block that has passed is only time that went by.
Three rules that make it work
The calendar is for hard edges only. Meetings, the call at two, the appointment. Things that exist whether you show up or not.
The board is for everything else. You work the cards in the gaps between the hard edges, in whatever order your energy allows.
Reminders are for deadlines, not for starts. Do not remind yourself to begin writing. Remind yourself that the form is due at five. Reminders prevent disasters; the board handles flow.
Setting it up in ten minutes
Three columns are enough: this week, doing, done. Put a limit of one on doing, or two if your work genuinely alternates.
In TaskNote, ours, so judge accordingly: the board has a card limit per column, and a global hotkey means a task that arrives mid-call gets captured without leaving the call. Anything written in a note becomes a card with a link back to where it came from, so the plan and the thinking stay connected. Fridays, clear the board and the week's pages: most of what you wrote was disposable.
The board lives on your own machine in the Windows app, so it opens instantly and works with the network off.
The short version
Stop micromanaging your future self. Keep the calendar for what is genuinely fixed, rank the rest on a board, limit what you allow yourself to be doing at once, and pull the next card when you actually have the room. The day still goes sideways; the plan no longer goes with it.
kanbanplanningfocus