Framing Problem Statement
---
id: prompt-framing-problem-statement
type: discovery
phase: framing
name: "Problem Statement Framing"
version: 1.0.0
tags: [framing, problem-statement, definition]
lens_rules: [empathy_first, value_over_noise, bias_toward_action]
---
# Problem Statement Framing
## Input Requirements
- **Initial problem**: The raw problem or opportunity description
- **User context**: Persona or user description
- **Business context**: Organizational goals and constraints
- **Research artifacts**: Pain points, competitor analysis (optional)
## Instructions
### Step 1: Problem Deconstruction
Deconstruct the initial problem into these components:
| Component | Current Understanding | What's Missing |
|-----------|----------------------|----------------|
| Who is affected | | |
| What is the symptom | | |
| What is the root cause | | |
| When does it happen | | |
| Where does it happen | | |
| Why does it matter | | |
| How is it measured | | |
### Step 2: Draft Problem Statements
Write 2-3 alternative problem statements using these formats:
**Format A — User-centered**:
> [User persona] needs [user need] because [insight].
**Format B — Outcome-focused**:
> The problem is that [current situation], which causes [negative impact]. Success means [desired outcome].
**Format C — Gap-based**:
> Despite [current solutions/tools], users still [unmet need] because [root cause].
### Step 3: Validation Criteria
For the selected problem statement, define:
1. **How would we know this problem is real?** (Evidence requirement)
2. **How would we know it's solved?** (Success metric)
3. **What would invalidate this framing?** (Falsification test)
Include a concrete example of what success looks like:
> *If we solve this problem, [persona] will be able to [do something] in [timeframe] instead of [current situation].*
### Step 4: Next Action
- **Target artifact**: Opportunity Canvas (`.skillweave/templates/discovery/opportunity-canvas.md`)
- **Suggested next step**: Share problem statement with 3 stakeholders for validation
## Output Format
Markdown document with problem deconstruction table, 2-3 alternative problem statements, selected statement with rationale, validation criteria, and example success scenario.when to use it
Community prompt sourced from the open-source GitHub repo LangeVC/skillweave (NOASSERTION). A "Framing Problem Statement" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
roleplaycommunitygeneral
source
LangeVC/skillweave · NOASSERTION