opportunity-framework
owl-listener/designer-skills
Identify, score, and prioritize design opportunities against impact and effort.
What is opportunity-framework?
A framework for evaluating and ranking design ideas when capacity is limited. Use this to move from a backlog of possible improvements to a prioritized roadmap, then pair with design-brief to frame your chosen opportunity.
- Score opportunities using Impact-Effort Matrix (quick wins, strategic bets, fill-ins, deprioritize)
- Apply RICE scoring (Reach, Impact, Confidence, Effort) for quantitative ranking
- Evaluate using Kano Model to classify features as must-be, one-dimensional, or attractive
- Compare user value vs complexity on 1-10 scales
- Generate ranked lists with rationale and confidence levels
- Group opportunities by theme and identify dependencies
How to install opportunity-framework
npx skills add https://github.com/owl-listener/designer-skills --skill opportunity-frameworkHow to use opportunity-framework
- 1.Gather opportunity sources: research findings, analytics, competitive gaps, stakeholder requests, support feedback
- 2.Select one or more evaluation frameworks (Impact-Effort Matrix, RICE, Kano Model, Value vs Complexity)
- 3.Score each opportunity using your chosen framework(s)
- 4.Document the rationale and confidence level for each score
- 5.Group related opportunities by theme and identify dependencies
- 6.Review the ranked output and use design-brief skill to frame your top-priority opportunity
Use cases
- Prioritize feature requests when your team has more ideas than capacity
- Evaluate research findings and competitive gaps to identify high-impact improvements
- Score stakeholder requests and support channel feedback against effort required
- Compare strategic bets (high impact, high effort) against quick wins before committing resources
- Triangulate multiple frameworks to build consensus on which opportunity to pursue next
- Product managers evaluating feature backlogs
- Design teams with competing improvement ideas
- Teams conducting research and needing to act on findings
- Stakeholders deciding between strategic initiatives
opportunity-framework FAQ
Use Impact-Effort Matrix for quick visual prioritization with small teams. Use RICE when you need quantitative scoring with reach and confidence data to justify decisions to stakeholders.
High scores across multiple frameworks indicate strong candidates. Document which frameworks agree and which diverge—this builds confidence in your final ranking.
Include diverse perspectives initially, then filter by relevance to your strategy. The framework helps you evaluate fairly rather than relying on who spoke loudest.
Use disagreement as a signal to gather more data or revisit assumptions. Document different perspectives and use the framework to make the trade-offs explicit.
Revisit quarterly or when significant new information emerges (research findings, market changes, capacity shifts). Document how your thinking evolved.
Full instructions (SKILL.md)
Source of truth, from owl-listener/designer-skills.
name: opportunity-framework
description: Identify, score, and prioritise design opportunities against impact and effort. Use when there are more ideas than capacity. For framing the one you choose, use design-brief.
Opportunity Framework
You are an expert in identifying, evaluating, and prioritizing design opportunities.
What You Do
You help teams move from possible improvements to a prioritized roadmap.
Opportunity Sources
Research findings, analytics, competitive gaps, technology, stakeholder requests, support channels.
Evaluation Frameworks
Impact-Effort Matrix
2x2 grid: quick wins, strategic bets, fill-ins, deprioritize.
RICE Scoring
Reach, Impact (1-3), Confidence (%), Effort (person-weeks).
Kano Model
Must-be, one-dimensional, attractive, indifferent, reverse.
Value vs Complexity
Score user value (1-10) and complexity (1-10).
Output
Ranked list with rationale, theme groupings, dependencies, confidence levels.
Best Practices
- Use multiple frameworks to triangulate
- Include diverse perspectives
- Revisit as you learn
- Document the 'why' behind every decision
Related skills
More from owl-listener/designer-skills and the wider catalog.
pattern-library
Document reusable design patterns with problem context, solution, anatomy, and related patterns.
presentation-deck
Structure design presentations that persuade your specific audience and drive decisions.
prototype-strategy
Choose the right prototype fidelity and method to answer your design question efficiently.
readable-measure
Set optimal line length (45–75 characters) for comfortable reading across devices and type sizes.
research-repository
Organize research findings so teams stop redoing studies and build on accumulated evidence.
responsive-design
Design layouts and interactions that adapt across screen sizes and input methods.