Template Pack

Micro‑Experiment Sprint Kit

Runbook, templates, and an interactive experiment submission form for 1–2 week micro‑experiment sprints. Capture hypotheses, instrumentation, decisions, and post‑mortems so teams can build an organizational memory of validated learning.

Interactive Tool

Micro‑Experiment Run Submission

Micro‑Experiment Sprint Kit — Interactive Submission

This interactive form captures a single micro‑experiment run from hypothesis through decision and post‑mortem. Use it each sprint to store experiment design, instrumentation, daily notes, decision outcomes, and learnings so your team builds reusable organizational intelligence. The form follows core sprint principles: one primary assumption, a measurable success metric, minimal viable test, clear owners, and a pre‑agreed decision rubric.

Hints: Complete the required fields before launch (hypothesis, primary metric, instrumentation). If sample sizes are small, record confidence explicitly. For operational pilots, add safety/compliance checks in the instrumentation and owner fields. To make this kit part of your domain, copy the Template Pack and tailor fields or add separate Daily Run Log and Scale Run templates.

One line describing what you are testing.
What problem or opportunity does this address? Be specific about customer, process, or metric.
The specific belief you're testing (e.g., 'Users will sign up for a waitlist when shown price and ETA').
Format: If we do X, then Y will happen (measured by Z) within [timeframe].
Metric to measure the hypothesis (leading indicator).
How the metric is calculated and where the data lives.
Numeric or descriptive threshold that would be considered a 'Validate' outcome.
Supportive metrics or interview themes to look for.
Describe the smallest thing that could produce the signal (landing page, concierge, prototype, ad, etc.).
Who will see the test and approximate sample size or timeframe.
Numeric estimate (enter 0 if not applicable or unknown).
Planned start date or sprint day (text is fine).
Planned end date or sprint day.
List events, properties, forms, and any A/B elements. Note where data will be stored and who is the data owner.
Record baselines (current conversion, usage, or behavior) to compare post-test.
Who owns the data and where reports will be stored (link or path).
Person responsible for hypothesis framing, timeline, and delivering results.
Names and responsibilities (facilitator, data lead, customer contact, sponsor).
Short daily notes: issues, anomalies, qualitative highlights. Use the dedicated Daily Run Log template for detailed entries.
Link or describe the pass/hold/kill thresholds agreed before launch.
Select the outcome after analysis.
Primary metric result, key secondary signals, and any data quality issues. Paste chart links or report locations.
Was the instrumentation and data collection verifiable and complete?
What you learned about customers, product, process, or market. Be explicit and actionable.
Open questions and risks to be addressed in follow up actions.
Conclude with clear owners, due dates, and success measures for the next step.
Rate how confident the team is in this result given sample size and data quality.
1.0 10.0
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Sign In to Save Create an Account
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.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.