Back to Prompts
Content GenerationClaude Sonnet 4.5
Create Problem Statement
Prompt
You are a product strategist crafting clear problem statements. Define problems precisely to enable better solutions.
**Context:**
{{context}}
**Symptoms/Observations:**
{{symptoms}}
**Who is Affected:**
{{who}}
**Business Impact:**
{{impact}}
Create a problem statement:
---
## Problem Statement
### One-Liner
[One sentence that captures the core problem]
---
### Structured Problem Statement
**For:** [Who experiences this problem]
**Who:** [What they're trying to accomplish]
**The:** [Current solution or workaround]
**Is a problem because:** [Specific pain or failure]
**A successful solution would:** [Desired outcome without prescribing how]
---
### Expanded Problem Description
**The current situation:**
[2-3 sentences describing what's happening now]
**Why this is a problem:**
[Specific pain points and their consequences]
**Evidence:**
- [Data point or observation]
- [Data point or observation]
- [Data point or observation]
**Root cause hypothesis:**
[Underlying reason this problem exists]
---
## Impact Analysis
### Quantified Impact
| Metric | Current State | Cost/Impact |
|--------|---------------|-------------|
| [Metric] | [Value] | [$ or time or other] |
### Qualitative Impact
- [User frustration or experience impact]
- [Business or brand impact]
### Who Cares
| Stakeholder | Why They Care | Priority |
|-------------|---------------|----------|
| [User type] | [Impact on them] | High/Med/Low |
| [Business team] | [Impact on them] | High/Med/Low |
---
## Problem Boundaries
**In scope:**
- [What's included in this problem]
**Out of scope:**
- [Related but separate problems]
**Assumptions:**
- [What we're assuming to be true]
**Constraints:**
- [Limitations we must work within]
---
## Validation Needed
Questions to answer before solving:
- [ ] [Question about the problem]
- [ ] [Question about the users]
- [ ] [Question about the impact]
Research to conduct:
- [Method]: [What we'll learn]
---
## Success Criteria
**We'll know we've solved this when:**
- [Measurable outcome]
- [Observable behavior change]
**Metrics to track:**
| Metric | Current | Target |
|--------|---------|--------|
---
## Anti-Patterns Avoided
✓ Problem, not solution (no "We need a...")
✓ Specific, not vague ("Users struggle" → "Users spend 5 minutes...")
✓ Observable, not assumed (backed by evidence)
✓ Focused, not boiling the ocean
---
A well-defined problem is half-solved. Resist jumping to solutions.Example
Input
Context: SaaS onboarding flow Symptoms: 60% of signups never complete setup, support tickets about 'getting started', users abandon at step 3 Who: New users in first 7 days Impact: Low activation, high CAC payback period
Output
## Problem Statement ### One-Liner New users abandon onboarding before experiencing core product value, resulting in 60% never reaching activation. ### Structured Problem Statement **For:** New signups in their first 7 days **Who:** Are trying to set up the product for their team **The:** Current 5-step onboarding flow **Is a problem because:** Users get stuck at the team invitation step (step 3) and leave without completing setup **A successful solution would:** Get 80%+ of users to complete setup and perform their first key action...