Improve Collaboratively and Evolve Experimentally
Originally Published August 2025
The Kanban Maturity Model (Second Edition) describes improving collaboratively as “a collaborative collection of observations and insights from people at different positions in the process and the organization,” while evolving experimentally “conveys the idea that chosen changes are guided by models and have a hypothesis, even if purely qualitative, about the anticipated outcome.” Together, these ideas create a culture where change is not imposed, but co-created – rooted in evidence, enriched by diverse perspectives, and tested in ways that reduce risk while increasing confidence.
At its heart, this practice is about building a shared understanding of the purpose, process, and associated problems. From there, teams suggest improvement actions based on sound models and methods, then reach agreement to evolve continually. With Kanban, we start with what we do now and seek ways to improve it. It begins from the organization as it exists today and pursues continuous, incremental changes that, over time, add up to meaningful progress.
A defining strength of this practice is the way it promotes learning through deliberate experimentation. Teams define improvement experiments with a clear hypothesis, foresee the likely outcome, and then compare the actual results against what was expected. This cycle of prediction and validation deepens understanding, reduces the risks of change, and allows lessons learned to be applied to the next round of improvements. The process often begins with identifying sources of dissatisfaction, whether they arise from internal team dynamics or from the customer’s experience. Identifying and correcting these sources can shape the Kanban system, the policies that govern it, and the classes of service it uses. As teams refine their work, they also become adept at spotting sources of delay, addressing bottlenecks, and reducing wait times that slow delivery and diminish value.
Policies, too, benefit from regular review. Over time, they may evolve unintentionally or remain in place long after they are useful. By questioning whether they are still relevant, effective, or perhaps even harmful to the broader system, teams can decide whether to adapt, replace, or retire them. This continual questioning and refining ensures that improvement remains a steady, deliberate habit rather than an occasional initiative.
When practiced consistently, Improve Collaboratively, Evolve Experimentally makes change a natural part of everyday work. Instead of large, risky overhauls, teams make smaller, safer adjustments—learning with each step and strengthening both their processes and their trust in one another.
We have now explored all six core practices of Kanban: Visualize the Workflow, Limit Work in Progress, Manage Flow, Make Policies Explicit, Implement Feedback Loops, and now Improve Collaboratively, Evolve Experimentally. Each practice offers its own perspective on how to make work visible, guide it effectively, and keep improving along the way. Woven together, they create a system where progress is easier to see, challenges are easier to address, and improvements are easier to sustain. That’s why, in Kanban, Seeing Is Believing – once you can truly see your work, you can begin to change it for the better.