David Bland


Experiment Dashboard MVP

David Bland

When I go into companies to help them experiment, one of the first questions asked is What tools should we use?

To which I reply by using post-its, index cards, sharpies, blue tape and a wall.

This is intentional on my part, as I want them to understand the why and lower the barrier to learning. As awesome as a tool sounds, they never quite work the way you want them to. You also get, whether you want it or not, the tool creator's biases on how something should work.

If you've tried a few agile tools over the years, you'll notice they are all quirky in their own way. Each represents the founder's vision of agile. (or used to anyway)

But after repeated requests, I've decided to share my Experiment Dashboard MVP with the public. This is the same structure I use at Fortune 500 clients, with a few minor tweaks.

ID - The unique identifier for the experiment

Description - The description of your experiment. Includes problem and solution statements.

Tactic - The manner in which you are running your experiment. Includes problem interview, solution interview, survey, fake door, concierge, clickable wireframe, paper prototype, feature fake, a/b test, feature test, prototype

Cohort - The group of people you are including in the experiment.

Metric Theme - Which pirate metric theme applies? Includes acquisition, activation, retention, referral, revenue.

Metrics - The metric or metrics you are measuring for the experiment.

Status - Whether the experiment is actively running or not.

Start Date - Start date of the experiment.

End Date - End date of the experiment.

Results - Did your experiment pass or fail.

Learning - What you learned from running the experiment.

Next Steps - What's next after your experiment has completed.

Since this is a Google Doc, you can customize it to meet your vision of what an experiment dashboard should be. All I ask is that you first go to File -> Make a copy...

You can find the Experiment Dashboard MVP here.