1. Problem phase
The art of understanding before solving.
This is the operational guide for executing Problem Phase — the phase where the team investigates the real problem before thinking about solutions. While the methodology section explains the why and the conceptual foundations, this guide covers the how: the concrete process to follow, the artifacts to produce, the criteria to meet before moving forward, and the failure patterns to watch for.
The Problem Phase workflow
Problem Phase is a structured four-step process that guides the team from identifying a problem to its validated definition. Each step produces a deliverable that feeds the next: the kick-off establishes the actor map and hypotheses, the interviews generate raw findings, the synthesis converts those findings into patterns, and the Problem Statement distills everything into a definition that both users and the Decision Owner recognize as real. Discipline in the sequence is what differentiates a rigorous discovery from a well-intentioned conversation.
1. Discovery Kick-off
Align scope, build the Actor Map, document starting hypotheses, and design the Interview Guide.
Actor Map + Interview Guide2. In-depth interviews
Structured 45-60 min conversations with minimum 5 people who live the problem. Literal note capture without interpretation.
Raw findings3. Findings synthesis
The team groups findings by patterns, identifies tensions and outliers, and distills the real problem emerging from the data.
Synthesis Board4. Problem Statement drafting and validation
Distillation of the problem into a half-page document. Dual validation: resonance with users and viability with the Decision Owner.
Validated Problem StatementThe four artifacts
This phase produces four artifacts that together form the foundation for Phase 2. Each one captures a distinct type of knowledge: who surrounds the problem, what questions to ask, what patterns emerge from listening, and what the distilled definition of the real problem is.
Actor MapInterview GuideSynthesis BoardProblem StatementThe cost of error
Why invest in Discovery? Because fixing a misunderstood problem in Production costs 100x more than fixing it during Discovery. The earlier the error is caught, the cheaper the correction.
This is not theory. It is the most consistent finding in software engineering research: the cost of change grows exponentially with each phase. Discovery is the cheapest moment to be wrong.
What this guide covers
Step by Step
A structured four-step process from kick-off to validated Problem Statement. Each step produces a deliverable that feeds the next.
Anatomy
The seven mandatory elements of a well-crafted Problem Statement. What each element contributes and how to validate it.
Artifacts
Actor Map, Interview Guide, Synthesis Board, and Problem Statement. Templates, formats, and quality criteria for each deliverable.
Gate Review
Six criteria that must all pass before advancing to Phase 2. The checkpoint that prevents carrying a poorly defined problem forward.
Anti-patterns
The most common failure modes in problem discovery. How to recognize them early and what to do when they appear.
Effort
Time investment ranges for teams of different sizes. How to calibrate effort without over-investing or under-investing.
Every hour invested in properly understanding the problem saves weeks of misguided building, rework cycles, realignment meetings, and — above all — the erosion of trust that occurs when a team delivers something nobody needed. If you're dedicating less than 15% of the project's total time to Problem Phase, you're probably investing too little. The sweet spot is between 15% and 25%.