Learn Kanban by practicing Kanban
Each concept is a short experience: you decide, simulate the flow and see the consequence right away. Practice > memorize.
WIP limit
Adjust the WIP and find the sweet spot between starving and overload.
Practice this concept → ⏱️ InteractiveLead Time & Cycle Time
The gap between what the customer feels and the execution time.
Practice this concept → 📦 InteractiveThroughput
How much the system really delivers, and what limits it.
Practice this concept → 🔧 InteractiveBottlenecks
Find the stage that sets the pace, and why only it matters (Theory of Constraints).
Practice this concept → 💧 InteractiveFlow Efficiency
How much of the time work actually flows, and how much it just waits.
Practice this concept → 📊 InteractiveCFD
Read the cumulative flow diagram and what it reveals.
Practice this concept → 🎯 InteractiveClasses of Service
Prioritize by risk and cost of delay, not by who shouts loudest.
Practice this concept → 💸 InteractiveCost of Delay
The real price of postponing a delivery.
Practice this concept → 🧭 InteractiveFlow War Room
A decision mission: diagnose the bottleneck, handle the urgent and prioritize by CD3.
Practice this concept →Frequently asked questions
How many experiences are there?
Nine, all available: WIP limits, lead time and cycle time, throughput, bottlenecks, flow efficiency, cumulative flow diagram, classes of service, cost of delay and the flow war room.
How long does each one take?
Between five and seven minutes. They are deliberately short: each covers one concept and shows the consequence of your decision right away.
Do I need an account?
Not to practice. The free account is there to save progress, join the learning paths and show up in your progress page.
Is there a recommended order?
There is, and it lives in the learning paths. If you just want a loose starting point, begin with WIP limits: it is the concept the others depend on.
Does this replace a Kanban course?
No. The experiences teach how each concept behaves, which is the part text explains badly. Organizational context, rollout and facilitation still need a course and practice with people.
Does it work outside software?
It does. Flow concepts apply to any work with queues, deadlines and too much started work. The examples use product teams, but the mechanics are the same.
