A Kanban board only helps if it changes what you do next. Most personal boards fail the same way: the Doing column fills with six half-started tasks, stalled items sit beside live ones, and cards like “Website” never move because they were never tasks in the first place.
Four mechanics solve this, and none of them is another column. Set a hard limit of one or two cards in Doing, give blocked work its own Waiting For column, size every card between 30 minutes and four hours, and track two numbers, throughput and cycle time, to decide how much to commit to each week.
Why To Do, Doing, Done is not enough
Kanban began on Toyota’s factory floor, where a card signalled that a station needed more parts. Nothing was produced until the signal arrived. Jim Benson adapted the idea for individuals as Personal Kanban and reduced it to two rules: visualize your work and limit your work in progress.
The second rule does the heavy lifting. A board without a limit is a to-do list with extra steps, because nothing stops you from starting a new card every time the current one gets hard.
The cost of those open cards is real. Sophie Leroy’s research on attention residue found that switching away from an unfinished task leaves part of your attention stuck on it, which lowers performance on the next task. Every card sitting in Doing is one you are likely to flip back to, which is the same trap described in the multitasking myth.
Set up the board in five steps
- Empty everything into a Backlog. Pull tasks from your notebook, inbox flags and sticky notes into one column. A quick brain dump works well here. Do not size or sort yet.
- Create five columns: Backlog, Ready, Doing, Waiting For, Done. Ready holds what you have committed to this week; Backlog holds everything else.
- Write the WIP limit on the Doing header. Start at 1 if your work is mostly long solo tasks. Use 2 if your work has natural pauses, such as a file exporting or a draft out for a quick check. Benson recommends treating the number as something you calibrate by noticing when you start to feel scattered, then adjusting.
- Size each card as it enters Ready. Every card gets a verb and a finish line, and should take 30 minutes to four hours. Personal Kanban’s own guidance favours multi-hour blocks rather than multi-day projects.
- Add two dates to every card: the day it entered Doing and the day it reached Done. These are all you need for the metrics later.
Column and WIP limit reference
| Column | Purpose | Recommended WIP limit | Exit criteria to move the card |
|---|---|---|---|
| Backlog | Every possible task, unsorted | None | Chosen at the weekly refill and split into 30-minute to 4-hour cards |
| Ready | This week’s commitments, in priority order | Your average weekly throughput (often 6 to 12) | A slot opens in Doing; take the top card |
| Doing | The work you are actively touching today | 1 or 2 | Finish line met, or you cannot take the next action |
| Waiting For | Cards blocked by another person or event | Soft cap of about 5 | The reply or input arrives; card returns to the top of Ready |
| Done | Finished cards with start and end dates | None | Logged and archived at the weekly refill |
Sizing cards: the 30-minute to 4-hour rule
A card that hides a week of work breaks the WIP limit without looking like it. Benson calls oversized cards hidden WIP: one card in Doing labelled “Q3 report” is really five or six tasks you are juggling in your head.
Split by finish line, not by topic. “Q3 report” becomes “Pull sales figures into template (1 hr)”, “Draft regional summary (2 hr)”, “Build three charts (1.5 hr)” and “Send draft to finance for figure check (30 min)”. Each one either is done or is not.
Cards under 30 minutes clutter the board. Do them on the spot, or bundle them into one card such as “Admin block: six replies and two invoices (45 min)”.
The Waiting For column keeps blocked work out of Doing
When a card stalls because you need someone else, it should leave Doing immediately. Benson introduced a dedicated column he calls The Pen for exactly this, so stalled tasks stop occupying the slots meant for active work.
Three rules make the column useful rather than a graveyard:
- Write who and when on the card. “Legal sign-off: Priya, chase Thursday” turns the column into a follow-up list you can scan in seconds.
- Waiting cards do not count against your Doing limit, but more than five means you have a dependency problem worth raising with the people involved, not a personal focus problem.
- Unblocked cards go to the top of Ready, not straight into Doing. Do not abandon the card you are working on just because a reply landed.
Genuine emergencies get one Expedite row above Doing with a limit of one. If it fills more than once or twice a week, the interruptions are part of your normal workload and belong in your Ready count.
Track throughput and cycle time
Two numbers turn the board from a picture into a forecast. Personal Kanban defines throughput, cycle time and lead time as the core measures of personal capacity:
- Throughput: cards finished per week.
- Cycle time: days from entering Doing to reaching Done.
- Lead time: days from first landing on the board to Done.
Take a freelance oral historian who logs four weeks of Done cards: 7, 9, 6 and 10, an average of 8. From then on, Ready gets filled to 8 cards on Monday, not 15. Most cycle times sit at one to two days, but three cards took six days or more. All three were “transcribe and index recording” cards, which were really full-day jobs and now get split into one card per hour of tape.
Check one more number daily: how long your current Doing card has been there, which the Kanban Guide calls work item age. If it is older than your usual cycle time, the card is either too big or secretly blocked.
Kanban, a to-do list or time blocking?
| Your situation | Best fit | Why |
|---|---|---|
| Requests arrive unpredictably all week | Kanban | You pull the next card when ready instead of rebuilding a schedule |
| Calendar is mostly fixed meetings and deadlines | Time blocking, with Kanban feeding it | Blocks protect the hours; the board decides which card fills them |
| Several projects depend on other people | Kanban with Waiting For | Blocked work stays visible without stalling everything else |
| A short list of errands for one day | Plain list | Columns and limits add overhead for no gain |
The two methods combine well: time blocking reserves a 9:00 to 11:30 slot, and the top card in Ready is what you work on inside it.
Board habits that quietly undo the limits
- Doing creeps to four cards “because they’re all small”. Either they are one card or they belong in Ready. Return to the posted limit and follow the Kanban slogan: stop starting, start finishing.
- Waiting For becomes a graveyard. Any card past its chase date gets a follow-up today. Anything waiting over ten days gets escalated or deleted.
- Ready holds 30 cards. That is a second backlog. Cap it at your average throughput and push the rest back.
- Throughput drops for three weeks. Check cycle times first; a cluster of oversized cards is the usual cause.
- New requests keep jumping the queue. Show the board: “Ready has eight cards this week. Which one should come off to make room?” It makes saying no a conversation about priorities.
Weekly refill checklist
Run this once a week, ideally at the same time. If you already plan your week, fold it into that session.
- Count Done cards and write the number in a running log.
- Note any card with a cycle time over three days and the reason.
- Archive Done (photograph a paper board first).
- Chase or close every card in Waiting For.
- Split the next Backlog items into 30-minute to 4-hour cards.
- Fill Ready to your four-week average throughput, most important first.
- Confirm the Doing limit on the header still matches how the week felt.
1 Comment