liveBook · Manning

Chapter 15: Leading Lean change

What you will learn in chapter 15 of Build High Value Software Systems

The introduction frames Lean change as a learnable, people-centered skill and proposes starting with small, measured improvements that developers share with their teams.

After this chapter you will be able to

What it builds on

Section by section

Introduction

The introduction frames Lean change as a learnable, people-centered skill and proposes starting with small, measured improvements that developers share with their teams.

Key terms: Lean change, people problem, developer-led, act, measure, share

15.1 Influence without authority

This section explains how developers can lead Lean change without formal authority by making improvements visible and valuable to others.

Key terms: influence without authority, positional power, reciprocal relationships

15.1.1 The pattern: Act, measure, share

The section shows how a developer can influence change without authority by trying a safe improvement, measuring and sharing its results, and letting others adopt it voluntarily.

Key terms: act, measure, share, influence without authority, permission, approval gate, reversible, queue time, WIP, credibility, Kaizen, buy-in

15.2 Micro coaching

This section introduces micro coaching as brief, everyday interactions that help teammates learn beyond the immediate fix.

Key terms: micro coaching, feedback, error boundary, PR review comment, Slack reply, pairing session

15.2.1 Micro coaching framework

This section teaches a four-step micro-coaching framework for turning a brief code-review comment into a reusable improvement in developer practice.

Key terms: what, why, how, pattern, Andon, 5 Whys, standard work, quality at the source, dependency on the reviewer

15.2.2 From micro coaching to coaching kata

This section adapts the Coaching Kata into a repeatable peer-coaching habit that can spread learning through everyday software work.

Key terms: Improvement Kata, Coaching Kata, micro coaching, what/why/how/pattern, yokoten, PR review

15.3 Demonstrating value through small wins

This section shows how measurable small improvements gain support for larger change when teams make their progress—and their unsuccessful experiments—visible.

Key terms: small wins, friction, delivered improvements, weekly wins, local optimization, communication rhythm, visual management, revert, experiment, metrics

15.4 Scaling improvements across teams

The section explains how to scale a Lean improvement by preserving its purpose while letting each team adapt and test its implementation.

Key terms: WIP limits, context switching, cycle time, extract the principle, target context, co-design, experiment, baseline, standard work, standardized work

15.5 Handling resistance to change

The section treats resistance to change as information and explains how to respond to experience-based, fear-based, and identity-based concerns.

Key terms: resistance, experience-based resistance, fear-based resistance, reversibility, metrics, revert, identity-based resistance, jidoka, judgment, higher-value work

15.5.1 We have always done it this way

The section shows how to respond to resistance to a Lean change without dismissing people’s expertise or forcing adoption.

Key terms: automated code formatting, PR reviews, time boxed experiment, pre-commit hook, real objection, opt out, partial adoption, slow adoption

15.6 Building a culture of continuous learning

The section shows how teams turn incidents and everyday work into shared learning by updating standard work and making the reasons for changes visible.

Key terms: incident review, root cause, standard work, 5 Whys, decision log, standards wall, learning backlog, post-feature retrospectives, code archaeology sessions

15.7 The change agent’s toolkit

The section presents Lean change as a repeatable, measured cycle, explains common ways change agents undermine it, and shows how small wins can become a team habit.

Key terms: change agent, baseline, adoption, standardize, observation bias, sharing, pulling, mandating, compliance, small improvements

15.8 Exercise: Plan your first team Kaizen event

This exercise guides a team through a small, measurable Kaizen event and emphasizes repeating that improvement cycle as a habit.

Key terms: Kaizen event, friction point, baseline, problem statement, people who do the work, standard work, Kaizen

15.9 Summary

Concepts explained in this chapter

← Chapter 14: Personal Lean: Building habits

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.