How does "Set and enforce a WIP (Work In Progress) limit" work?

Starting new work is cognitively easier and more rewarding than completing difficult existing work — new tasks offer freshness, autonomy, and an initial hit of progress. Without a WIP limit, this preference for starting over finishing creates a growing queue of half-done work, increasing cognitive load (Zeigarnik effect) and reducing throughput (more items in progress but fewer completing). A WIP limit forces the harder but more productive choice: finish before starting. In queuing theory, limiting queue depth directly improves average completion time (Little’s Law).

How does "Pull work rather than having it pushed to you" work?

Push-based systems (email inbox, meeting invites, Slack messages) deposit work at a rate controlled by others. Pull-based systems (checking a backlog when a slot opens) give the worker control over the intake rate. Personal Kanban structures work as pull: you take a card from the To Do column when Doing has space. This is a practical application of autonomy theory — control over work intake is associated with lower stress and higher intrinsic motivation — and prevents the reactive overload that characterizes push-dominated work.

How does "Use the Done column to learn about your work patterns" work?

Completed work contains signal about how you actually work — which tasks cluster, which take longer than expected, which types consistently stall before completion. Without a visible record, this signal is lost: memory selectively distorts toward how work felt rather than how long it took. The Done column is a data archive that enables the kind of calibrated self-knowledge that makes future planning more accurate.

How does "Watch for cards that stay in Doing without moving" work?

Stalled work cards are diagnostic data: they indicate a blocker (missing information, dependency, unclear next step, avoidance) that is invisible when work is managed mentally. The visual board makes stalls obvious without requiring active tracking. A well-functioning Kanban board has consistent left-to-right flow; a card that stops moving is a system signal that something needs to change — adding more cards to Doing in response is exactly the wrong reaction.

How does "Only put tasks on the board that you’ve explicitly decided to do" work?

A Kanban board loses its function when the To Do column becomes an undifferentiated backlog of everything you might possibly do. A genuine To Do column contains only committed work — tasks you have decided are worth completing in the near term. This distinction mirrors the essentialism principle: having fewer items in the queue is a sign of better prioritization, not of having less work. A short, committed To Do column exerts appropriate urgency; an infinite backlog is just anxiety without direction.

Benson & Barry

How does Personal Kanban work and does it actually help you manage work in progress?

Visualize your work, limit what’s in progress, and let the system show you where you’re stuck

Short answer

Personal Kanban (Jim Benson & Tonianne DeMaria Barry) adapts the industrial lean-production Kanban board for individual and small-team use. Its two rules are: visualize your work and limit work in progress (WIP). The Kanban method in manufacturing has strong evidence; the personal adaptation is a practitioner system with mechanistic grounding in cognitive load and attention research but limited formal trials in personal productivity contexts.

Kanban originated in Toyota’s production system as a signal card that controlled the flow of work through a manufacturing line. Jim Benson and Tonianne DeMaria Barry adapted its core insight — that limiting work in progress dramatically improves flow and completion rate — to personal and knowledge work. The system requires only three columns (To Do, Doing, Done) and one constraint (WIP limit). Below are the core practices, each with the mechanism and an honest read on the evidence.

The practices (6)

Why it works

Invisible work creates two cognitive problems: you cannot accurately assess how much is in progress, and you cannot see which tasks are actually advancing. A visual board externalizes both. The simple left-to-right flow (not yet started → in progress → complete) maps onto temporal progress in a way that makes queues, bottlenecks, and completion rates immediately apparent without requiring analysis. This is an application of distributed cognition: the board thinks for you.

How to do it

1Create three columns: To Do (backlog), Doing (active work), Done (completed).
2Write each task on a separate card or sticky note — one task per card.
3Move cards left to right as work progresses; never move a card backward.

Evidence

Mechanistic

Visualization of work state is a core element of both Kanban in manufacturing (where it has strong industrial evidence for throughput improvement) and lean management. Distributed cognition research supports the value of offloading cognitive representations onto physical artifacts. Direct RCTs on personal kanban boards are not available.

Honest caveat: Industrial Kanban evidence does not transfer cleanly to personal knowledge work — production lines have stable, measurable tasks; personal work is more variable and ambiguous.

— Hutchins (1995), Cognition in the Wild (distributed cognition foundation)

Common mistake: Creating a board with too many columns (Analysis, Design, Review, Testing, Done) that adds complexity without proportional clarity — three columns is not a starting point, it is the optimal default.

Go deeper on this practice →

Practice this with IX Coach

Reading about a practice changes nothing on its own. IX Coach turns these into a guided, adaptive routine — discerning where you are in real time and walking the practice with you, session after session.

Start with IX Coach →