problem-definition

Problem Definition

Scope

Covers

• Turning a vague idea into a crisp, testable problem definition
• Writing a shareable problem statement (1-liner + expanded)
• Capturing Jobs To Be Done (JTBD) and target segments
• Mapping current alternatives (including non-digital/analog) and “why now / why digital”
• Building an evidence + assumptions log to drive learning
• Defining success metrics + guardrails and clear scope boundaries

When to use

• “Write a problem statement for…”
• “We need to define the problem space / JTBD.”
• “We keep jumping to solutions; help us get clear on the real problem.”
• “Pressure to ‘do AI’ — verify there’s a real pain point first.”
• “Before we write a PRD, align on what problem we’re solving.”

When NOT to use

• You already have an approved problem definition and need a delivery-ready PRD (use writing-prds)
• You need roadmap prioritization across many competing initiatives (use prioritizing-roadmap)
• You need to set company-level strategy/vision (use defining-product-vision)
• You need a competitive landscape analysis as the primary output (use competitive-analysis); this skill references alternatives only to frame the problem
• You’re doing deep research execution (recruiting, interviews, analysis); use this to frame what to learn, not as a substitute for conducting-user-interviews or designing-surveys
• You need to analyze existing user feedback data (use analyzing-user-feedback); this skill frames the problem, not the evidence pipeline

Inputs

Minimum required

• Product/context + target user (or segment hypotheses)
• The triggering signal (customer quotes, data trend, stakeholder request, competitor move)
• The decision to make (e.g., invest now vs later; explore vs stop) + timeline
• Known constraints (tech/legal/privacy/compliance/capacity)

Missing-info strategy

• Ask up to 5 questions from references/INTAKE.md.
• If still missing, proceed with clearly labeled assumptions and list Open questions that would change the decision.