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.
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.
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 structure that provides components, conventions, services, or extension points for building applications or other software systems.
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.