Learning Question → Experiment Planning Form

An interactive, saveable experiment-planning form that converts KPI observations into short, hypothesis-driven experiments with owners, success criteria, and timeboxes. Designed to be completed during KPI huddles and to store results for organizational memory.

Interactive Tool

Learning Question → Experiment Planning Form

This form helps teams turn KPI observations into focused, testable learning cycles. Use it during KPI huddles to capture the observation, write a clear learning question and hypothesis, design a compact experiment, assign an owner, set measurable success criteria, and timebox the work. Return to this form to record results and learnings so insights feed organizational memory.

Describe the KPI, dashboard tile, or observation (what changed, when, value, and where). Include a link or dashboard name if available.
Write a specific question about what you want to learn (what uncertainty or assumption are you testing?).
State a testable hypothesis. Use the template: If we [change], then [expected measurable outcome], because [rationale].
Describe the minimal, timeboxed experiment steps (what, who, how long, sample size or scope, and control if applicable). Keep it compact and feasible within the timebox.
List primary and secondary metrics, how they will be measured, and measurement frequency (e.g., daily conversion rate, sample size).
What data, events, tags, dashboard updates, or tracking must exist to measure the experiment? Note any quick instrumentation steps required.
Define clear, measurable success criteria (include thresholds, direction, and required confidence where appropriate). Example: Increase conversion by >= 0.5 percentage points vs control over 7 days.
Who is accountable for running the experiment, collecting data, and reporting results? Include contact info or role if helpful.
Quickly indicate relative priority for scheduling experiments during huddles.
Rough estimate of effort to implement and run the experiment (hours). Use this to help prioritize.
How long will the experiment run before evaluating results? Keep experiments short where possible.
Optional: approximate end date for scheduling and follow-up. Use YYYY-MM-DD format.
List potential risks, negative impacts, or required approvals and how you'll mitigate them.
Track experiment lifecycle. Update this when moving from proposed to in-progress to completed.
Summarize outcomes, whether success criteria were met, key learnings, next steps, and recommended decisions. Leave blank until the experiment is complete.
Optional: date the experiment was recorded. If left blank the system may stamp creation date.
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.

Discussion

Comments and conversation will live here.