pm-problem-framing

To turn a vague brief into clear problem framing, identify target users, core jobs, obstacles, and success metrics. Specifying non-goals and target scenarios prevents early jumps to solutions and anchors product discussions.

Problem framing in product management defines the exact product problem by reconstructing current workarounds and justifying why now. It is needed to prevent teams from jumping to solutions before understanding user obstacles and scope.

Define non-goals and success metrics for product scope by establishing measurable criteria and explicit boundaries. This enforces concrete guardrails, ensuring required deliverables guide scoped prototyping and team handoffs.

You can use scenario analysis to identify user obstacles by anchoring target scenarios. Reconstructing the current job and existing workarounds surfaces exact obstacles, providing rationale for why the product is needed now.

Problem framing works for normalizing ambiguous user research requirements by extracting target users and jobs from briefs. It translates raw research context into precise product problems with measurable success criteria.