Example data. Fieldnote is a fictional company used to fill all 61 boards, so the examples tell one consistent story.
Post-PMF Fieldnote: the trio turns the two winning ideas plus one assumption into experiments for the next three weeks.
What the team took away
Two of three held up. Photo-only mode shipped as the default, the kit went to Julien's onboarding, the counter died cheaply.
How to run it
Preparation
The product trio: PM, designer, tech lead. Add a data person if you have one; they will save you from untestable metrics.
Bring the top 3 to 5 assumptions from the assumption map, or the leaf-level experiments from the OST.
On the board: the grid with one row per experiment and the six columns: hypothesis, test, metric, success criteria, result, learning.
Have last quarter's experiment board open next to it. Half the time, someone already tested something close.
Agenda
15 min
Rewrite the assumptions as hypotheses Format: 'we believe [segment] will [behavior] because [reason]'. One per row. If you cannot name the behavior, the hypothesis is not testable yet.
25 min
Choose the cheapest test For each: fake door, concierge, landing page, prototype interview, data pull, or a real small release. Pick the one that gives a signal in two weeks or less. Write who runs it.
25 min
Define metric and threshold One metric per test and the number that means 'validated' or 'killed', decided now. 'We will see' is not a criterion. Include the sample size you need.
15 min
Check for confounds For each test, ask what else could explain a positive result. If the answer is obvious, change the test. Add the control where needed.
10 min
Schedule and commit Start dates, review date, owner in each row. Book the review in the calendar before leaving.
Pitfalls
Do not set the success threshold after seeing the data. Every result looks like a win in hindsight.
Do not run six experiments at once with a team of three. Two in parallel is the realistic ceiling.
Do not delete failed rows. The learning column of a failed experiment is worth more than the result column of a successful one.
Afterwards
Each row is reviewed at the agreed date; result and learning are filled in the same meeting. Validated hypotheses move to the story map or the roadmap; killed ones update the assumption map and the OST.