problem-definition

To define a product problem before building features, you frame the user context, identify Jobs To Be Done (JTBD), and map current alternatives. This generates a structured Problem Definition Pack to ensure team alignment and focus prior to solutioning.

A Problem Definition Pack in product discovery is a comprehensive artifact that articulates problem statements, logs evidence and assumptions, sets scope boundaries, and outlines prototype plans. It transforms vague business signals into actionable product requirements.

To gather requirements for a vague user engagement request, identify the target user, map current alternatives, and define specific success metrics. Logging knowns and unknowns helps validate hypotheses and clarify scope before committing to feature development.

You need to use Jobs To Be Done (JTBD) for scope definition when receiving vague requests that require clear problem framing. JTBD helps articulate the specific user problem and context, allowing you to set guardrails and boundaries to prevent scope creep.

The best way to document assumptions and evidence during product discovery is to log knowns and unknowns systematically alongside your problem statement. This creates a validation trail and directly informs your proposed learning plans and success metrics.

Problem framing does not work effectively without clear success metrics and boundaries. Defining scope guardrails and measurable success criteria is critical to ensure the problem statement remains focused and actionable for the product team.