problem-framing

Problem framing articulates and refines the user problem to prevent solution-first product mistakes. It guides you through creating a structured problem brief covering problem, user, triggers, costs, evidence, and open questions.

Problem framing applies to discovery work and framing sessions to articulate and refine the user problem. It produces a structured problem brief containing sections for the problem, user, triggers, costs, evidence, and open questions.

Run a problem framing workshop by facilitating a step-by-step session to generate multiple alternative problem statements and validation questions. This drives stakeholder alignment across early product ideas before solution development.

This problem framing approach applies recognized frameworks from Teresa Torres, Marty Cagan, and Bob Moesta. It uses these methodologies to guide framework-guided problem framing and structured problem definition.

The best way to structure a problem brief is to create a one-page document detailing the problem, user, triggers, costs, evidence, and open questions. This format ensures structured problem definition for early product ideas.

You need problem definition during discovery work and framing sessions to prevent solution-first product management mistakes. It is required to achieve stakeholder alignment across early product ideas before committing to a solution.