problem-framing-canvas

Problem framing is the process of clarifying and reframing problem statements to ensure product teams solve the root cause. It helps product management by surfacing assumptions and biases before solution ideation, preventing teams from building features that miss underlying user issues.

To use the problem framing canvas, guide your team through three phases: Look Inward to identify assumptions and biases, Look Outward to map stakeholders and impact, and Reframe to restate the problem and generate actionable How Might We questions for ideation.

You should use problem framing techniques during product discovery before solution ideation begins. It is essential when stakeholders present vague requests like improving user engagement, ensuring you systematically uncover underlying issues and define a precise problem statement.

The best way to write actionable How Might We questions is by first analyzing user research to identify core assumptions and stakeholder impacts, then reframing the initial problem statement through the Look Inward and Look Outward phases to generate targeted questions.

Yes, you can use problem framing for complex product issues like mobile retention drops. The structured canvas process helps you systematically uncover underlying issues, validate stakeholder assumptions, and restate the problem to ensure your solutions address the actual root cause.

Problem framing helps mitigate cognitive bias in product decisions by explicitly guiding teams through a Look Inward phase to surface and challenge assumptions, ensuring solutions are based on validated root causes rather than untested biases.