Chapter 15: Leading Lean change
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
- People Side of Lean Change. Explain why a technically sound improvement may fail to change a team's practices, using the stalled deployment-automation PR as an example.
- Developer Led Improvement Approach. Describe the chapter's proposed starting point for change and contrast it with imposed change programs.
- Influence through visible improvement. Distinguish authority from influence and explain how a developer can encourage change without a leadership title. Describe why improving your own work and showing its value is more persuasive than starting with a top-down framework.
- Act measure share pattern. Trace how Eimear improved staging deploys by making a working change, measuring its effect, and sharing the results without pressuring the team to adopt it.
- Permission boundary for experiments. Distinguish an improvement someone can try without permission from a change that needs buy-in, and explain why unnecessary approval gates slow experimentation.
- Coaching versus directive feedback. Distinguish a directive PR comment from micro coaching in the dashboard example, and explain how coaching helps the developer apply the lesson in future work.
- Four-step micro-coaching framework. Explain how a micro-coaching comment moves from what to why to how to pattern, using the missing error-handling example.
- Peer Coaching Kata. Explain how the Coaching Kata is adapted for software teams: peers use a repeatable micro-coaching routine rather than relying on a manager to solve problems.
- Coaching Embedded in Daily Work. Describe how repeated micro coaching in ordinary team interactions can spread coaching capability and reduce recurring review problems.
- Measurable small wins. Explain how to find a first small win in recurring friction and why a chain of modest, measured improvements can build support for larger changes.
- Visible improvement momentum. Describe how a regular weekly wins message turns individual improvements into visible team progress, including the roles of cumulative measures and recognition.
- Principle Versus Local Practice. Explain why a successful practice should not be copied unchanged across teams, using the WIP-limit example to show how different work patterns change its effects.
- Contextual Adoption Sequence. Describe the sequence for bringing a Lean practice to another team: identify the problem it solves, understand the target team’s context, co-design a local version, and test it as an experiment.
- Resistance as useful information. Explain why pushback should be treated as a signal rather than a personality flaw, and describe how to respond when it comes from a failed past attempt.
- Reversible trials for fear. Describe how a limited, reversible trial addresses fear-based resistance.
- Identity concerns and human judgment. Explain why AI can provoke identity-based resistance and how the section reframes a skilled developer's role.
- Respectful Reframing and Experimentation. Explain how David used review data to reframe automated formatting as a way to free senior developers for substantive review, then tested it in a time-boxed experiment.
- Resistance Beyond the Data. Describe why clear data may not resolve resistance and how to respond by uncovering the real objection, allowing opt-outs where feasible, and giving adoption time.
- Incident to standard work cycle. Trace how a team reviews an incident, identifies its root cause, looks for the same problem elsewhere, and promptly changes standard work to prevent recurrence.
- Visible shared learning records. Describe how decision logs, a standards wall, and a learning backlog make incident lessons available to the team, including how backlog items are prioritized.
- The change agent cycle. Trace the change agent’s sequence from spotting friction and measuring a baseline through building a fix, measuring its result, sharing evidence, adoption, and standardization. Explain that the work is to apply existing Lean practices in order rather than invent new tools.
- Four change agent failure modes. Explain why skipping a baseline, fixing the most noticeable annoyance, failing to share, and mandating adoption can each undermine Lean change.
- Focused and measurable event. Describe how to choose and scope a team Kaizen event: select one recurring process friction point, record a baseline, and set a target narrow enough for a half-day effort.
- Measurement and follow-through cycle. Trace what happens after the event: remeasure the same metric, share the result, and standardize an improvement or revert an unsuccessful change. Explain why repeating this cycle matters more than the tool names.
What it builds on
- Limiting work in progress (chapter 6) · The idea of work in progress, applied here to pending proposals.
- What Kaizen actually means (chapter 10) · The idea of Kaizen as small, continuous improvement.
- By the people who do the work (chapter 10) · The principle that the people doing the work participate in designing improvements.
- Standard work for coding (chapter 4) · The book’s earlier discussion of standard work for coding.
- The 5 whys (chapter 8) · Using the 5 Whys to trace an incident's root cause.
- Post-incident reviews as kaizen triggers (chapter 12) · Treating post-incident reviews as opportunities for improvement.
- Tracking decisions (chapter 11) · The architectural decision-log format, here applied to process decisions.
- Retrospectives as structured Kaizen (chapter 10) · Retrospectives as a structured improvement practice.
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.
- People Side of Lean Change: Explain why a technically sound improvement may fail to change a team's practices, using the stalled deployment-automation PR as an example.
Why it matters: A useful improvement can stall if no one helps the team adopt it. - Developer Led Improvement Approach: Describe the chapter's proposed starting point for change and contrast it with imposed change programs.
Why it matters: You can begin influencing change from your own work without waiting for formal authority.
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.
- Influence through visible improvement: Distinguish authority from influence and explain how a developer can encourage change without a leadership title. Describe why improving your own work and showing its value is more persuasive than starting with a top-down framework.
Why it matters: You can help a team change without waiting for permission to lead a formal transformation.
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.
- Act measure share pattern: Trace how Eimear improved staging deploys by making a working change, measuring its effect, and sharing the results without pressuring the team to adopt it.
Why it matters: A working example and credible results can invite change even when you cannot mandate it. - Permission boundary for experiments: Distinguish an improvement someone can try without permission from a change that needs buy-in, and explain why unnecessary approval gates slow experimentation.
Why it matters: Knowing which experiments are safe to start yourself avoids waiting without treating every change as yours to make. - Compounding credibility from small wins: Explain how repeated small improvements with transparently measured results can build credibility for later changes that need buy-in.
Why it matters: A record of useful changes makes future proposals easier for others to trust.
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.
- Coaching versus directive feedback: Distinguish a directive PR comment from micro coaching in the dashboard example, and explain how coaching helps the developer apply the lesson in future work.
Why it matters: A review comment can build a teammate’s judgment rather than merely request a one-time fix. - Everyday coaching opportunities: Explain where micro coaching can happen on a software team and why it does not require formal credentials or scheduled sessions.
Why it matters: Seeing ordinary interactions as coaching opportunities makes skill development part of daily work.
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.
- Four-step micro-coaching framework: Explain how a micro-coaching comment moves from what to why to how to pattern, using the missing error-handling example.
Why it matters: A short comment can help a developer address both the immediate defect and the conditions that would produce it again. - Capability over reviewer dependence: Justify why a coaching comment should reach the pattern step rather than only tell the developer what to fix.
Why it matters: The aim is to build quality into future work, not just correct one pull request.
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.
- Peer Coaching Kata: Explain how the Coaching Kata is adapted for software teams: peers use a repeatable micro-coaching routine rather than relying on a manager to solve problems.
Why it matters: Coaching can become a practiced habit between colleagues, not a role reserved for managers. - Coaching Embedded in Daily Work: Describe how repeated micro coaching in ordinary team interactions can spread coaching capability and reduce recurring review problems.
Why it matters: Small coaching exchanges can develop teammates' abilities without setting up a separate mentoring program.
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.
- Measurable small wins: Explain how to find a first small win in recurring friction and why a chain of modest, measured improvements can build support for larger changes.
Why it matters: A modest improvement with visible results can make a stronger case for change than a large proposal alone. - Visible improvement momentum: Describe how a regular weekly wins message turns individual improvements into visible team progress, including the roles of cumulative measures and recognition.
Why it matters: Making improvement visible helps the team see a continuing trajectory rather than a collection of isolated fixes. - Visible unsuccessful experiments: Explain why the team should share and acknowledge a reverted change when its metrics do not improve.
Why it matters: Being open about an experiment that did not work keeps the team willing to try changes that might produce larger gains.
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.
- Principle Versus Local Practice: Explain why a successful practice should not be copied unchanged across teams, using the WIP-limit example to show how different work patterns change its effects.
Why it matters: A practice can preserve its intended benefit across teams without imposing the same rule on everyone. - Contextual Adoption Sequence: Describe the sequence for bringing a Lean practice to another team: identify the problem it solves, understand the target team’s context, co-design a local version, and test it as an experiment.
Why it matters: This gives teams a way to spread improvements without turning them into one-size-fits-all mandates. - Standard Work Distinction: Distinguish a team’s context-specific standard work from standardized work imposed identically on every team.
Why it matters: The distinction explains why sharing an improvement does not require identical team procedures.
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.
- Resistance as useful information: Explain why pushback should be treated as a signal rather than a personality flaw, and describe how to respond when it comes from a failed past attempt.
Why it matters: Listening to the reason for pushback can help you design a better change. - Reversible trials for fear: Describe how a limited, reversible trial addresses fear-based resistance.
Why it matters: A reversible experiment lets people test a change without feeling locked into it. - Identity concerns and human judgment: Explain why AI can provoke identity-based resistance and how the section reframes a skilled developer's role.
Why it matters: Framing automation around human judgment addresses the concern that AI makes a developer's expertise worthless.
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.
- Respectful Reframing and Experimentation: Explain how David used review data to reframe automated formatting as a way to free senior developers for substantive review, then tested it in a time-boxed experiment.
Why it matters: A respectful experiment can make a proposed change easier to judge without treating colleagues’ past work as a mistake. - Resistance Beyond the Data: Describe why clear data may not resolve resistance and how to respond by uncovering the real objection, allowing opt-outs where feasible, and giving adoption time.
Why it matters: Addressing the concern behind an objection helps change become something the team owns rather than endures.
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.
- Incident to standard work cycle: Trace how a team reviews an incident, identifies its root cause, looks for the same problem elsewhere, and promptly changes standard work to prevent recurrence.
Why it matters: A fix protects one incident; a shared preventive practice can protect the team from the next one. - Visible shared learning records: Describe how decision logs, a standards wall, and a learning backlog make incident lessons available to the team, including how backlog items are prioritized.
Why it matters: Visible records let current and future teammates use a lesson rather than depend on the person who discovered it. - Learning without an incident: Explain how post-feature retrospectives and code archaeology sessions produce learning during normal work.
Why it matters: Routine reflection can reveal improvements and missing knowledge before either causes an incident.
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.
- The change agent cycle: Trace the change agent’s sequence from spotting friction and measuring a baseline through building a fix, measuring its result, sharing evidence, adoption, and standardization. Explain that the work is to apply existing Lean practices in order rather than invent new tools.
Why it matters: The sequence turns a local fix into an evidence-backed improvement others can choose to adopt. - Four change agent failure modes: Explain why skipping a baseline, fixing the most noticeable annoyance, failing to share, and mandating adoption can each undermine Lean change.
Why it matters: Avoiding these failures helps a useful improvement earn influence and lasting ownership. - From small wins to habit: Describe how measured and shared small improvements can gradually lead to teammate adoption, contributions from others, and a team-owned improvement habit.
Why it matters: Early silence need not mean failure if measured wins are building toward a team-owned practice.
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.
- Focused and measurable event: Describe how to choose and scope a team Kaizen event: select one recurring process friction point, record a baseline, and set a target narrow enough for a half-day effort.
Why it matters: A narrow problem and a starting number let the team tell whether its effort helped. - Event time and participants: Describe how to schedule the event and who should take part in the improvement work.
Why it matters: The people closest to the process are the ones positioned to improve it. - Measurement and follow-through cycle: Trace what happens after the event: remeasure the same metric, share the result, and standardize an improvement or revert an unsuccessful change. Explain why repeating this cycle matters more than the tool names.
Why it matters: Following through turns a one-off event into a tested improvement the team can keep or revise.
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
- standard workA single prescribed method applied across teams regardless of differences in their work contexts.
- learning principleA Lean principle of using feedback, operational experience, and failures to improve the delivery system.
- baselineAn initial measurement of a process or system that provides a reference for comparison with later measurements.
- kaizen eventA focused, time-boxed effort in which a team works intensively to improve a specific process problem.
- automationThe use of software or machines to perform tasks with reduced manual intervention.
- jidokaA Lean production approach that builds quality into processes by stopping when abnormalities occur and preventing defects from proceeding.
- experimentationA deliberately limited activity undertaken to learn about an uncertain idea or approach.
- architecture decision recordAn architecture decision record is a concise document that records an architectural decision, its rationale, and its consequences.
- inventoryInventory is the waste of work items, information, or decisions that have been started or accumulated but are not yet needed downstream.
- waiting wasteLean waste caused by people or work items being unable to proceed while awaiting input, feedback, a decision, or another process step.
- feedbackInformation about the effects or results of work that can guide subsequent decisions or changes.
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.
