🌊 Learning path
Kanban from Zero to Flow
The foundation: visualize, limit work, and see flow through metrics.
How this path is put together
The order here is not accidental. You start by limiting work in progress because it is the only change that improves flow without asking for more people. Then you learn to measure what the customer feels, lead time, and what the system actually delivers, throughput. The cumulative flow diagram puts both in a single chart, and the closing mission tests all of it on a squad drowning in WIP, where you decide under pressure instead of agreeing in theory.
Who it is for
For anyone starting with Kanban, or already running a board without being able to say whether it is working. No prior knowledge and no tool required.
By the end of the path, you can
- Explain why limiting WIP shortens delivery time
- Tell lead time from cycle time and know which one each conversation needs
- Read a cumulative flow diagram and point out where work piles up
- Cut a team WIP without stopping the operation
Ready to start?
Steps are saved to your progress. You can stop and come back later.
