Developed for knowledge work by David J. Anderson (Kanban, 2010), from the kanban of Taiichi Ohno (Toyota Production System, 1978).
Puts work on a board of stages, caps how many items each stage may hold, and pulls new work only when capacity frees up, exposing bottlenecks.
Seven requests a week into a team that finishes about six: what a limit on work in progress does
The team starts work whenever it is under its limit; every item in progress past six adds switching that slows finishing (R1). It opens with no limit that binds. Lower the limit and watch work in progress, the weeks each item takes once started, and the queue of requests that now waits in plain view. Illustrative.
Items in progress
Weeks per item once started
Requests waiting to start
Week 16 of 16
- Items in progress
- 105
- Weeks per item once started
- 33.6
- Requests waiting to start
- 0
- Items finished that week
- 3.0
- R1, Overload slows finishing
- More in progress means more switching, slower finishing, and so more still in progress next week. Two negative (−) links: an even count, so the loop reinforces.
- Requests waiting
- New requests arrive at seven a week. With a limit, the ones not yet started wait here, visible, where they can be ranked or declined.
- Work in progress
- Everything started and not finished: the cards on the board between the first column and Done.
- Finished a week
- About six a week when people work on few things at once.
- Limit on work in progress
- The team's rule: pull a new item only when the count in progress is under the limit.
- Switching between tasks
- Each item past six in progress costs time in context switches, status meetings, and waiting on each other.
An example
A five-person marketing operations team took requests from every product group: landing pages, email builds, campaign reports. Each person had eight or nine things open, everything was in progress, and a simple page took five weeks. The team lead had asked for two more hires and been refused.
She put every open item on a board with five columns: requested, building, in review, ready, and done. The board showed forty-one cards between requested and done, and eleven of them sat in review, waiting on the same two approvers. The team agreed on a limit: no more than eight items in building and review together, and a new item pulled only when one finished. The requests not yet started now waited in the first column, where the product leads could see them.
Within eight weeks, items in progress were down to eight and a landing page took about a week and a half once started. The queue in the first column told the product leads what the hiring request had not: demand ran ahead of capacity, so they ranked it.
Why it works
Starting work feels like progress, so teams start everything. But each item in progress takes a share of attention, and a person juggling nine items spends much of the week switching, chasing status, and waiting on others. The more that is open, the slower each item finishes, and the slower things finish, the more stay open.
A limit on work in progress breaks that loop. Finishing becomes the only way to start something new, so attention goes to what is nearly done and to whatever is blocking it, which makes the bottleneck obvious. The work that cannot start yet does not disappear: it waits in plain view, so the gap between demand and capacity becomes a question for the people asking, who can rank it or drop it.
The thinking behind it
David J. Anderson David J. Anderson, a software manager, set out the Kanban method for knowledge work in Kanban: Successful Evolutionary Change for Your Technology Business (2010): make the work visible, limit work in progress, and improve the process in small steps. His book traces it from a 2004 team at Microsoft to a project at Corbis in 2006 and 2007. It is a practitioner's book drawn from those cases, not a research study.
Taiichi Ohno Taiichi Ohno, the Toyota executive regarded as the father of the Toyota Production System, built it on just-in-time production, in which each step makes only what the next one has pulled, and on autonomation. He described the system, and the kanban cards that carry those pull signals between steps, in Toyota Production System: Beyond Large-Scale Production (1978; English edition 1988).
How to run it
- Draw the process as it is. Make one column for each real stage the work passes through today, without redesigning anything yet.
- Put every open item on the board. Include the work people are doing quietly, since the true count is usually the first surprise.
- Set a limit on items in progress. Start near the team's size or a little above, for each column or for a group of columns.
- Pull new work only under the limit. When a column is full, help finish or unblock what is in it before starting anything new.
- Keep the waiting work visible. Leave unstarted requests in the first column and let the people asking rank them.
- Track lead time and throughput. Record when each item starts and finishes, and how many finish each week.
- Write the rules down and adjust. Post the limits and the team's working rules on the board and change them a little at a time.
Where it goes wrong
The limit is set so high it never binds. A limit of thirty on a five-person team changes nothing, and the board becomes a picture of the overload. Set it low enough that the team feels it within a week.
The limit is broken for urgent work. Every request can be made urgent, and an exception used weekly is the old system again. Give urgent work one reserved lane with a limit of its own.
The queue is hidden again. Teams under pressure start items to make the first column look shorter. The waiting queue is the point: it is the evidence that demand exceeds capacity, and it belongs in front of the people who set priorities.
When to use something else
- Theory of Constraints. When one stage clearly limits the whole flow and the work is to raise that stage's capacity.
- Queueing Theory. When the arrivals and service times need to be modeled to size capacity before changing anything.
- Getting Things Done. When the overload is one person's scattered commitments, with no shared board.
Where it sits in SOLVE eX
Go to the source
- Kanban: Successful Evolutionary Change for Your Technology Business, 2010
- Toyota Production System, 1978