Template

Continuous Improvement Experiment Tracker

An interactive, fillable experiment template to run disciplined CI experiments: capture hypothesis, baseline, measurement plan, step-by-step run instructions, collected data (paste or summarize), results, and concrete sustainment actions so improvements become measurable and repeatable.

Interactive Tool

Continuous Improvement Experiment Tracker

Use this tracker to design, run, measure, and sustain short experiments that turn ideas into reliable day-to-day improvements. Be specific about the hypothesis, how you will measure success, how long you will run the test, and who will own follow-up. Where possible capture before-and-after data so the team can see what actually changed.

Give this experiment a clear, searchable name (e.g., 'Reduce setup time on Press A').
Person responsible for running the experiment and following up (name and role).
People or teams to inform or involve (comma-separated).
Use YYYY-MM-DD or describe the planned start. (Date fields may integrate in future versions.)
Planned end date or run length (e.g., '2 weeks' or a date).
Describe the real outcome you hope to improve (customer need, waste to reduce, quality failure, downtime, etc.).
State a simple, testable hypothesis in 'If we... then...' form, including the signal you expect to change.
What exactly will you measure (e.g., 'average setup time (minutes)', 'first pass yield %', 'downtime minutes per shift').
Explain how to compute the metric from raw observations or system values so everyone measures the same way.
Current value measured before the experiment (use the same units as the metric). If unknown, describe how you'll determine baseline in the data collection plan.
The period used to calculate baseline (e.g., 'last 30 days', 'last 5 shifts').
Numeric target or improvement goal (e.g., reduce from 12 to 8 minutes). If percentage or ratio, enter the numeric value (e.g., 20 for 20%).
Be explicit: what will count as success? Include confidence or sample-size guidance if appropriate.
Step-by-step instructions the team will follow during the experiment. Include who does what, when, and any control conditions.
List forms, equipment, permissions, data access, or training needed to run the test.
How often you'll collect or record measurements during the run.
Describe who will collect data, what tools they'll use, where values will be stored, and any sampling rules. If you plan to paste a CSV summary, paste it in the Data points field below.
Paste measured values, a short CSV, or a summarized table (e.g., 'shift1: 12, shift2: 9, ...'). If you have a system, note where the raw data lives for later analysis.
Summarize what happened: observed changes, unexpected effects, and any contextual notes that could explain the result.
Yes = target achieved as defined in success criteria. No = target not met.
If applicable, indicate whether results appear statistically meaningful or require further testing.
What did the team learn about the process, people, materials, or measurement? List root causes surfaced or constraints discovered.
If the experiment succeeded, what steps will make the change part of standard work? If it failed, what next steps will you take? Be specific about changes to SOPs, checklists, training, or control plans.
Check items the team completed to sustain improvement.
When the team will review the experiment outcome and confirm sustainment (YYYY-MM-DD or descriptive).
Note folder, system, or link where raw data, photos, or additional files are stored (do not paste heavy files here).
Ideas for the next run, recommended adjustments, or hypotheses to explore next.
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.