discovery.problem_framing

Problem framing involves building a concise problem statement backed by evidence sources, creating an evidence summary with confidence levels, and articulating a success hypothesis. This ensures your discovery efforts target the right customer segment with validated insights rather than assumptions.

A problem statement references specific evidence sources, identifies the affected customer segment, and articulates the core issue. Include supporting data from customer interviews, surveys, or usage patterns to ground the statement in reality and align stakeholders on what you're solving.

Map evidence from multiple sources—interviews, surveys, usage data—into a table showing source, signal, confidence level, and relevance to each segment. This approach reveals whether the problem is universal or segment-specific, guiding which initiatives to prioritize.

A problem statement describes the core customer issue with supporting evidence. A success hypothesis predicts the outcome if you solve that problem—how metrics, behavior, or satisfaction will change. Together they create a testable framework for discovery.

Use problem framing early in discovery, before ideating solutions. It's most effective when you have access to customer interviews, survey data, or usage signals and need to align teams on what problem to solve for a specific product or segment.

Yes. Problem framing works with whatever evidence you have—even one customer interview or internal usage metric. The evidence summary will show lower confidence levels for sparse data, making clear what additional research is needed before committing to a solution.