Key takeaways
– Kanban is a visual, pull‑based inventory and workflow control system developed at Toyota by Taiichi Ohno; the name means “visual card.”
– Core goals: reveal and eliminate bottlenecks, limit work‑in‑progress (WIP), and smooth flow so the right items are produced or worked on at the right time.
– Kanban applies to manufacturing, purchasing, software development and other knowledge work; it can be implemented with physical cards or electronic tools.
– Essential practices: visualize the workflow, set WIP limits, manage flow, make policies explicit, implement feedback loops, and improve collaboration continuously.
1. What is Kanban?
Kanban is a signal-and-response system originally used in just‑in‑time (JIT) manufacturing to trigger production or replenishment when inventory reaches predefined levels. In modern business contexts it is a workflow management method that uses visual cues (cards) on a board to represent tasks or containers, enabling teams to pull work when capacity is available rather than having work pushed to them.
2. Brief origin
Kanban was developed by Taiichi Ohno at Toyota as part of JIT manufacturing. The classic implementation used colored cards placed on or in containers; when a card appeared it signaled that more parts should be produced or moved.
3. Core principles and practices
– Visualize the workflow: map the end-to-end process step by step; represent individual work items as cards on a board (physical or electronic).
– Limit work in progress (WIP): set explicit limits on how many items may be in a given stage at once.
– Manage and optimize flow: watch how work moves; identify and remove bottlenecks to keep items flowing.
– Make policies explicit: define entry/exit criteria, done definitions, priorities, and handover rules so everyone agrees how work proceeds.
– Use feedback loops: hold regular reviews (daily standups, replenishment meetings, retrospectives) to inspect and adapt.
– Improve collaboratively and experimentally: use empirical data and small experiments to evolve the system.
4. Typical components of a Kanban board
– Board: represents a workflow at a macro level (team, department, product).
– Lists/columns: process stages (e.g., Backlog → Ready → In Progress → Review → Done).
– Cards: individual work items with attributes (assignee, size, due date, class of service).
– Swimlanes: horizontal grouping for teams, priority classes, or work types.
– Explicit WIP limits: shown on columns or lanes.
Example physical approach: sticky notes or cards on a whiteboard. Example electronic approach: Kanban features in tools like Trello, Jira, Azure Boards (see Electronic Kanban section).
5. Classic kanban signals: two-card system
– Production card (P‑kanban): authorizes production of a fixed quantity at a workstation.
– Transportation card (T‑kanban): authorizes movement of a container to the next workstation.
This physical two‑card approach enforces pull and exact replenishment amounts.
6. Scrum vs Kanban (high‑level)
– Cadence: Scrum uses fixed-length iterations (sprints); Kanban is continuous flow with no required iteration length.
– Roles & ceremonies: Scrum prescribes roles (Scrum Master, Product Owner) and ceremonies; Kanban imposes no required roles or rituals—teams adopt what they need.
– WIP & planning: Kanban explicitly limits WIP and pulls work; Scrum limits scope by sprint commit. Kanban tends to be more flexible for changing priorities midstream.
7. Benefits of Kanban
– Better visibility of work and bottlenecks.
– Reduced overproduction and excess inventory/WIP.
– Faster response to changing priorities and demand.
– Improved throughput and lead-time predictability.
– Lower waste and more efficient use of capacity.
– Easier incremental adoption (no big process rewrite required).
8. Disadvantages and limitations
– Requires organization‑wide discipline to make limits and policies effective.
– Can be less prescriptive; teams new to self‑management may struggle to define policies.
– Without metrics and feedback loops, Kanban can degrade into unmanaged queues.
– Scaling across multiple teams or complex value streams requires careful design.
9. Rules of Kanban (practical restatement)
– Start with what you do now; don’t force big change.
– Agree to incremental, evolutionary change.
– Respect current roles and responsibilities.
– Encourage leadership at all levels.
– Make work and policies visible; limit WIP; measure and improve flow.
10. Why use Kanban?
– To control inventory and avoid excess (manufacturing/procurement).
– To visualize and manage workflow, decrease lead times and increase throughput (knowledge work).
– To create a pull system so work is started only when capacity exists.
– To build continuous improvement through transparent data and feedback.
11. Is Kanban Agile or Lean?
– Kanban is rooted in Lean manufacturing principles (waste elimination, JIT).
– It is commonly used in Agile software and knowledge work environments because its focus on flow and incremental improvement complements Agile values. So it is both Lean‑inspired and commonly used within Agile practices.
12. Metrics and visual tools to use
– Lead time: time from request to delivery.
– Cycle time: time from start of work to completion.
– Throughput: items completed per time period.
– Work‑in‑Progress (WIP): current items in progress.
– Cumulative Flow Diagram (CFD): visualizes queue sizes across stages over time—very useful to spot bottlenecks.
– Control charts: variability in cycle time.
13. Practical step‑by‑step implementation (for a team)
1) Sponsor and alignment
• Secure visible sponsor/leadership buy‑in and agree goals (e.g., reduce lead time, increase throughput).
2) Map the current workflow
• Draw the end‑to‑end process; include cross‑functional handoffs and policies that already exist.
3) Define board layout
• Choose columns (e.g., Backlog, Ready, In Progress, Review, Blocked, Done). Add swimlanes for priorities or work types.
4) Decide card attributes
• What info goes on cards (title, owner, size/estimate, due date, class of service)?
5) Set initial WIP limits
• Start conservative and measurable. Tip: limit WIP per person to 1–3 items in-progress, or set column limits based on team size (e.g., WIP = number of people in that stage + 1).
6) Define explicit policies
• Entry/exit criteria for columns, definition of “Done”, handling blocked items, service level expectations.
7) Implement a pull mechanism
• Team members pull work from the upstream column when capacity permits—no pushing.
8) Establish cadences and feedback loops
• Daily standups at the board, replenishment meetings (to refill the Ready column), and retrospectives (weekly or biweekly) to tune process.
9) Instrument and measure
• Start tracking cycle time, lead time, throughput, and visualize with CFD and control charts.
10) Iterate and improve
• Use small experiments (Change one policy or WIP limit), observe effects, adopt or revert based on data.
11) Scale thoughtfully
• For multiple teams or complex value streams, consider value stream mapping, service classes, or a Portfolio Kanban.
14. Practical tips, patterns and policies
– Classes of service: Expedite, Fixed Date, Standard, Intangible — set explicit rules for each (e.g., expedite preempts WIP limit but requires manager approval).
– Blocked column: move blocked items to a visible “Blocked” column and require an owner to resolve.
– Pull not push: enforce that only when WIP < limit can a new card be pulled.
– Limit work size: break large items into smaller cards to improve flow and predictability.
– Use Cumulative Flow Diagram every week to detect growing queues.
– Start with a single team or value stream; scale only after stabilization.
15. Common pitfalls and how to avoid them
– Pitfall: No WIP limits — leads to multitasking and slower flow. Fix: enforce WIP limits and make violation visible.
– Pitfall: Poorly defined policies — leads to confusion. Fix: write simple, testable entry/exit criteria and publish them on the board.
– Pitfall: Ignoring metrics — you won’t know whether changes help. Fix: track cycle time and throughput from day one.
– Pitfall: Treat Kanban as only a board tool — it’s a system that requires process change and behavior change.
16. Example quick checklist for Day 1 Kanban
– Map workflow and draw board.
– Create cards for current work and place them in appropriate columns.
– Set simple WIP limits (e.g., In Progress = team size).
– Agree on definition of “Done” for each column.
– Schedule daily 15‑minute standups at the board.
– Start tracking cycle time for completed cards.
17. When to use Kanban vs when not to
– Use Kanban when: work is continuous or unpredictable, you need faster throughput, you want incremental change, or you have cross-functional flow.
– Consider alternatives (Scrum, Scrumban, or staged hybrid) when: fixed-length releases are required, teams need explicit cadence for planning, or when a more prescriptive framework will help a novice organization.
18. Bottom line
Kanban is a simple, powerful approach to visualize work, limit WIP and improve flow. It can be applied to manufacturing, supply chains, purchasing and many kinds of knowledge work. Effective Kanban combines visible boards, explicit policies, WIP limits, and a culture of measurement and continuous improvement. Start small, measure, and evolve your system to reduce lead times and improve predictability.
Further reading / reference
– Investopedia — Kanban
Editor’s note: The following topics are reserved for upcoming updates and will be expanded with detailed examples and datasets.