
Define Hypothesis
Turns vague product ideas into testable statements with clear metrics and validation plans. You'd use this before committing resources to a feature, when your team has competing assumptions, or when setting up A/B tests. Follows the "We believe that [action] for [target user] will [outcome]" format and forces you to define specific success metrics, guardrails, and falsifiable criteria. The structured template keeps you honest about what you're actually testing. Fits into the triple diamond and lean startup frameworks if you're into that. Most useful when you're about to build something expensive based on gut feel and need to make your assumptions explicit enough that the whole team can argue about them productively.
- skills.sh installs
- 858
- GitHub stars
- 794
- last updated
- Aug 21, 2026
Install
$ npx -y skills add product-on-purpose/pm-skills --skill define-hypothesis --agent claude-codeInstalls into .claude/skills of the current project.
Files
Hypothesis
A hypothesis is a testable prediction about how a change will affect user behavior or business outcomes. It transforms assumptions into explicit statements that can be validated or invalidated through experimentation. Well-formed hypotheses prevent teams from building features based on untested beliefs and create shared understanding of what success looks like.
When to Use
- After problem framing, before committing to a solution
- When designing experiments or A/B tests
- When team members have differing assumptions about user behavior
- Before investing significant engineering resources in a feature
- When pivoting direction and need to validate the new approach
When NOT to Use
Sponsors
Details
- Repository
- github.com/product-on-purpose/pm-skills
- Categories
- Testing & QA, Data Science & ML, Design & UI/UX
- First seen
- Jun 3, 2026
More from product-on-purpose/pm-skills
All 68- Develop Adr842
- Deliver Launch Checklist834
- Develop Solution Brief830
- Define Opportunity Tree824
- Discover Interview Synthesis819
- Define Jtbd Canvas817
- Measure Dashboard Requirements801
- Measure Experiment Design801
- Deliver Release Notes797
- Develop Design Rationale793
- Foundation Persona792
- Measure Instrumentation Spec792
- Measure Experiment Results787
- Iterate Retrospective786
- Utility Mermaid Diagrams786
- Discover Stakeholder Summary779
- Foundation Okr Writer776
- Develop Spike Summary774
- Iterate Lessons Log767
- Iterate Pivot Decision767
- Utility Slideshow Creator764
- Foundation Lean Canvas762
- Iterate Refinement Notes753
- Utility Pm Skill Builder751