Personal Kanban: Two Rules That Improve How Knowledge Work Flows

From Toyota to the Individual

Taiichi Ohno developed the kanban system at Toyota as part of the Toyota Production System described in his book Toyota Production System: Beyond Large-Scale Production (Productivity Press, 1988). The original kanban was a physical card (kanban means "signboard" or "visual signal" in Japanese) that signaled a downstream process to pull work from an upstream process, a pull system that prevented overproduction by making production contingent on actual downstream demand.

Jim Benson and Tonianne DeMaria Barry adapted the principles for individual and team knowledge work in Personal Kanban: Mapping Work / Navigating Life (Modus Cooperandi Press, 2011). They stripped the system to its minimum viable form: two rules, applicable without any specialized tooling.

The Two Rules

Rule 1: Visualize your work. All tasks, commitments, and work items should be represented visibly, typically as cards on a board with at least three columns: Ready (to be done), Doing (in progress), and Done (completed). The visualization rule addresses a specific problem: invisible work. When commitments exist only in memory, their aggregate volume and the relationship between them are invisible. Making work visible shows the total load, reveals dependencies, makes progress concrete, and enables others to see and contribute to what is being tracked.

Rule 2: Limit WIP. Set an explicit maximum for how many cards can be in the Doing column at once, typically 3 to 5 for an individual. When the Doing column is full, no new work can be started until a current item is completed. This rule forces a specific behavior: completing work before starting new work. Without a WIP limit, it is possible to begin many things simultaneously and complete few of them, which is the most common failure mode of knowledge worker productivity.

The WIP limit creates productive tension. When new requests arrive, the person must either push back ("I'm at capacity; this will start when something finishes") or complete something currently in progress before accepting the new work. Both responses are healthier than the alternative: accepting the new work, adding it to a growing in-progress pile, and fragmenting attention across too many commitments.

Professional Applications

• Managing competing commitments. The most common professional failure mode personal kanban addresses is the accumulation of partially completed work: projects started but not finished, emails responded to but not resolved, commitments made and not tracked. The WIP limit prevents the accumulation by requiring explicit completion before new starts. For knowledge workers managing multiple stakeholders, this creates a natural forcing function for negotiating priorities rather than accepting every request simultaneously.
• Making the invisible backlog visible. Most professionals have a mental backlog: a collection of commitments, follow-ups, and intentions that exists in memory rather than in a system. Externalizing this into a visible board does two things: it relieves the cognitive load of maintaining the backlog in working memory (the Zeigarnik effect, where incomplete tasks occupy mental bandwidth), and it makes the true scope of commitments visible, often revealing that the backlog is much larger than felt subjectively.
• Team and meeting integration. Personal kanban boards can be made visible to collaborators, converting a private tracking system into a shared coordination tool. Standup meetings structured around the kanban board, covering what moved from Doing to Done, what is blocked, and what is entering Doing, are a standard agile practice that reduces the reporting overhead of status meetings while increasing their accuracy.