Kanban
Kanban is a visual agile workflow method that optimizes delivery by visualizing tasks and limiting work in progress.
52 resourcesbeginner
Originating in Toyota automotive manufacturing, it uses columns on a board to track task status from backlog to completion. By constraining simultaneous work, teams eliminate bottlenecks and maintain steady flow.
How it works
Kanban organizes work through continuous visual flow and strict capacity management.
- Visual boards represent progress stages with columns such as To Do, In Progress, Review and Done.
- Kanban cards represent discrete units of work containing specifications, assignees and criteria.
- Work in progress limits cap the maximum number of active cards allowed in any single column.
- Continuous delivery releases completed items immediately rather than waiting for rigid sprint boundaries.
When to use it
Adopt Kanban when work priorities shift rapidly or teams manage continuous incoming requests.
- Maintenance and bug triage handles urgent production defects and ongoing customer feedback tickets.
- Design system support teams handle incoming component requests, reviews and accessibility updates steadily.
- Mature product squads that have moved beyond artificial sprint boundaries to continuous deployment.
- Operational support squads where rigid two-week sprint planning is constantly disrupted by live events.
Trade-offs
Kanban delivers flexible adaptability, but requires strong team discipline to prevent drifting.
- Less structured milestone planning makes it harder to promise fixed delivery dates to external stakeholders.
- Requires strict adherence to limits, because ignoring work in progress limits destroys the flow benefits.
- Can lead to endless backlogs if teams continuously pull small tasks without shipping cohesive releases.
Key takeaways
- Kanban visualizes workflow stages on a board to create transparent team accountability.
- Limiting work in progress prevents multitasking, reduces cycle times and exposes bottlenecks.
- Continuous delivery pulls tasks as capacity opens rather than adhering to rigid sprint batches.
- It excels at managing continuous streams of design maintenance and incoming issue requests.
Learn this
Lessons and exercises mapped to this concept.
CourseProduct Management FoundationsMaster modern product leadership: root-cause problem discovery, customer-driven vision, cross-functional collaboration, agile execution, and measurable business impact.CourseUX Design FoundationsMaster the principles, cognitive ergonomics, visual hierarchy, and scientific workflows of user experience design. 100% original curriculum synthesized from authoritative interaction design literature.
Common questions
- How does Kanban differ from Scrum?
- Scrum organizes work into fixed time-boxed sprints with predefined commitments. Kanban is a continuous pull system where work flows steadily without fixed sprint dates.
- Why are work in progress limits vital in Kanban?
- Without limits on active tasks, team members juggle too many tasks at once, creating context switching and slowing down overall team throughput.