Problem Framing

Distinctions

The act of defining what problem is being solved, for whom, why it matters, and where its boundaries are.
A way to shape the solution space before committing to a solution.
A way to evaluate problem quality: whether a problem is real, painful, important, fundable, and strategically relevant.
A leverage point because choosing or framing the wrong problem can constrain the entire downstream effort.

Problem Framing evaluates and defines the problem before committing to a solution.
It does not determine whether a proposed solution is usable, feasible, or profitable.

Part of product discovery and opportunity evaluation.
Relevant to Customer Discovery because discovery must test not only whether a problem exists, but whether it is worth solving.

Supports Diagnose Before Prescribing by making the diagnosis explicit before intervention.
Reduces Inside-Out Product Development by forcing the team to frame the problem from customer reality rather than internal assumptions.
Strengthens Product Clarity when the product is anchored in a high-quality problem.
Influences Speed Without Direction Is Harmful because speed compounds the consequences of a bad problem frame.
Poor Problem Framing can make an initiative fail from the moment of problem selection, even if the failure only becomes visible later during execution.

From the customer perspective, a high-quality problem is painful enough to motivate change.
From the business perspective, a high-quality problem is valuable enough to fund.
From the product team perspective, a high-quality problem creates focus and helps reject attractive but weak ideas.
From the execution perspective, failure may look like poor delivery, weak adoption, or bad go-to-market.
From the problem-selection perspective, the initiative may have been constrained from the start by choosing a problem that was not worth solving.