discover-assumptions
npx machina-cli add skill kasperjunge/agent-resources/discover-assumptions --openclawDiscover Assumptions and Experiments
Overview
Surface the riskiest assumptions in an Opportunity Solution Tree and design the smallest tests that can prove or disprove them quickly.
Position in Workflow
Step 4 of product strategy workflow:
/discover-outcomes- Define outcomes/discover-opportunities- Identify opportunities/ideate-solutions- Explore solution concepts/discover-assumptions- Validate with experiments (THIS)
Inputs (ask if missing, max 5)
- Target node(s): outcome, opportunity, or solution
- Target users/market
- Existing evidence (data, research, learnings)
- Constraints (time, budget, ethics, legal)
- Decision deadline
Assumption Types
- Desirability: Users want or value it
- Usability: Users can use it successfully
- Feasibility: We can build/deliver it
- Viability: It supports the business model
- Risk/Compliance/Ethics: It is safe and allowed
- Strategic: It aligns with goals and positioning
Workflow
- List assumptions per node
- Write assumptions as testable statements.
- Score risk
- Impact (low/medium/high) x uncertainty (low/medium/high).
- Note current evidence strength (none/weak/moderate/strong).
- Prioritize
- Select top 3-5 riskiest assumptions.
- Design experiments
- Propose 2+ tests per assumption, fastest/cheapest first.
- Define hypothesis, method, sample, success metric, and decision threshold.
- Sequence tests
- Start with tests that can invalidate assumptions quickly.
Experiment Patterns (examples)
- Customer interviews, observation, diary studies
- Survey with behavioral intent + follow-up validation
- Smoke test or landing page
- Fake-door or click-through test
- Concierge or Wizard-of-Oz pilot
- Prototype usability test
- A/B test or pricing experiment
- Limited rollout with manual operations
Output Format
## Assumption Discovery
### Context Summary
[1-3 sentences]
### Assumptions (by node)
- Node: [Outcome/Opportunity/Solution]
- Assumption: ... (type: desirability)
- Evidence: ... (strength: weak)
- Risk: impact high x uncertainty high
### Top Risks
1) Assumption: ...
- Why risky: ...
### Experiments
1) Assumption: ...
- Hypothesis: ...
- Method: ...
- Sample: ...
- Success metric: ...
- Decision threshold: ...
- Time/cost: ...
### Sequenced Plan
1) ...
2) ...
### Open Questions
- ...
### Next Step
If assumptions are validated, proceed to product planning.
Quick Reference
- Turn beliefs into testable statements.
- Prefer tests that can disprove the assumption fast.
- Document decision thresholds before running tests.
Common Mistakes
- Treating opinions as evidence
- Testing solutions before validating the underlying assumption
- Running expensive tests without cheap falsification attempts
- Vague hypotheses or missing thresholds
Source
git clone https://github.com/kasperjunge/agent-resources/blob/main/skills/product-strategy/discover-assumptions/SKILL.mdView on GitHub Overview
Discover Assumptions surfaces the riskiest beliefs behind outcomes, opportunities, or solution ideas within an Opportunity Solution Tree. It guides you to design the smallest, fastest tests to prove or disprove those assumptions and move toward validated product decisions.
How This Skill Works
List assumptions per node (outcome, opportunity, or solution), score risk as impact x uncertainty and note evidence strength, then prioritize the top 3-5 riskiest assumptions. For each, design 2+ tests with clear hypotheses, methods, sample sizes, success metrics, and decision thresholds, then sequence tests to invalidate risky beliefs quickly.
When to Use It
- After ideating solution concepts, to test underlying assumptions (desirability, usability, feasibility, viability, risk/ethics, and strategic alignment) before building.
- When you want to surface and document the riskiest assumptions in an Opportunity Solution Tree.
- When prioritizing which assumptions to test given time and budget constraints.
- When designing experiments with multiple tests per assumption, focusing on fastest/cheapest options first.
- When sequencing tests to quickly invalidate or validate core beliefs about outcomes, opportunities, or solutions.
Quick Start
- Step 1: List assumptions per node (outcome/opportunity/solution).
- Step 2: Score risk (Impact x Uncertainty) and pick the top 3-5 riskiest assumptions.
- Step 3: Design 2+ tests per assumption (hypothesis, method, sample, success metric, decision threshold) and plan their sequence.
Best Practices
- List assumptions per node as testable statements.
- Score risk using Impact x Uncertainty and note current evidence strength.
- Prioritize the top 3-5 riskiest assumptions.
- Design at least 2+ tests per assumption, with the fastest/cheapest first.
- Sequence tests to invalidate assumptions quickly.
Example Use Cases
- Conduct customer interviews or observations to test desirability and usability.
- Run a smoke test or landing page to gauge interest and viability.
- Use Concierge or Wizard-of-Oz pilots to validate feasibility and user experience before full build.
- Execute a pricing or A/B test to test viability and monetization assumptions.
- Implement a limited rollout with manual operations to assess real-world feasibility and risk.