problem-framing

To reframe a vague product brief, surface underlying assumptions and use How Might We reformulation to articulate user needs. This prevents premature commitment to specific solutions and ensures the team aligns on the actual problem.

Problem framing in design thinking is the process of distinguishing symptoms from root needs during product discovery. It uses assumption mapping and jobs-to-be-done articulation to transform ambiguous requests into structured, defensible problem statements.

Use assumption mapping and jobs to be done articulation during the discovery and definition phases when teams lack alignment. This approach untangles symptoms from root needs and validates that the resulting problem statement avoids pre-committing to solutions.

Write a How Might We statement by combining point-of-view articulation with user insights to keep possibilities open. This ensures the statement addresses the unmet need without locking the team into a specific feature or solution path.

The best way to turn a feature request into a user need statement is symptom-to-need laddering. This technique questions what is taken on faith, identifies the true user motivation, and rewrites the brief into a single-sentence problem statement.

Yes, use problem framing techniques when teams lack alignment on project scope. By explicitly surfacing assumptions and articulating the user, the need, and the motivating insight, you can converge on a shared, defensible problem definition.