E.g. text is an example you replace with your own answer.
Confirm the test is done
Record the numbers against the brief
Assign a status and decide the next action
Identify the test
Fill in the fields that tie this review to its brief. Keep the rows that fit, add any your team relies on:Concept review: Tying the review to its brief
Concept review: Tying the review to its brief
Record the results
Enter each metric next to what the brief committed to, so the comparison is visible in one place:Concept review: Reading results against the brief, not on their own
Concept review: Reading results against the brief, not on their own
Check the result against success criteria
Work through the checks the brief set. Keep the ones that apply, add any your criteria included:- E.g. Primary metric met the minimum lift stated in the brief
- E.g. Result reached the confidence threshold stated in the brief
- E.g. No guardrail degraded beyond its stated limit
- E.g. Test ran to its planned sample and timeline (no peeking, no early stop)
- Add a criterion
Concept review: Why the checks are separate from the numbers
Concept review: Why the checks are separate from the numbers
Assign a status
Mark the test with one status. These five cover the common cases; add your own if your team distinguishes more:Concept review: What the five statuses keep clean
Concept review: What the five statuses keep clean
Interpret and decide the next action
Explain what the result means and what you’ll do about it: E.g. Orange CTA lifted click-through without touching revenue per session, which supports the contrast hypothesis. Next action: roll the orange button out to the pricing page permanently, and queue a follow-up test applying the same treatment to the checkout CTA.Concept review: Why interpretation and next action live together
Concept review: Why interpretation and next action live together
Save the review and link it back to the brief
Once the review is complete, it doesn’t live here. Save it into the experiment learning group as a report, then copy that report’s link back into the original brief, so the brief and the learning group point at each other.Concept review: Why the review lives in the learning group, linked from the brief
Concept review: Why the review lives in the learning group, linked from the brief
Your review at a glance
Identify
Record
Check
Status
Decide, save, and link back
Related resources
- Experiment brief The hypothesis, design, and success criteria this review is checked against.
- Experiment brief concepts
- Experiment learning library
- Statistical significance
MCP wiring
MCP wiring
Domains: experiment, reporting
Provides:
process:experiment-reviewUses:
experiment-brief, experiment-log, library:experiment, statistical-significanceAsks, in order:- Which experiment is this (ID)? Options:
experiment-log. Skip when: ID given. - Did the test run to its planned sample and end date? Options: yes or no.
- What were the primary, secondary and guardrail results? Options: your answer. Skip when: flat file accessible.
- What’s the next action? Options: your answer.