15 Leading Lean change

This chapter argues that meaningful improvement in software teams is driven less by formal authority and more by visible, measured action. Developers can influence practices by improving their own work first, sharing the results, and letting voluntary adoption follow. The core idea is simple: act, measure, and share. When a change is local, reversible, and low risk, it can usually be tried without permission; when it works, the evidence builds credibility for larger changes later.

The chapter also shows that coaching can happen in tiny, everyday interactions. A short PR comment, Slack reply, or pairing conversation can teach not just what to fix, but why it matters, how to address it, and the broader pattern to apply next time. This approach helps knowledge spread across the team, reduces repeated mistakes, and turns individual reviewer insight into shared standard work. In the same spirit, small wins should be made visible so the team can see progress accumulating and feel momentum rather than treating each improvement as isolated.

As change spreads, the chapter emphasizes adapting practices to context instead of copying them mechanically. What works for one team may not fit another, so principles like reducing context switching or improving flow must be co-designed locally and tested as experiments. Resistance to change is treated as useful information: experience-based resistance reveals hidden constraints, fear-based resistance calls for reversibility, and identity-based resistance—especially when AI changes roles—needs reframing so people see their expertise as more valuable, not less. Finally, production incidents and delivery experiences should be turned into learning by updating standard work, so the organization gets better over time instead of merely recovering from problems.

The influence without authority cycle: act first, share data, let adoption happen.

Micro-coaching framework: what, why, how, pattern.

The communication cycle that turns isolated wins into team momentum.

Copy the principle, not the practice.

Working through identity-based resistance without burning trust.

From incident to updated standard work: the learning cycle

The change agent's cycle: Lean tools applied to organizational change.

• Influence without authority follows a simple pattern: act, measure, share. Let voluntary adoption make it standard.
• The Coaching Kata: what, why, how, pattern, maps micro coaching to Lean principles and compounds skill transfer.
• Small wins compound into momentum only when you communicate them. A weekly wins message with a running total, naming the people behind the changes, builds a team identity around continuous improvement.
• Resistance comes in three types: experience-based, fear-based, and identity-based. AI is the largest current source of identity-based resistance.
• Incident reviews that update standard work convert individual debugging into team-wide learning. Post-feature retros and code archaeology sessions extend that learning beyond failures.
• The long game unfolds in three phases: prove it works, others adopt, it becomes how we work.

FAQ