Time Blocking vs Kanban | Plan the Order, Not the Hour

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 how long something will take, and estimates are the part of planning most of us get wrong most often. Nothing personal in that: a task you expected to fill thirty minutes fills an hour, and every block after it has quietly moved.

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.

A stricter version of the same idea, with one card in Doing and a brain dump in front of it, is in low-stimulation computing.

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.

When time blocking is the right answer

A piece that only argues one side is not much use to somebody deciding. Blocks genuinely work, and here is where.

When the hours are not yours anyway. Teaching, clinics, court, shift work, support rotas: if the day is already cut into fixed pieces by other people, a calendar is simply an accurate description of it. There is nothing to predict.

When the work is the same size every time. A radiologist reading scans, a translator working by the page, anyone whose unit of work has a known length. The estimate problem disappears when you have done the same thing four hundred times.

When the enemy is starting, not switching. Some people do not lose the day to interruptions, they lose it to not beginning. A block at nine with a name on it is a commitment in a way that a list is not, and for that person the calendar is doing real work.

When you are protecting time from other people. A block on a shared calendar is a fence. It stops the eleven o'clock meeting from landing on the two hours you needed, which no personal board can do.

The honest summary: blocks are good at defending time and bad at predicting it. Most people need both, and the split in the next section is the one that survives a normal week.

The day a board handles and a calendar does not

Four situations where the difference is not theoretical.

The morning that starts badly. A calendar day that begins an hour late is wrong in every row, and fixing it is twenty minutes of work about work. A board is simply pulled from later.

The two-hour meeting that appears at nine. The blocks it eats have to be moved somewhere. The cards do not move at all; there are just fewer of them today.

The task that turns out to be three tasks. A block cannot grow without pushing everything after it. A card splits into three and the board tells the truth about what is left.

The day with no energy for the hard thing. A calendar insists you write the report from ten to twelve. A board lets you pull something that fits the state you are actually in, which is how the day ends with work done rather than with an hour of staring.

The pattern is the same in all four: a calendar makes a promise about the future, a board makes a decision in the present.

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.