The Principle of Evolutionary Change

The first foundational principle of Kanban is: Start with what you do now.

This sounds obvious but is profoundly different from most process improvement approaches. Scrum says "adopt these roles and events." SAFe says "implement these layers." Six Sigma says "follow this methodology."

Kanban says: "First, understand your current reality."

Why? Because:

• Revolutionary change triggers resistance
• Imposed processes feel like criticism of current work
• People protect what they've built
• Context gets lost when you tear down and rebuild

Evolutionary change means making small, incremental improvements to an existing system rather than replacing it wholesale.

The second foundational principle: Agree to pursue incremental, evolutionary change.

This requires organizational buy-in not to any specific change, but to the idea of continuous small improvements. It's a meta-agreement: we commit to the process of evolving, not to a specific end state.

In practice, this means:

• No "big bang" transformations
• Experiments rather than mandates
• Permission to try and fail safely
• Patience with the pace of change

The paradox: Small changes feel slow, but they stick. Big changes feel fast, but they often revert.

Most "agile transformations" fail because they try to change everything at once. Teams comply while managers watch, then revert when attention moves elsewhere. Kanban's incremental approach, while slower initially, creates sustainable change.

The third foundational principle: Initially, respect current roles, responsibilities, and job titles.

This is counterintuitive. If the current process has problems, shouldn't we fix the roles? Not immediately.

Here's why:

• People's identities are tied to their roles
• Role changes feel like demotions or criticism
• Political battles over titles derail improvement
• The process, not the people, usually needs to change first

As flow improves through Kanban practices, roles naturally evolve. A bottleneck might reveal that one role has too much responsibility. A flow problem might show that handoffs between roles are the issue. Let the data drive role evolution, not top-down reorganization.

The exception: If a role is actively harmful, you may need to address it. But even then, start by visualizing the harm before proposing changes.

The fourth foundational principle: Encourage acts of leadership at every level.

Kanban isn't a management system that gets imposed on teams. It's a framework that enables anyone to identify and address problems. The person closest to a bottleneck is often best positioned to fix it.

This means:

• Individual contributors can propose process changes
• Experiments don't require executive approval
• Data-driven decisions replace authority-driven ones
• Improvement is everyone's job, not just management's

The role of formal leaders: Create the environment where this can happen. Remove fear of punishment for experiments. Celebrate learning from failures. Make it safe to raise problems.

Kanban systems without psychological safety become surveillance systems. The board shows who's "behind," and people game the metrics. With safety, the board becomes a collaboration tool where problems are welcomed as opportunities.