Kanban

A strategy for making work observable, managing flow, and continuously improving value delivery. Specifically Kanban as outlined in the Kanban Guide.

Kanban is a strategy for change, not a tool or board. As defined in the Kanban Guide, it enables organisations to “start with what they do now,” understand their current system, and improve flow and value delivery through evolutionary change. It is rooted in Lean principles and systems thinking, focusing on how work flows rather than what work gets done.

Unlike frameworks that prescribe roles or timeboxes, Kanban introduces observability: visualising work, limiting WIP, managing flow, and making policies explicit. This exposes bottlenecks and enables evidence-based improvement without disrupting existing structures.

Kanban complements other approaches like Scrum and DevOps by improving transparency and decision-making. It does not require a reset or reorganisation. Instead, it guides teams to adapt their way of working over time, based on feedback and performance metrics such as lead time, throughput, and service-level expectations.

Crucially, Kanban is often misunderstood as just visual task tracking. But its true power lies in creating a shared understanding of system behaviour and enabling strategic decisions about where and how to improve. It empowers teams to deliver value predictably, sustainably, and with greater resilience, making it an essential strategy for navigating complex, evolving environments.

The strongest work on Kanban — ranked by substance, not recency. How this is ranked

Article Product Development Kanban

Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?

Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …

Read article
Article Lean Kanban

Estimating Better in an Overloaded System Is a Poor Man’s Strategy

High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …

Read article
Video Kanban Lean

Maximizing Transparency and Improvement in Software Engineering with Kanban

Learn how Kanban boosts transparency in software engineering, helping teams visualise workflows, identify bottlenecks, and drive continuous …

Watch video
Article Kanban Product Development

Why Measuring Individual Cycle Time is Killing Your Flow (And What to Do Instead)

Measuring individual cycle time in Kanban misleads teams, hides real bottlenecks, and harms flow. Focus on system-wide metrics like PCE, …

Read article
Video Kanban Product Development

Mastering Kanban: Creating a Pull-Based System for Workflow Efficiency

Learn how Kanban’s pull-based system boosts workflow efficiency by visualising tasks, setting WIP limits, managing bottlenecks, and enabling …

Watch video
Video Kanban Product Development

The Open Guide to Kanban: Unlocking Collaborative Flow and Real-World Value for Every Team

Unlock better flow and real value with the Open Guide to Kanban, a practical, community-driven resource for teams in any industry. Join the …

Watch video
Video Kanban Product Development

Why Limiting Work in Progress is Key to Success in Kanban

Limiting work in progress in Kanban helps teams focus, spot bottlenecks, maintain quality, and deliver value efficiently by ensuring a …

Watch video
Video Kanban Product Development

Mastering Kanban: A Simple Guide to Its Core Principles

Learn the three core Kanban principles, visualising workflow, actively managing tasks, and continuous improvement, to boost team efficiency, …

Watch video
Video Kanban

Mastering Kanban: The Essential Guide to Defining and Visualising Your Workflow for Maximum Efficiency

Learn how to define and visualise workflows in Kanban to boost team clarity, alignment, and efficiency, with practical steps for stable …

Watch video