Five Whys is a problem-space technique that stacks “why?” questions to move beyond an apparent request and identify the problem’s underlying origin before implementation begins. section 2.1
Use the questions to clarify what should be built and why:
- Why do we need the solution, and what problem does it solve? section 2.1
- Why does the problem occur, and what alternatives are known? section 2.1
- Why must the solution work within constraints such as metrics, latency, or training-sample limits? section 2.1
From request to underlying need
A request for a lead-scoring tool becomes more precise by asking what problem it solves, when scores are needed, and why the stated operational constraints matter. The resulting requirement may specify scores before Monday sales-planning meetings. section 2.1
Figure 2.1 An experienced engineer always handles the problem space first with specifying questions.
Use the problem-space diagram to distinguish specifying questions from premature solution design. section 2.1
