Experiment Board

Purpose

The Experiment Board gives teams a single place to plan, track, and learn from experiments. Each experiment moves through columns — from hypothesis to design, running, results, and validated/invalidated. The board makes the team's learning pipeline visible and prevents experiments from being run without clear success criteria or follow-through.

At a glance

How to run

1. Set up the board (5 min): Create columns: Hypotheses → Experiment Design → Running → Results → Validated / Invalidated / Inconclusive.
2. Populate hypotheses (5 min): Pull the top-priority assumptions from your Assumption Map or Hypothesis Canvas.
3. Design experiments (15 min): For each hypothesis, define: method, metric, success criterion, timeline, and owner. Write on a card and place in Experiment Design.
4. Review and commit (5 min): Walk the board. Check that each experiment is feasible within the timebox. Move the first experiments to Running.

Materials needed

• Physical board (whiteboard, wall, or corkboard) or digital board (Miro, Trello, Notion)
• Experiment cards (template with Hypothesis, Method, Metric, Success Criterion, Owner, Deadline)
• Markers and sticky notes

Pitfalls & common mistakes

• Too many experiments at once: Limit work in progress. 2–3 running experiments is plenty for most teams.
• No review cadence: Schedule a weekly experiment review to update the board.
• Inconclusive results ignored: Inconclusive is not failure — redesign the experiment.
• Board goes stale: If the board is not updated, it loses trust. Assign a board owner.

Inclusion & accessibility

• Make the board visible and accessible to all team members, including remote ones.
• Use clear, consistent card formats so anyone can read and understand an experiment.
• Review the board together rather than relying on individuals to check asynchronously.

Variations

• Lean Canvas + Experiment Board: Pair the Business Model Canvas with an experiment board for each risky block.
• Sprint-based Experiment Board: Reset the board each sprint with new experiments.
• Traffic-light Board: Use Green / Yellow / Red signals instead of columns.

When NOT to use this

• When the team is not running experiments — the board is overhead without experiments.
• When there is only one experiment — a simple task tracker suffices.
• When the organisation does not support experimentation culture.

Source & further reading

• David J. Bland & Alexander Osterwalder, *Testing Business Ideas* (2019)
• Javelin Board (experiment board template)
• Lean Startup methodology