Extra-Why Problem Distillation
Push past surface answers until the underlying problem is clear.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 99%
Extra-Why Problem Distillation uses persistent questioning to move from a proposed action to the underlying problem. A teammate asks why a belief, build request, or investment is justified, then rejects answers that merely repeat the proposal or offer surface reasoning. Each round must connect evidence, cause, and desired outcome more clearly. The questioning may feel uncomfortable, but a high-functioning team treats that discomfort as part of rigorous collaboration when the intent is to improve the work. Once the simplest defensible problem statement is explicit, the team can evaluate multiple solutions rather than defending the first idea presented. The method counters a common failure mode: becoming solution obsessed and inventing reasons to support a preferred implementation.
Origin
Extracted from Marketing Against The Grain through Kieran Flanagan's description of HubSpot product leader Nicholas Holland repeatedly asking the uncomfortable extra why.
Core principles
- 01A clear problem must precede a good solution.
- 02Surface explanations often conceal unsupported assumptions.
- 03Constructive discomfort improves reasoning when intentions are sound.
- 04Teams should be problem obsessed rather than solution obsessed.
How to run it
- 1
State the Proposal
Describe the action, feature, or investment being requested without treating it as self-justifying.
Pro tip Write the proposal separately from its rationale.
Watch out A polished solution can make an untested premise feel true.
- 2
Ask the Extra Why
Ask why the proposal is necessary and continue when the first response remains superficial.
Pro tip Use a curious tone while maintaining a high standard for the answer.
Watch out Aggression can turn useful pressure into interpersonal threat.
- 3
Connect Evidence and Outcome
Require the explanation to identify evidence, the causal problem, and the outcome that matters.
Pro tip Ask what would be observed if the problem were real.
Watch out Opinions repeated with greater confidence are not stronger evidence.
- 4
Distill the Problem
Express the simplest clear problem without embedding a preferred solution in its wording.
Pro tip Test whether several different solutions could address the statement.
Watch out A problem statement that names the feature to build is probably still a solution.
- 5
Evaluate Solutions
Generate and compare possible responses only after the problem is understood.
Pro tip Include the option of changing nothing if the evidence is weak.
Watch out Do not let the original proposal receive automatic priority.
In the wild
A product leader repeatedly asks why engineers should build a requested feature. The requester moves from a surface preference to evidence about a customer obstacle, the business consequence, and the outcome that needs to change. Only then does the team discuss implementation.
→ Engineering investment is tied to a clear problem rather than a solution in search of justification.
Common mistakes
Accepting the First Why
The initial answer often restates the proposal rather than revealing the causal problem.
Using Discomfort as an Excuse to Stop
Avoiding all tension protects weak reasoning and produces lower-quality decisions.
Interrogating for Status
The method fails when questions are intended to humiliate or dominate rather than clarify the work.
Is it for you?
Best for
It is best for product, strategy, and investment discussions where shallow assumptions can trigger expensive work.
Not ideal for
It is not ideal for emergencies requiring immediate action before a full causal investigation is possible.
From the transcript
“And what he's really good at is like asking you that extra why that's an uncomfortable, like that's uncomfortable for most people to ask.”
“Most people in this world are solution obsessed and not problem obsessed.”
“And you're saying do the hard work, have the debate, have the conversation around getting to the crystal clear problem.”
From the episode
8 Leadership Habits You Need To Make $1 Billion (#146)