methodDelivery & agility

Kanban Method

An evolutionary management method that visualizes knowledge work, limits work in progress, manages flow, and improves an existing service through feedback.

Download Markdown (.md)

01What it means

The Kanban Method improves how a service delivers work without requiring a wholesale process replacement. Teams start with their current workflow, visualize work and policies, limit work in progress, manage flow, establish feedback loops, and evolve the system through collaborative experiments. Work is pulled when capacity becomes available rather than pushed into an overloaded system.[1][2]

Evolutionary flow-management system Visualize current work, limit overload, review flow, and improve collaboratively
  1. 01VisualizeWork, states, queues, blockers
  2. 02Make policy explicitEntry, exit, replenishment, service classes
  3. 03Limit WIP + pullProtect finishing capacity
  4. 04Measure + reviewLead time, throughput, age, feedback loops
  5. 05EvolveSmall reversible experiments

Work is pulled when capacity becomes available; the method starts from the current service instead of requiring wholesale process replacement.

02Why it matters

Invisible queues and excessive parallel work make delivery slow and unpredictable. Kanban exposes waiting, blocked work, and uneven demand. Work-in-progress limits encourage finishing, while flow measures help teams discuss system performance with evidence instead of judging individual busyness.

03When to use it

Use Kanban for product, platform, support, operations, or discovery work that arrives continuously or varies in size and urgency. It is also useful when a team wants incremental improvement without adopting time-boxed iterations. It requires enough discipline to honor explicit policies and address bottlenecks rather than merely decorate a board.

04How it works

  1. Map the current workflow and visualize work items, states, queues, and blockers.
  2. Define explicit entry, exit, replenishment, and class-of-service policies.
  3. Set work-in-progress limits that create pull and protect finishing capacity.
  4. Track flow using measures such as lead time, throughput, work in progress, and work item age.
  5. Hold replenishment, delivery, and service reviews suited to the context.
  6. Run small, reversible experiments to improve customer outcomes and flow.

05A practical example

Example

A growth platform team receives planned enhancements and urgent integration failures. It visualizes both, caps active engineering work, defines a narrow expedite policy, and reviews aging items weekly. Lead time falls after the team stops starting new enhancements whenever testing becomes the bottleneck.

06Where it breaks

A board alone is not Kanban, and faster flow does not prove that the work is valuable. Poorly chosen limits can be ignored or create local optimization. Metrics can also become performance targets, inviting gaming unless the team uses them to improve the service as a whole.

Common mistakes

  • Calling any task board Kanban while leaving work in progress unlimited.
  • Optimizing one workflow column instead of end-to-end customer delivery.
  • Treating blocked work as normal rather than investigating its causes.
  • Using cycle-time data to rank individuals.

07Sources

  1. The Official Guide to the Kanban MethodKanban University · Official method guideThe Official Guide to the Kanban Method
  2. The Kanban GuideKanban Guides · Professional guideThe Kanban Guide
View saved topics

Start typing to search titles, definitions, categories, and frameworks.