Moving your experiment tracking from spreadsheets to Experiment OS

If you’ve outgrown your “spreadsheet of doom” (too many tabs, knowledge walking out the door, or too much time maintaining the sheet), this guide gets you into Experiment OS with minimal fuss. You don’t need a perfect import; you need a workable one. You can refine as you go.

1. 1

   Export your experiment log

   Export to CSV (or similar). Include: hypothesis or test name, status (e.g. backlog, running, done), result if done, decision (ship, iterate, stop, investigate), and any learnings. If you have multiple tabs (backlog, running, done), combine or export each and plan how they map into projects and statuses in Experiment OS.

2. 2

   Map columns to Experiment OS

   Hypothesis or idea maps to Hypothesis (or Experiment) name. Status to project and experiment status. Result: add when you create the experiment as completed. Decision and learnings: capture at the Decision step. You don’t need a 1:1 column match; focus on: what did we run, what did we decide, what did we learn.

3. 3

   Create a project and add content

   Create a project in Experiment OS. For each row in your export: add a Hypothesis (if it’s pre-test) or an Experiment (if it’s run or done). For completed tests, add the result and decision. Use the notes/learnings field for rationale. You can do this in batches; start with the last 20 to 30 that matter most.

4. 4

   Link research where it matters

   If you have research (surveys, heatmaps, interviews) that supported hypotheses, add them in the Research library and link to the relevant hypotheses. You don’t have to do everything day one; prioritise the tests you’re most likely to refer back to.

5. 5

   Invite the team

   Once the first batch is in, invite the team. They’ll see one source of truth. New experiments go in Experiment OS from here on. You can backfill more history over time.

All guides · Compare vs spreadsheets · 10 signs you’ve outgrown spreadsheets