Evolutionary change is Anderson's foundational philosophical principle for the kanban-method — the claim that organizations should improve incrementally, starting from their current state, rather than through revolutionary disruption of existing processes, roles, and culture. It is encoded in the method's first two core principles and shapes everything else about how the method is designed and positioned.
The Three Founding Principles
Anderson's mature formulation of the evolutionary change philosophy appears in kanban-book as three principles:
1. Start with what you do now. The kanban system overlays on existing processes. It does not require abandoning the current workflow, methodology, or organizational structure. 2. Agree to pursue incremental, evolutionary change. The organization commits explicitly to gradual improvement rather than transformation. The commitment is to direction, not destination. 3. Respect the current process, roles, responsibilities, and titles. Existing arrangements are not treated as obstacles to be cleared. They represent accumulated decisions — political settlements, learned expertise, institutional memory — and should be evolved with respect.
These principles were not just pedagogical: they were the design rationale for why the Kanban Method was structured as an overlay rather than a replacement methodology.
The Consulting Context
Anderson developed this philosophy partly from direct experience with consulting engagements. Disruptive change management approaches (such as Scrum adoption, which requires new role definitions, ceremonies, and iteration structures) frequently failed in organizations where:
The evolutionary approach was designed to be politically low-friction. Because it starts with what exists, there is no role restructuring to fight over, no ceremony calendar to argue about, no iteration cadence to impose. The board appears on the wall; WIP limits are added; the existing team, doing their existing work, begins to see their system differently.
Contrast with Scrum
Anderson was explicit — at times polemical — about the contrast with Scrum. Scrum is a prescriptive framework: it specifies roles (Product Owner, Scrum Master, Development Team), ceremonies (Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective), artifacts (Product Backlog, Sprint Backlog, Increment), and time-boxing (sprints of 1-4 weeks). Installing Scrum means changing what the organization does.
Anderson's argument in kanban-alternative-path-to-agility and elsewhere was not that Scrum is wrong but that evolutionary adoption often succeeds where Scrum adoption fails, precisely because it doesn't require the organization to simultaneously learn a new process, restructure roles, and commit to iteration discipline. The kanban overlay creates improvement pressure without the adoption barrier. This contrast is explored systematically in kanban-and-scrum-kniberg, which compares the two frameworks across multiple dimensions.
This debate was significant in the broader Agile community from approximately 2009 onward, when the Kanban Method was gaining visibility. It was sometimes read as an attack on Scrum; Anderson's position was more nuanced — that evolutionary change is the appropriate mechanism for organizations that cannot absorb disruptive change.
Evolutionary, Not Static
The evolutionary change principle is sometimes misread as conservatism: "start with what you do now" sounds like "don't change much." Anderson was emphatic that this is a misreading. The commitment is to continuous evolutionary change — the PDSA cycle applied indefinitely, with each improvement creating the stable platform for the next. The target state is not defined in advance because it cannot be: the appropriate organizational design depends on the context, which evolves as the organization learns.
This connects to the kanban-maturity-model-concept: the maturity model describes the typical trajectory of evolutionary development, not a destination. Organizations at higher maturity levels got there through accumulated incremental improvements, not through a transformation program.
Intellectual Sources
While Anderson developed this as an original principle for the Kanban Method, it connects to several intellectual traditions:
The synthesis — framing evolutionary change as the change management philosophy of the method itself — is Anderson's original contribution.