Five Whys
The Five Whys is a root-cause analysis technique that repeatedly asks why a problem occurred to trace it toward underlying causes.
Architecture Modernization: Socio-technical alignment of software, strategy, and structure
The 5 Whys is a root-cause analysis technique that repeatedly asks why to trace a stated problem toward underlying causes.
- How it is used
- Uses repeated why questions to deepen a listening session around a specific modernization concern.
- How deep it goes
- Defines the questioning pattern and works through an onboarding concern, without prescribing a formal cause-validation process.
- Examples
- Traces slow agent onboarding through difficult tools and developer-built interfaces to the absence of UX specialists for internal tools.
- What you can do after
- Practice/perform it to pursue a specific concern beyond its initial symptom while keeping the interviewee informed.
Build High Value Software Systems
A root-cause analysis technique that repeatedly asks why a problem occurred, using each answer to guide the next question.
- How it is used
- Traces recurring software failures past symptom fixes toward a change that prevents recurrence.
- How deep it goes
- Works through successive why-questions and an evidence rule, stopping at a changeable cause rather than a fixed question count.
- Examples
- Uses failed uploads and a flaky asynchronous database test to contrast cause-directed fixes with larger queues and retries.
- What you can do after
- Practice/perform an evidence-backed cause chain and choose a countermeasure that addresses its changeable cause.
Read how Build High Value Software Systems explains Five Whys →
Machine Learning System Design
A questioning technique that repeatedly asks why to trace a problem toward its underlying origin.
- How it is used
- Clarifies the problem space before teams choose an implementation.
- How deep it goes
- Defines chained why-questions and gives practical prompts, but stops short of prescribing implementation details.
- Examples
- Uses a lead-scoring requirement and questions about purpose, causes, alternatives, metrics, latency, and training samples.
- What you can do after
- Evaluate and understand what to build, why it matters, and which constraints shape the requirement.
Read how Machine Learning System Design explains Five Whys →
The Art of Code
The 5 Whys is an iterative problem-solving method that identifies an issue's root cause by repeatedly asking why.
- How it is used
- Investigates engineering symptoms by tracing successive causes during creative problem-solving and continuous improvement.
- How deep it goes
- Traces one worked database incident through five causal questions and stops at an organizational automation gap.
- Examples
- Uses a slow page, delayed database queries, a dropped users-table index, and manually adapted migration SQL.
- What you can do after
- Diagnose issues by building a stepwise chain from a visible symptom to an underlying cause.
Think Like a CTO
The five whys is an iterative root-cause analysis technique that repeatedly asks why to narrow an observed problem to underlying causes.
- How it is used
- Guides incident investigations toward causes, accountability, and practical prevention rather than stopping at the immediate error.
- How deep it goes
- Narrows causes through repeated questioning and examines training, human factors, planning, and safeguards, but notes that multiple causes may resist a single chain.
- Examples
- Uses accidental production-server deletion, terminal-window confusion, incident records, and conspicuous environment safeguards.
- What you can do after
- Diagnose contributing causes and select prevention measures such as retraining, reviews, documentation, or software guard rails.
Also covered in
- Grokking Software ArchitectureIn early access (MEAP)
- Data-Driven Cybersecurity
- Think Like a Software Engineering Manager
- Automating API Delivery
- Cloud Observability in Action
What to know first
- backup and restoreBackup and restore is the practice of preserving copies of data or system state and using them to recover it after loss, damage, or failure.
Related concepts
- cause analysisused by · Cause analysis is a systematic investigation of the underlying factors that produced a problem, failure, incident, or other outcome.
- root causeaddresses · A root cause is an underlying condition or factor that produces or substantially contributes to an observed problem, failure, or outcome.
- assumptionproduces · An assumption is a proposition or condition provisionally accepted as true or applicable as a basis for reasoning, planning, modeling, or action.
- frameworkkind of · A software framework is a reusable foundation of components, conventions, and supporting mechanisms that structures application development and provides common functionality and extension points.
- debuggingaddresses · Debugging is the systematic investigation of software behavior to identify, understand, and correct defects or unexpected behavior.
Questions about Five Whys
What is Five Whys?
The Five Whys is a root-cause analysis technique that repeatedly asks why a problem occurred to trace it toward underlying causes.
Which Manning books explain Five Whys?
Architecture Modernization: Socio-technical alignment of software, strategy, and structure, Build High Value Software Systems, Machine Learning System Design, The Art of Code and Think Like a CTO.
What should I know before learning Five Whys?
Manning books that teach Five Whys usually introduce backup and restore first.
What is Five Whys a kind of?
Five Whys is a kind of framework. A software framework is a reusable foundation of components, conventions, and supporting mechanisms that structures application development and provides common functionality and extension points.
What is Five Whys also called?
Five Whys is also called 5 whys.
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.




