liveBook · Manning

Five Whys

As explained in 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.

Five Whys is a way to go deeper when a listening session stays at a high level. Start with a specific concern and ask “why” repeatedly. Each answer gives you a more focused question; the aim is to uncover underlying conditions and trends relevant to modernization, not to force an instant conclusion. section 4.3.3

Why does onboarding take so long?

An agent-onboarding concern leads to three difficult internal tools. Further questions reveal that developers built their interfaces because the company does not consider internal tools important enough for UX specialists. The conversation has moved from a symptom to an organizational practice worth examining. section 4.3.3

Tell the interviewee before you start using the technique. Repeatedly asking “why” without warning can sound impolite; use the questions to guide a collaborative conversation. section 4.3.3

How Architecture Modernization: Socio-technical alignment of software, strategy, and structure covers it

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 it assumes
Assumes a listening session with a specific concern; teaches the repeated-question pattern from a simple definition.
What you can do after
Practice/perform it to pursue a specific concern beyond its initial symptom while keeping the interviewee informed.
How it connects
Connects listening sessions, agent onboarding, internal tools, user interfaces, and UX specialization.

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 Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.