wowprompt

Product experiment brief with a hypothesis, guardrail metrics and a ship rule

Writes the brief for a product experiment before it runs: the change, the hypothesis, the primary metric, guardrail metrics that must not get worse, who sees it, how long it runs, and a decision rule written in advance for ship, iterate or drop. Use it before a feature test, a pricing page change or an onboarding experiment, so the result cannot be argued into whatever the team hoped for.

An experiment brief with the hypothesis, primary and guardrail metrics, audience and duration, a pre-agreed decision rule table and the risks to watch
The output this prompt produced, unedited.

The prompt

Fill in these first

  • Product and the change being tested: [e.g. showing delivery time on the product card in a grocery app]
  • Why we think it will work: [evidence, such as interviews, support tickets, a competitor pattern]
  • Primary metric and its current value: [e.g. add-to-cart rate, 11 percent]
  • Metrics that must not get worse: [e.g. order value, refund rate, page load time]
  • Traffic available per week: [e.g. 40,000 users on that screen]
  • Smallest change worth shipping: [e.g. plus 0.5 percentage points]

Write the brief

  1. Hypothesis: "If we [change], then [metric] will [move] because [reason]."
  2. Variants: control and each test version, described so a developer can build them.
  3. Audience: who is included, who is excluded, and how users are split.
  4. Duration: whole weeks only, long enough to reach the needed sample, and the date to stop.
  5. Primary metric and how it is counted.
  6. Guardrail metrics, each with the threshold that stops the test.
  7. Decision rule written now:

| Result | Decision | | Primary up by at least the smallest worthwhile change and guardrails hold | Ship | | Primary flat or unclear | Iterate or drop, with which one | | Any guardrail breached | Stop and roll back |

  1. Risks: novelty effects, seasonal traffic such as a festive sale week, and other tests running on the same screen.

Guardrails

  • Do not peek and stop early on a good day; name the stop date.
  • If the traffic cannot reach the sample needed in four weeks, say so and suggest a bigger change or a different method.
product experiment briefa b test plan for productguardrail metricsexperiment hypothesisship decision ruleproduct experimentation

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity