Brainstorm Experiments Existing

Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.

Published by @Paweł Huryn·from phuryn/pm-skills·0 agent reads / 30d·0 saves·

Design Experiments (Existing Product)

Design low-effort experiments to test product assumptions before committing to full implementation.

Context

You are helping a product team design experiments for $ARGUMENTS. The team has a feature idea and assumptions that need validation.

If the user provides files (PRDs, assumption lists, designs), read them first.

Instructions

The user will describe their idea and assumptions. Work through these steps:

  1. Clarify the idea and assumptions: Confirm what the team wants to build and what they need to validate.

  2. Suggest experiments for each assumption. Consider methods like:

    • First-click testing or task completion with a prototype
    • Feature stubs or fake door tests
    • Technical spikes
    • A/B tests on production (with risk mitigation)
    • Wizard of Oz approaches
    • Survey-based validation (behavioral, not opinion-based)
  3. Key principles to follow:

    • Measure actual behavior, not users' opinions
    • Test responsibly — don't put users or the business at risk
    • For production tests (e.g., A/B tests), explain risk mitigation strategies
    • Aim for maximum validated learning with minimal effort
  4. For each experiment, specify:

    • Assumption: What do we believe?
    • Experiment: What exactly will we do to validate it?
    • Metric: What will be measured?
    • Success threshold: The expected value if we are right

Think step by step. Present experiments in a clear table or structured format. Save as markdown if substantial.


Further Reading

  • Testing Product Ideas: The Ultimate Validation Experiments Library
  • Assumption Prioritization Canvas: How to Identify And Test The Right Assumptions
  • What Is Product Discovery? The Ultimate Guide Step-by-Step
  • Continuous Product Discovery Masterclass (CPDM) (video course)

Bundled with this artifact

2 files

Reference files that ship alongside this artifact. Agents pull these in only when the task needs them.

More on the bench

SKILL0

Launch

When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas.

marketing-growth-copy+2
9
SKILL0

Marketing Ideas

When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing strategies,' 'marketing tactics,' 'ways to promote,' or 'ideas to grow.' This skill provides 139 proven marketing approaches organized by category.

marketing-growth-copy+2
7
SKILL0

Bash Pro

Master of defensive Bash scripting for production automation, CI/CD pipelines, and system utilities. Expert in safe, portable, and testable shell scripts.

ai-prompt-engineering+3
4