| name | ost-builder |
| description | Use to build or update an Opportunity Solution Tree from research data. Never from brainstorming. |
OST Builder Skill
Build and maintain Opportunity Solution Trees from research evidence.
Workflow
Building a New OST
-
Define the desired outcome at the top of the tree. This comes from the north star metric or current strategic goal.
-
Review all research data: Interview transcripts, behavioral data, analytics, observation notes.
-
Extract opportunities (unmet needs, pain points, desires):
- Each opportunity must cite at least 2 evidence sources.
- Phrase as user needs, not solutions: "Users need to know their payment succeeded" not "Users need a confirmation email."
- Look for frequency across interviews, not just intensity in one.
-
Structure hierarchically: Group related opportunities. Identify parent-child relationships.
-
For each leaf opportunity, generate solution ideas:
- Multiple solutions per opportunity.
- Solutions can be simple experiments, not just features.
- Include "do nothing" as an option when appropriate.
-
For each solution, identify assumption tests:
- What must be true for this solution to work?
- What is the cheapest way to test that assumption?
Updating an Existing OST
- Review new research data since last update.
- Add new opportunities with evidence citations.
- Refine or remove opportunities that evidence no longer supports.
- Add new solutions for validated opportunities.
- Update confidence scores based on new evidence.
- Prune solutions that have been invalidated.
Rules
- Never add opportunities without evidence citations.
- Never brainstorm opportunities. Discover them.
- Every opportunity must link to at least 2 research data points.
- Solutions come after opportunities are understood, not before.
- The OST is a living document. Update weekly with new research.
Theory Citations
- Torres: Continuous Discovery Habits (OST methodology)
- Christensen: Competing Against Luck (JTBD informing opportunities)