liveBook · Manning

Chapter 8: Root cause thinking for developers

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

The introduction uses a recurring payment-service failure to show why developers should trace evidence to a changeable root cause instead of repeatedly restoring service with temporary fixes.

After this chapter you will be able to

What it builds on

Section by section

Introduction

The introduction uses a recurring payment-service failure to show why developers should trace evidence to a changeable root cause instead of repeatedly restoring service with temporary fixes.

Key terms: symptom-fix cycle, underlying fault, root cause, root cause thinking, structured questioning techniques, cause chains

8.1 Going beyond symptoms to the root cause

This section explains when to investigate a recurring failure and how to address its root cause rather than repeatedly fixing its symptoms.

Key terms: root cause thinking, symptom fix, fix, prevent, detect, schema migration, CI lint, observability check

8.2 Lean problem-solving tools and techniques

This introduction explains why a small set of practical Lean tools is enough for most software root-cause investigations.

Key terms: Lean problem-solving toolbox, gemba, root cause investigations

8.2.1 The 5 whys

This section shows how to use the 5 Whys to move from an incident symptom to a changeable cause, while checking every answer against evidence.

Key terms: 5 Whys, countermeasure, API boundary, missing requirement, observed behaviour, logs, metrics, traces, reproducible test, evidence

8.2.2 Fishbone diagrams

This section explains how a fishbone diagram broadens a software investigation across possible causes before the team narrows its focus.

Key terms: fishbone, Ishikawa diagram, cause and effect diagram, spines, 6Ms, structured sweep, Process, Technology, runtime

8.2.3 Pareto analysis

This section explains how Pareto analysis ranks recurring software failures so teams investigate the highest-impact problem first.

Key terms: Pareto analysis, rank by frequency, top contributor, 5 Whys, fishbone, root cause

8.2.4 Is/Is not

This section explains how Is/Is Not analysis uses the boundaries of an inconsistent failure to narrow down its cause.

Key terms: Is/Is Not analysis, boundaries, dimensions, environment, timing, user segment, platform, data characteristics, feature flag

8.2.5 Combining them: Root cause analysis

The section shows how four Lean tools work together to narrow a problem, trace its cause, check for related failures, and prioritize a fix.

Key terms: Root Cause Analysis (RCA), Is/Is Not, 5 Whys, fishbone, Pareto, Pro plan, EU region, company_logo, migration spec, Process

8.3 Debugging at the gemba

This section shows how to debug at the software gemba by observing the running system, finding the conditions behind a failure, and verifying that a root-cause fix works.

Key terms: software gemba, observability tooling, reproduce at the gemba, production environment, staging setup, Is/Is Not, 5 Whys, fishbone, Pareto, stack trace

8.4 When AI introduces non-RCA fixes

This section shows how an AI-generated patch can hide a bug’s symptom and argues for human root cause analysis before using AI to produce a fix.

Key terms: retry loop, race condition, create_test_user(), await, 5 Whys, RCA, gemba, hypothesis, fix-prevent-detect test, symptom fix

8.5 Countermeasures, not quick fixes

The section explains how to turn root cause analysis into durable countermeasures rather than leaving a quick fix in place.

Key terms: countermeasure, quick fix, fix-prevent-detect, observability and alerting, standard work, automated checks, process changes, architectural changes, quick fixes, countermeasures

8.6 A3 reports: Structured, blameless problem solving

This section explains how a concise, blameless A3 report communicates a root cause analysis, its countermeasures, and the plan for checking whether they worked.

Key terms: A3 report, one page, Root Cause Analysis, Countermeasures, Background, Current state, Goal, Implementation plan, Follow-up, Learnings

8.7 RCA beyond your value stream

The section extends root cause thinking beyond code to product decisions and operational processes, showing why fixing a persistent cause matters more than polishing a symptom.

Key terms: root cause thinking, symptoms, causes, 5 Whys, onboarding flow, naming, product decision, Is/Is Not analysis, shared database, coupling

8.8 Exercise: Write an A3 report for a production issue

The exercise guides readers to write a concise A3 report for a real issue, test its countermeasures, and share and act on the analysis.

Key terms: A3 report, Root Cause Analysis, Countermeasures, RCA tools, one-page A3, sharp enough, countermeasure, quick fix, root cause, A3

8.9 Summary

Where this is used later

Concepts explained in this chapter

← Chapter 7: Taming legacy code Chapter 9: Measuring what matters →

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.