five-whys

A root-cause analysis using the five-why method enforces a structured five-step questioning chain on a stated technical decision to identify true motives. It classifies each answer explicitly to reveal whether a design choice rests on business value or technical satisfaction.

To run a five-why root-cause analysis for a feature decision, provide a clear initial decision statement and execute the five-step why chain. The Skill enforces no skipping and no circular reasoning while explicitly classifying each engineering answer.

Yes, you can use root-cause analysis to justify process improvements across product development. The five-why questioning chain applies to engineering design choices and feature decisions, documenting findings to distinguish business value from technical necessity.

The best way to prevent circular reasoning during a five-why root-cause analysis is to enforce a structured five-step why chain with explicit classification of each answer. This structured interrogation prevents skipping steps and exposes true root causes.

You should not use a five-why chain for decision analysis when you lack a clear initial decision statement. The method requires a specific stated technical decision or process improvement justification to effectively execute the questioning chain.