Skip to main content

Product Demo Experiment Results Readout Template

Illustrated templates & scripts article cover with a document and play control for product demo experiment results readout template

An experiment result is useful when a teammate can see what changed, who saw it, and why the team made a decision. This template works even when the sample is too small for a firm numerical conclusion.

Copy the results record

  • Experiment and brief link:
  • Dates and owner:
  • Audience, placement, and eligibility:
  • Control experience:
  • Changed experience:
  • Primary measure: [the buyer action or result you hoped to improve]
  • Primary result: original [count or rate]; changed [count or rate]
  • Guardrail measure: [something that should not get worse, such as confusion or page speed]
  • Guardrail result: original [observation]; changed [observation]
  • Sample size and exclusions:
  • Buyer or sales observations:
  • Known confounders:
  • What the evidence supports:
  • What it does not establish:
  • Decision: keep / revise / stop / rerun
  • Decision owner and date:
  • Next check and rollback link:

If a new demo card gets more starts but the same number of meaningful completions, report both. If campaign targeting changed during the test, note it. Do not describe a directional lift as a proven causal effect.

What would a cautious readout say?

This example is fictional; the counts are not MaybeUndo performance data:

  • Comparison: An original demo card and a new role-specific card on the same type of page.
  • Observation: The new card had 18 useful completions from 90 eligible visits; the original had 12 from 85. Two reviewers still misunderstood the plan label.
  • Limit: The groups were small and the traffic mix changed during the test, so the counts do not establish that the new card caused the difference.
  • Decision: Revise the plan label and rerun before adopting the new card.

The decision sentence should connect the observed result to the next action without describing a directional count as a proven lift. If the evidence is inconclusive, say so.

How can the next team use the result?

Link the exact asset versions and the original experiment brief. Record exclusions, unresolved questions, and a future review trigger such as a plan update. That lets another editor understand the decision and repeat the test under comparable conditions.

Ready to try our platform?

Get started for free