liveBook · Manning

Five Whys

As explained in The Art of Code

The 5 Whys is an iterative problem-solving method that identifies an issue's root cause by repeatedly asking why.

Five Whys investigates a visible engineering symptom by repeatedly asking “Why?” until the chain reaches an underlying wrong assumption, design flaw, or team practice. section 10.3.3

Tracing a slow page

Why is the page slow? Database requests take longer. Why? An index disappeared during a schema update. Why? The migration recreated the table without it. Why? Developers manually adapt SQL per environment. Why? The project has no standard schema-migration tool. The investigation moves from symptom to an automation gap. section 10.3.3

Use five questions as a guide, not a rigid limit: stop when the underlying cause is clear, and seek documentation, colleagues, forums, or verified AI assistance when the investigation needs outside input. section 10.3.3

How The Art of Code covers it

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 it assumes
Assumes a clearly understood problem and context, while teaching the investigation method from its basic question onward.
What you can do after
Diagnose issues by building a stepwise chain from a visible symptom to an underlying cause.
How it connects
Connects root cause analysis, continuous improvement, database migration, schema design, and automation.
Cover of The Art of Code
liveBookmanning.com
Read The Art of Code on liveBook Get the book at manning.com

Also explained in

Compare how 4 books explain Five Whys →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of The Art of Code. The section links point to the parts of the book it draws on.