The Kanban method helps teams visualize their work, identify bottlenecks, and optimize the flow of tasks. It is based on the use of Kanban boards to represent the status of tasks in different phases of the workflow.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
Kanban is a method for steering work through a visible flow with limits on parallel work. Teams make tasks, bottlenecks, and waiting visible and improve flow step by step.
Kanban originated in the Toyota Production System, where replenishment was aligned with actual consumption. David J. Anderson adapted its principles to knowledge work and software development in the 2000s; a broad community continues to evolve the method.
Picture a board as a riverbed: cards move through states such as ready, in progress, and done. WIP limits constrain each section; when cards pile up, the team works on the bottleneck before starting more work.
A shared board shows work state, order, and blockers.
Bounded parallel work protects focus and exposes overload.
Measurement and shared experiments reduce waiting and stabilize delivery.
Kanban supports teams with changing or unplanned work, such as operations and support. It improves transparency and throughput but does not replace product decisions; poor columns or limits can hide actual flow.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.