The register
The first three rows are examples using Doughnut Labs, a SaaS company that sells disruptive Doughnut Technology. Delete them and fill in your own.Status values
Seven values, so the register can be filtered rather than read. The first five apply to experiments, the last two to pilots.
A pilot never gets Win or Loss. Those words claim a comparison that a pilot has no control to support, and using them here is how a first flight gets cited a year later as proof a channel works.
Invalid matters as much as the others. A test recorded as Inconclusive when it was actually broken tells the next person the idea doesn’t work, which is not what happened.
Before you design a test, search here
Search on the surface and on the metric, not on the wording of your hypothesis. Someone else will have described the same idea differently. Three outcomes, and all three are useful:- Already tested and won. It should already be a default. If it isn’t, that’s the finding.
- Already tested and lost or showed nothing. Either move on, or state what is different now: more traffic, a different audience, a changed product. “We’ll try it again properly” is not a difference.
- Not tested. Design it, following run an experiment.
What a row needs to be useful
The register is only as good as the discipline behind the rows.- The ID, matching the pattern in experiment ID, so the test can be traced to the campaigns and events that carried it.
- The hypothesis as it was written before launch, not a version rewritten to match the outcome.
- The decision rule’s verdict, not an interpretation. Whether it beat the bar is a fact; whether it was worth doing is an opinion, and belongs in the review.
- What actually changed as a result. A win with no decision recorded is a test that ran for nothing.
When a result stops being true
Results age. A test won in a different market, at a different price, against a different competitive set may not hold. Mark a row superseded rather than deleting it, and link the test that replaced it, so the history of what was believed and when stays intact.Related resources
- Run an experiment The full path, ending with a row here.
- Experiment review process What produces the row.
- Experiment brief The workbook each row links back to.
- Pilot brief The workbook behind a pilot row, where there was no control.
- Experiment ID The ID pattern and the issued-ID log.
- Experimentation best practices Why nulls get recorded.
MCP wiring
MCP wiring
Type: library
Domains: experiment
Provides:
Uses:
Domains: experiment
Provides:
library:experiment, experiment-logUses:
experiment-brief, experiment-id, pilot-briefAsks, in order:- Which surface and metric? Options: your answer. Skip when: experiment brief attached.
- Status by the pre-set decision rule? Options:
options:experiment-status. Skip when: review states it.
Get the complete Marketing OS
Subscribe to Snow Doughnut, our free weekly newsletter, and get the Notion workspace where you do the work: tasks, a marketing calendar, name generators, briefs, and more.
Have us run it for you
We implement this system, use it to help you grow and scale, then hand it all off to you when you’re ready.