# Growth experiment brief template

> Specify the hypothesis, assignment, outcome and decision rule before a growth experiment starts. Use the editable worksheet, example and review steps to turn it into a working document.

Source: https://saas-marketing.net/templates/experiment-brief/
Topic: SaaS Growth Marketing
Type: template
Published: 2026-09-17
Last updated: 2026-09-17
Publisher: SaaS Marketing (saas-marketing.net)
License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/templates/experiment-brief/

## Short answer

Growth experiment brief template helps a SaaS team specify the hypothesis, assignment, outcome and decision rule before a growth experiment starts. The fields below define the required decisions and evidence. Download a CSV working copy, assign owners and replace the illustrative example with your own approved information.

## Key takeaways

- Specify the hypothesis, assignment, outcome and decision rule before a growth experiment starts.
- Do not choose the winning metric after seeing the results or repeatedly stop when a p-value first looks favorable.
- Every field needs a useful answer, supporting evidence or an explicit unresolved question.
- The download is an editable CSV file that opens in spreadsheet applications.

---

Specify the hypothesis, assignment, outcome and decision rule before a growth experiment starts. This worksheet supports the broader [saas growth plan](/saas-growth/).

## The working template

| Field | What to enter | Your answer | Owner |
| --- | --- | --- | --- |
| Problem | Describe the observed constraint. | | |
| Hypothesis | Explain the mechanism expected to change behavior. | | |
| Audience | Define eligibility and exclusions. | | |
| Assignment | Document treatment and control allocation. | | |
| Primary metric | Choose one decision outcome. | | |
| Guardrails | Protect revenue, reliability and user experience. | | |
| Duration | Allow for sample requirements and delayed outcomes. | | |
| Decision | State what leads to ship, revise or stop. | | |

## A worked example

A trial activation test changes the setup instructions for randomly assigned new accounts while preserving the same product and pricing.

The example is illustrative. It does not describe a measured customer result or create a promise about your own outcomes. Use it to understand the level of specificity the document needs.

## How to complete the worksheet

1. Choose one project, account segment or decision. A document that attempts to cover the whole company usually hides important differences.
2. Gather the evidence required by the fields above. Use approved customer research, current product information and the relevant business records.
3. Draft the answers with the person responsible for doing the work. Keep unresolved questions visible and assign a next action to each one.
4. Review the document with the people who depend on it. Confirm scope, responsibilities and any constraints before treating it as an operating agreement.
5. Save the version and review date. Update it when the underlying offer, process or customer evidence changes.

## Review before sharing

Do not choose the winning metric after seeing the results or repeatedly stop when a p-value first looks favorable.

A useful working document makes disagreements visible while there is still time to resolve them. Ask a colleague to explain the intended decision from the filled-in version without additional narration. If they cannot identify the next step or the evidence behind it, revise the relevant field.

Remove confidential customer details from any public copy. Keep names, prices and results only when you have permission and can explain their context. An empty evidence field is a signal to investigate, not an invitation to supply a plausible-sounding number.

## Continue the work

- [How to Build a SaaS Growth Model](/guides/saas-growth-model/)
- [Growth Loops for SaaS](/guides/growth-loops/)
- [SaaS Growth Strategies That Actually Compound](/guides/saas-growth-strategies/)
- [B2B SaaS Growth](/guides/b2b-saas-growth-growth/)
- [Product Led Growth for SaaS](/guides/product-led-growth/)

Find more [templates](/templates/) and [checklists](/checklists/) for adjacent tasks.
{/* expanded-practice-2026-09 */}
## Apply growth experiment brief template in a working review

Make a copy of the working file and complete one representative row before filling the entire document. Replace example values with evidence from the actual project. Add an owner and a review condition where the template calls for a decision. A blank marked unknown is more useful than an invented number that makes the file look finished.

For this topic, involve the experiment owner and the analyst responsible for design integrity and work from hypothesis, assignment rules, metric definition and decision record. The relevant unit is the prespecified eligible user or account cohort. State the question the review should resolve before choosing a chart, an asset or a tool. If participants disagree about the unit or scope, resolve that disagreement before combining their evidence.

### Evidence to prepare

Check the design before interpreting a result. Assignment, exclusions, outcome timing and stopping rules can change the meaning of an apparently precise statistic. Separate practical effect from statistical evidence and keep guardrails beside the primary outcome.

| Review field | What to record |
| --- | --- |
| Topic | Growth experiment brief template |
| Decision | The specific action this explanation should help you choose |
| Working evidence | hypothesis, assignment rules, metric definition and decision record |
| Unit and scope | the prespecified eligible user or account cohort |
| Responsible people | experiment owner and the analyst responsible for design integrity |
| Remaining uncertainty | The missing fact that could change the decision |

### Two situations that can change the interpretation

#### When experiment groups have unexpected sizes

A tracking failure affecting one variant can create an apparent conversion lift even when the user experience did not improve.

Use this check: Check assignment, eligibility, logging and exclusions before interpreting outcome differences. Do not repair the result by silently dropping inconvenient observations.

The [focused diagnostic guide](/guides/growth-test-has-sample-ratio-mismatch/) provides the correction process and a working evidence sheet.

#### When the experiment backlog ignores the main constraint

Changing a button color is unlikely to fix a workflow that requires an unavailable integration before any value can be reached.

Use this check: Map the current customer path and identify where suitable users fail to progress. A large drop-off is not automatically the best target if the users are intentionally ineligible.

The [focused diagnostic guide](/guides/experiment-backlog-has-no-constraint/) provides the correction process and a working evidence sheet.

### Record the decision and the limit

A higher signup rate is not automatically a better activation path if the removed step helped users reach a useful workflow. Review the complete sequence and the relevant customer outcome. A bundled product change can be evaluated as a bundle without claiming to isolate every component.

Keep the conclusion beside the evidence that supports it. Record what the team will do, who owns the next action and which event or date will trigger a review. If the underlying definition, audience or product behavior changes, revisit the conclusion rather than assuming the old result still applies. A clear limit is useful information; it tells the next reader where additional investigation is required.

Use the [complete topic collection](/topics/saas-growth/) for related methods and the [category field guides](/industries/) when the product's buying situation or implementation requirements change how the method should be applied.

## Frequently asked questions

### What format is the downloadable template?

The working copy is a CSV file. Open it in your spreadsheet application, add owners and dates, and keep a separate copy of the original for reference.

### How should I fill in this template?

Specify the hypothesis, assignment, outcome and decision rule before a growth experiment starts. Start with one real project so that the decisions remain specific.

### What mistake should I avoid?

Do not choose the winning metric after seeing the results or repeatedly stop when a p-value first looks favorable.

### Do I need to complete every field before starting?

Identify the fields that change the decision or block safe execution. Mark unknowns with an owner and a review date rather than inventing an answer.