experiment-design

Design lean product experiments to validate hypotheses and document learnings.

19|3|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/qa-aman/claude-skills --skill experiment-design-qa-aman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: experiment-design
Source: https://github.com/qa-aman/claude-skills/tree/main/skills/by-role/pm/experiment-design
Command: npx skills add https://github.com/qa-aman/claude-skills --skill experiment-design-qa-aman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design product experiments to test hypotheses and reduce risk before building features.

Core Features & Use Cases

  • State hypotheses clearly
  • Identify riskiest assumptions
  • Design minimum viable tests
  • Define success criteria and learning outcomes

Quick Start

State a hypothesis and generate a minimal viable test plan to validate it.

Frequently Asked Questions about experiment-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a lean experiment to validate a product hypothesis?

Design a lean experiment by stating a clear hypothesis, identifying the riskiest assumption, selecting a minimum viable test, and defining success criteria to validate product ideas before committing development resources.

What is a minimum viable test in product management?

A minimum viable test is the simplest experiment designed to validate your riskiest assumption, enabling product teams to test feature ideas, onboarding changes, or pricing bets without fully building the feature.

How do I identify the riskiest assumption for a startup feature idea?

Identify the riskiest assumption by analyzing your product hypothesis and pinpointing the core belief that, if proven false, would cause your feature idea or strategic bet to fail completely.

Can I use lean experiment design for pricing and onboarding changes?

Yes, lean experiment design applies to pricing experiments, onboarding changes, and other strategic bets, allowing product teams to define success criteria and document validated learnings across various workflows.

What is the best way to document validated learnings from a product experiment?

The best way to document validated learnings is to outline the experiment steps from hypothesis to test execution, capturing outcomes against predefined success criteria to reduce risk for future product bets.

When should I not use lean experiments for product validation?

Avoid lean experiments when lacking a clear hypothesis or measurable success criteria, as minimum viable tests require defined learning outcomes to effectively reduce risk before building features.