problem-statement

A user-centered problem statement articulates who is blocked, what they are trying to do, why it matters, and how it feels. Using a structured narrative template ensures teams align on desired outcomes before jumping to solutions during PRD framing.

A problem framing narrative captures authentic user pain using a persona-centric template of who, what, why, and feelings. You need it during product discovery, prioritization, or design phases to ground your team in real user empathy and desired outcomes.

You frame user problems by applying a persona-centric template covering user identity, goals, blockers, causes, and emotions. Leveraging jobs-to-be-done and user research grounds the narrative in authentic empathy, producing a testable final problem statement.

Yes, this problem framing approach applies directly to product discovery, prioritization, and PRD work. It produces a dedicated context, constraints section, and final concise statement to guide cross-functional alignment across product, design, and engineering teams.

The best way to document context and constraints is through a structured workflow that isolates environmental factors alongside a concise final statement. This ensures your user research outputs remain testable and actionable for downstream product teams.

Teams jump to solutions when lacking a clear problem framing narrative that articulates user blockers and feelings. Drafting a structured persona-centric statement with explicit context and constraints aligns everyone on the actual outcome first.