Discover Opportunities
Overview
Find real opportunities by reasoning from first principles and Jobs-To-Be-Done (JTBD). Focus on the user's job, context, and constraints before any solution ideas.
Position in Workflow
Step 2 of product strategy workflow:
/discover-outcomes - Define outcomes
/discover-opportunities - Identify opportunities (THIS)
/ideate-solutions - Explore solution concepts
/discover-assumptions - Validate with experiments
Inputs (ask if missing, max 5)
- Target user / segment
- Trigger and context (when the job arises)
- Desired outcomes (time, money, risk, effort, emotion)
- Current alternatives / workarounds
- Non-negotiable constraints (budget, regulation, tech, org)
Workflow
- Frame the jobs
- Define the core job as verb + outcome (not a solution).
- Include functional, emotional, and social jobs.
- Map the job journey: before / during / after.
- First-principles check
- Identify root frictions (physics, economics, human limits).
- Separate real constraints from assumed constraints.
- Generate opportunities
- Produce 5-10 opportunity statements using the template below.
- For each, note frequency, severity, and current workaround.
- Score and rank
- Score 0-3: impact, urgency/frequency, underservedness, feasibility/leverage, willingness to pay.
- Rank top 3-5.
- Output and validation
- Present top opportunities with short rationale.
- List key assumptions and missing evidence.
- Suggest fastest validation tests (interviews, data checks, lightweight prototypes).
Opportunity Statement Template
Help [segment] achieve [job outcome] by reducing [specific friction] in [context].
Output Format
## Opportunity Discovery
### Context Summary
[1-3 sentences]
### JTBD Map
- Functional: ...
- Emotional: ...
- Social: ...
- Journey: before / during / after
### Opportunities (ranked)
1) [Statement]
- Scores: impact X, urgency X, underservedness X, feasibility X, WTP X
- Evidence: frequency, severity, workaround
- Rationale: ...
### Assumptions / Gaps
- ...
### Fast Validation Tests
- ...
### Next Step
Proceed to solution ideation. Run `/ideate-solutions`.
Quick Reference
- No solutions until opportunities are listed.
- Use concrete outcomes and observable behaviors.
- Always include alternatives and workarounds.
Common Mistakes
- Jumping to features instead of jobs
- Vague outcomes ("better UX")
- Ignoring current alternatives
- Mixing constraints with assumptions
- Too few opportunities (aim for 5-10)
Example
Input: "Independent designers need to invoice clients. They use spreadsheets and email, but late payments are common. They want faster payment and less admin. Budget is low."
Opportunity statement:
Help independent designers get paid faster by reducing follow-up overhead when invoices go overdue in client email workflows.
1---2name: discover-opportunities3description: Use after outcomes are defined to discover opportunities, unmet needs, market gaps, or JTBD insights before choosing solutions.4---5
6# Discover Opportunities
7
8## Overview
9Find real opportunities by reasoning from first principles and Jobs-To-Be-Done (JTBD). Focus on the user's job, context, and constraints before any solution ideas.
10
11## Position in Workflow
12
13Step 2 of product strategy workflow:
141. `/discover-outcomes` - Define outcomes
152. `/discover-opportunities` - Identify opportunities (THIS)
163. `/ideate-solutions` - Explore solution concepts
174. `/discover-assumptions` - Validate with experiments
18
19## Inputs (ask if missing, max 5)
20- Target user / segment
21- Trigger and context (when the job arises)
22- Desired outcomes (time, money, risk, effort, emotion)
23- Current alternatives / workarounds
24- Non-negotiable constraints (budget, regulation, tech, org)
25
26## Workflow
271. **Frame the jobs**
28 - Define the core job as verb + outcome (not a solution).
29 - Include functional, emotional, and social jobs.
30 - Map the job journey: before / during / after.
312. **First-principles check**
32 - Identify root frictions (physics, economics, human limits).
33 - Separate real constraints from assumed constraints.
343. **Generate opportunities**
35 - Produce 5-10 opportunity statements using the template below.
36 - For each, note frequency, severity, and current workaround.
374. **Score and rank**
38 - Score 0-3: impact, urgency/frequency, underservedness, feasibility/leverage, willingness to pay.
39 - Rank top 3-5.
405. **Output and validation**
41 - Present top opportunities with short rationale.
42 - List key assumptions and missing evidence.
43 - Suggest fastest validation tests (interviews, data checks, lightweight prototypes).
44
45## Opportunity Statement Template
46```
47Help [segment] achieve [job outcome] by reducing [specific friction] in [context].
48```
49
50## Output Format
51```
52## Opportunity Discovery
53
54### Context Summary
55[1-3 sentences]
56
57### JTBD Map
58- Functional: ...
59- Emotional: ...
60- Social: ...
61- Journey: before / during / after
62
63### Opportunities (ranked)
641) [Statement]
65 - Scores: impact X, urgency X, underservedness X, feasibility X, WTP X
66 - Evidence: frequency, severity, workaround
67 - Rationale: ...
68
69### Assumptions / Gaps
70- ...
71
72### Fast Validation Tests
73- ...
74
75### Next Step
76Proceed to solution ideation. Run `/ideate-solutions`.
77```
78
79## Quick Reference
80- **No solutions** until opportunities are listed.
81- Use concrete outcomes and observable behaviors.
82- Always include alternatives and workarounds.
83
84## Common Mistakes
85- Jumping to features instead of jobs
86- Vague outcomes ("better UX")
87- Ignoring current alternatives
88- Mixing constraints with assumptions
89- Too few opportunities (aim for 5-10)
90
91## Example
92**Input:** "Independent designers need to invoice clients. They use spreadsheets and email, but late payments are common. They want faster payment and less admin. Budget is low."
93
94**Opportunity statement:**
95Help independent designers get paid faster by reducing follow-up overhead when invoices go overdue in client email workflows.