David J. Anderson’s *Kanban: Successful Evolutionary Change for Your Technology Business* is one of the foundational texts that brought the Kanban method into mainstream software and technology management. Rather than presenting Kanban as a sudden transformation or a set of rigid practices, Anderson describes it as an evolutionary approach to improving existing processes. His focus is on incremental, visual, and empirical change that respects the current structure of an organisation while leading it towards greater flow efficiency and predictability. This book is not about revolution but evolution, showing how teams can adapt and improve their systems through transparency and continuous feedback.
The Origins and Principles of Kanban
Kanban has its roots in the manufacturing world, particularly in the Toyota Production System. It was developed as a way to manage production flow using visual signals to indicate when new work should start and when capacity is available. Anderson adapted this concept for knowledge work, recognising that while software development differs from manufacturing, the underlying principles of flow and limiting work in progress (WIP) are universally applicable.
The essence of Kanban lies in starting with what you currently do. Unlike many process frameworks that demand structural change from the outset, Kanban emphasises respect for existing processes, roles, and responsibilities. Change happens gradually and continuously as the system reveals its constraints and inefficiencies. The key principles can be summarised as: visualising the workflow, limiting WIP, managing flow, making process policies explicit, implementing feedback loops, and improving collaboratively and experimentally.
These principles form the backbone of the method. They encourage teams to observe, measure, and adjust their systems in small steps, always guided by empirical evidence. Kanban provides a means of making invisible work visible, which allows organisations to better understand how work moves through their system and where it gets stuck.
Visualising the Workflow
One of the first steps in implementing Kanban is to visualise the workflow. Most knowledge work is intangible, hidden inside computers or people’s heads, which makes it difficult to manage. By mapping out the steps that work items follow from start to completion, teams can see how work actually flows, rather than how they imagine it does. This process often reveals bottlenecks, queues, and rework loops that were previously invisible.
Anderson recommends starting with a simple board that represents the main stages of your workflow, typically using columns for each stage such as “To Do”, “In Progress”, and “Done”. As understanding deepens, teams can refine the workflow into more specific stages that reflect reality. The visual board becomes a living representation of the process, creating shared understanding and accountability.
By visualising the flow, teams can manage it more effectively. They can see at a glance where work is accumulating, where people are overloaded, and where value is getting delayed. This visibility leads to more informed discussions and decisions about priorities and capacity.
Limiting Work in Progress
A central tenet of Kanban is the importance of limiting work in progress. Without limits, teams often start too many tasks, leading to multitasking, context switching, and longer delivery times. By setting clear limits on how many items can be in progress at any one time, teams are forced to focus and finish rather than start and scatter.
Anderson explains that WIP limits create a natural pull system, where new work only enters the system when there is available capacity. This prevents overloading and aligns work intake with the team’s actual ability to deliver. It also exposes bottlenecks more clearly, as any stage where work piles up signals an imbalance in capacity or flow.
By maintaining strict WIP limits, teams experience shorter cycle times, improved predictability, and higher quality outcomes. This principle often requires a cultural shift, as it goes against the common instinct to keep everyone busy at all times. Kanban teaches that idle time in one area is preferable to an overloaded system, as it creates space to address the root causes of delays.
Managing Flow
Once the workflow is visualised and WIP limits are established, the next step is to actively manage flow. The goal is to achieve smooth, predictable movement of work items through the system. Teams use metrics such as cycle time, throughput, and work item age to understand how efficiently work is flowing.
Anderson encourages using cumulative flow diagrams and other visual analytics to identify patterns and issues. For example, if cycle times are increasing, it may indicate growing queues or inconsistent prioritisation. Managing flow is about observing these patterns and taking small, targeted actions to improve them.
Kanban’s approach to flow management is empirical rather than prescriptive. Teams experiment, measure, and adjust based on what they observe. This makes Kanban particularly well suited for complex environments where predictability and adaptability are both essential.
Making Process Policies Explicit
A core idea in Kanban is to make process policies explicit. Many teams operate with implicit rules and assumptions about how work should be done, who makes decisions, and what “done” means. This lack of clarity can cause confusion, inefficiency, and conflict.
By defining and documenting these policies openly, teams create shared understanding and transparency. Examples include the criteria for moving work from one stage to another, prioritisation rules, or quality standards. Anderson emphasises that explicit policies are not meant to be rigid; they should evolve as the team learns and improves.
This explicitness supports fairness and objectivity. It reduces the reliance on individual judgement and memory, and it allows for smoother onboarding of new team members. Everyone can see how decisions are made and why, creating a more predictable and trustworthy environment.
Implementing Feedback Loops
Feedback is essential for continuous improvement. Anderson describes several types of feedback loops that keep a Kanban system healthy. Daily stand-ups, service delivery reviews, and operations reviews are all opportunities to inspect and adapt.
The daily stand-up focuses on the flow of work rather than the status of individuals. Team members discuss which items are blocked, where flow is slowing, and what actions can help restore balance. Service delivery reviews look at performance over time, examining trends in lead time, throughput, and customer satisfaction. Operations reviews take a broader perspective, connecting multiple teams or services to ensure that the overall system is optimised.
These feedback loops create a rhythm of reflection and adjustment. Instead of waiting for large retrospectives at the end of a project, Kanban encourages continuous micro-improvements. Each conversation and review contributes to an evolving, learning system.
Improving Collaboratively and Experimentally
Kanban fosters a culture of continuous, evolutionary change. Anderson’s approach to improvement is grounded in scientific thinking: make small changes, observe the results, and learn from them. This is in contrast to large-scale change initiatives that attempt to overhaul processes all at once.
Collaborative improvement means involving everyone in identifying problems and proposing solutions. Teams experiment with new policies, WIP limits, or flow adjustments, collecting data to evaluate whether the changes help or hinder performance. This participatory approach strengthens ownership and engagement.
Kanban’s evolutionary model aligns well with the complexity of modern technology organisations. It recognises that systems are interconnected and that change in one area can have unintended consequences elsewhere. By improving incrementally, teams reduce risk and build a more resilient culture of learning.
Kanban Metrics and Predictability
Measurement plays a critical role in Kanban. Anderson introduces a range of simple yet powerful metrics that help teams make data-driven decisions. The most important include lead time (the total time from request to delivery), cycle time (the time it takes for work to move through the active workflow), throughput (the number of items completed per time unit), and WIP.
By tracking these metrics and visualising them on charts such as cumulative flow diagrams or control charts, teams gain insight into their system’s performance. These measurements allow for more accurate forecasting, especially when combined with probabilistic models. Rather than making fixed-date promises, teams can use historical data to express confidence levels in their delivery estimates.
Predictability is one of the major benefits of Kanban. By stabilising flow and limiting WIP, variability decreases, allowing teams to deliver value more reliably. Customers and stakeholders gain trust in the process when they see consistent, data-backed results.
Scaling Kanban Across the Organisation
While Kanban often begins with a single team or service, Anderson provides guidance on scaling it across larger organisations. The approach remains evolutionary: expand Kanban organically where it brings value rather than imposing it universally.
Scaling involves creating interconnected Kanban systems, sometimes called service-oriented Kanban. Each team or service defines its workflow, WIP limits, and metrics but also aligns with others through shared policies and feedback loops. This creates a network of services, each optimising its own flow while contributing to the overall system’s performance.
Anderson also emphasises leadership’s role in scaling Kanban. Leaders should act as facilitators of flow, removing systemic impediments and fostering an environment of trust and collaboration. They must focus on enabling teams rather than directing them, aligning decisions with data and outcomes rather than opinions.
Culture, Resistance, and Change
Introducing Kanban is as much about culture as it is about process. Anderson devotes significant attention to the human side of change. Because Kanban does not require immediate structural upheaval, it encounters less resistance than many transformation programmes. However, it still challenges deep-seated habits, especially around multitasking, commitment management, and performance evaluation.
To succeed, leaders must foster a culture of safety and openness. People must feel comfortable exposing problems and experimenting with improvements. Anderson recommends starting small, demonstrating success, and letting results speak for themselves. Over time, success stories spread, and more teams adopt the approach voluntarily.
Kanban’s evolutionary nature respects the past while building a better future. It helps organisations improve without disrupting operations, which makes it sustainable and attractive in environments where failure tolerance is low.
Kanban as a Path to Agility
Although Kanban is not strictly an Agile framework, it aligns closely with Agile values such as transparency, collaboration, and responsiveness to change. Many organisations use Kanban alongside Scrum or as a next step in their Agile journey. It provides a lightweight, flexible system for managing flow that complements other methods and scales easily.
Anderson positions Kanban as a means to achieve agility through evolutionary improvement. It enables teams to deliver value more consistently, learn from data, and continuously adapt their processes. Rather than prescribing how to work, Kanban gives organisations the tools to observe, learn, and evolve their own ways of working.
Ultimately, *Kanban: Successful Evolutionary Change for Your Technology Business* is a practical guide to achieving continuous improvement without upheaval. Anderson shows that by visualising work, limiting WIP, managing flow, and fostering feedback, teams can create a culture of learning and adaptability. The result is not just better processes, but a more predictable, transparent, and resilient organisation.
Do You Want To Learn Scrum & Agile?
Learn Scrum & Agile at lost cost and online. Our 5-star rated Ultimate Scrum & Agile eLearning Courses can take you from beginner to advanced at your own pace.
Prepare and practice for the assessments from the major Scrum & Agile providers. Our 5-star rated Ultimate Scrum & Agile Practice Assessments will help you gain certification.
About TheScrumMaster.co.uk
