The Kanban Maturity Model

Kanban is evolutionary, but that doesn't mean random. The Kanban Maturity Model (KMM) provides a roadmap: what to focus on at each stage of maturity.

Levels in the KMM:

• ML0: Oblivious (no consistent process)
• ML1: Team-focused (basic Kanban at team level)
• ML2: Customer-driven (flow focus, customer orientation)
• ML3: Fit-for-purpose (sophisticated service delivery)
• ML4: Risk-hedged (quantitative management)
• ML5: Congruent (market-leading, fully evolved)

Most teams should focus on ML1-ML2 initially. ML3 and beyond require years of practice.

Focus: Basic Kanban practices at the team level.

What you're doing:

• Visualizing work on a board
• Implementing basic WIP limits
• Holding regular standups
• Starting to track cycle time
• Making some policies explicit

Organizational culture: Typically still command-and-control, but team has autonomy over their own process.

Success criteria:

• Team uses the board consistently
• WIP limits are generally respected
• Problems are visible sooner
• Some improvement in predictability

Common challenges:

• WIP limits feel uncomfortable
• Not everyone uses the board
• Metrics aren't tracked consistently
• Resistance to change

Focus: Flow and customer orientation.

What you're doing:

• Classes of service implemented
• Flow metrics tracked and used
• Service delivery reviews with stakeholders
• Policies are explicit and refined
• Pull system fully operational
• Regular replenishment meetings

Organizational culture: Teams have more autonomy. Customer satisfaction is a real focus, not just lip service.

Success criteria:

• Lead time is measured and improving
• Stakeholders trust delivery predictions
• Team proactively manages flow
• Bottlenecks are identified and addressed
• Continuous improvement is real, not just talked about

Common challenges:

• Metrics exist but aren't used for decisions
• Customer feedback loop is slow
• Dependencies on other teams cause problems
• Organization hasn't caught up with team maturity

ML3: Fit-for-Purpose

Advanced service management:

• Service level expectations formalized
• Risk management integrated
• Probabilistic forecasting (Monte Carlo)
• Sophisticated capacity planning
• Multiple services managed coherently

ML4: Risk-Hedged

Quantitative management:

• Statistical process control
• Risk models
• Portfolio-level flow management
• Predictability at organizational level

ML5: Congruent

Market leadership:

• Continuous innovation
• Organization fully aligned around flow
• Culture of continuous improvement at all levels
• External benchmarking and thought leadership

Realistic expectations: Most teams plateau at ML2 or ML3, and that's fine. These levels already provide massive value. ML4-5 are aspirational for organizations that want to lead, not just participate.

Assessment:

• Where is your team now?
• What practices are in place?
• What's missing or weak?

Prioritization:

• What's the next logical step?
• What would have the most impact?
• What foundations are unstable?

Avoiding premature advancement:

• Don't implement Monte Carlo if you're not tracking cycle time
• Don't formalize SLAs if you can't measure lead time
• Don't try organizational Kanban if teams don't have stable practices

The value of the model: It provides a coherent answer to "what's next?" Without it, improvement is random. With it, you have a roadmap.