# Problem Framing

The practice of defining which problem a team will address, for whom, in what context, and with what outcome and constraints.

- Type: practice
- Domain: Strategy & discovery
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/problem-framing/>)

## What it means

Problem framing turns a broad situation, symptom, or request into a useful design challenge. A strong frame identifies affected people, relevant context, evidence, desired change, boundaries, and open questions without quietly prescribing a single solution.

## Why it matters

The frame controls where a team looks and what it considers possible. A narrow or solution-shaped frame can waste excellent execution, while a frame that is too broad produces generic ideas. Making the frame explicit allows assumptions and stakeholder differences to be examined early.

## When to use it

Use it at the start of discovery, when a roadmap item arrives as a feature request, when research contradicts the original brief, or when stakeholders propose incompatible solutions. Revisit it whenever new evidence changes the perceived problem.

## How it works

1. Separate observed evidence from interpretations, requests, and preferred solutions.
2. Identify the people, situations, behaviors, and outcomes that matter.
3. Map system constraints, incentives, stakeholders, and potential harms.
4. Write several candidate frames at different levels of scope.
5. Choose a frame that is actionable yet leaves room for multiple responses.
6. State assumptions and questions that discovery must resolve.

## A practical example

A marketplace request to “add seller ratings” is reframed after research. Buyers actually struggle to judge whether a seller will dispatch on time. The team frames the challenge as helping buyers assess fulfillment reliability before purchase, opening options beyond a single reputation score.

## Where it breaks

Every frame includes some perspectives and excludes others; it is never neutral. Teams can endlessly reframe to avoid commitment, or wordsmith a statement without gathering evidence. Complex structural problems may not be responsibly reduced to one user-centered challenge.

## Common mistakes

- Writing the proposed feature into the problem statement.
- Framing around an internal metric without describing customer context.
- Treating the first frame as fixed after new evidence appears.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/problem-framing/#visualization-problem-framing>)

## Sources

1. [Design Project Scoping Guide](<https://dschool.stanford.edu/tools/design-project-scoping-guide>) — Stanford d.school · Institutional method guide
2. [How Might We Questions](<https://dschool.stanford.edu/tools/how-might-we-questions>) — Stanford d.school · Institutional method guide

## Related topics

- [Double Diamond](<https://wiki.soroush.uk/topic/double-diamond/>)
- [Design Thinking](<https://wiki.soroush.uk/topic/design-thinking/>)
- [Product Discovery](<https://wiki.soroush.uk/topic/product-discovery/>)
