Track experiments

Before you start

• At least one selected experiment (step 2 of the method).

Steps

1. Open the Experiments board

   In a project, choose Experiments. The board groups experiments by where they stand: designing, collecting evidence, learning and decided. Switch to list for a compact view. Filter by all or assigned to me, or search.

   

   Each card shows the experiment type, its hypothesis, owner and due date. Open one to go to its workbench.

2. Keep owner and due date current

   Owner and due date are set when you assign the experiment, and shown in the workbench's Now tab. The owner must be an editor on the project. Overdue experiments show on Project home under Needs attention.

3. Log evidence in the tracker

   Open the experiment's workbench, then Data tracker → Open tracker. In Log evidence:

   • Add row to type one result.
   • Paste rows from a spreadsheet.
   • Import CSV file for a batch; map its headers to the tracker's columns.
   • Columns to review the structure; Export CSV to take the data out.

   Or ask your AI tool: "Add these results to the SwiftCNS tracker: [rows]".

   

4. Complete the tracker

   When the sample is in or time is up, choose Complete tracker on the card or in Now. It saves a fixed snapshot of the rows and moves the experiment to learning. You can still open the tracker to read it.

What you get

A live picture of what your team is testing, who owns each test and what's late, with evidence for each kept in one place. In the running example, "Paid Team offer at invite" sits under decided, owned by the person who ran it.

Done when

• Every running experiment has an owner and a due date.
• Evidence goes into the tracker as it arrives, not at the end.

Common mistakes

• Collecting in a side spreadsheet and importing at the end. You lose the timeline of when evidence arrived.
• Completing early to "see what it says". Completing is final; finish the sample first.

For agents: MCP tools and gotchas

• list_experiments, get_experiment (status, owner, dueAt, metrics).
• get_data_tracker, list_data_tracker_rows, add_data_tracker_rows, update_data_tracker_row; CSV via preview_data_tracker_import then import_data_tracker_rows.
• complete_experiment submits the mark_complete request.

Next

Learnings and Decisions.