alexe-ev Frame Insight & Opportunity
Purpose
Convert research insights into structured opportunity statements that can be prioritized, sized, and used as inputs for experiment design or roadmap planning.
Skill type
Conceptual skill
Use this skill when
- Research synthesis exists but hasn't been turned into product opportunities
- A team is debating what to work on next and needs a structured opportunity view
- Insights need to be communicated to stakeholders as investable opportunities
- Prioritization requires comparing opportunities with consistent structure
Do not use this skill when
- The goal is solution design or feature definition (this skill defines the opportunity, not the solution)
- No research exists yet (run synthesize-qualitative-research first)
Required inputs
- Research insights or findings
Optional inputs
- Business goals or OKRs
- Affected user segment
- Relevant metrics
Upstream context
Works best when:
- Qualitative research has been synthesized
- Personas or segments are defined
If upstream context is missing
If only vague insights are provided, frame provisional opportunities and list what evidence is still needed.
Downstream handoff
Output can feed:
- build-portfolio-roadmap-strategy (which opportunities to invest in)
- formulate-experiment-hypothesis (turn opportunity into testable hypothesis)
- set-goals-okrs-kpis (connect opportunity to measurable goal)
Instructions
- For each key insight, extract the underlying user need or problem.
- Frame the opportunity using the format: "How might we [user need] so that [outcome]?"
- Assess evidence quality and confidence.
- Estimate rough potential impact on relevant product metrics.
- Identify the user segment most affected.
- Flag dependencies, risks, or constraints.
Output
For each opportunity:
- Opportunity statement (HMW format)
- Insight it is derived from
- Affected segment
- Potential impact (qualitative: low / medium / high)
- Evidence quality: assumed / data-informed / validated
- Risks or constraints
- Suggested next step: experiment, research, or build
Risks / caveats
- Do not jump to solution descriptions in the opportunity statement
- Opportunity quality depends on research quality — weak research produces weak opportunities
- Do not overstate impact estimates when evidence is thin