Tool

Experiment Tracker (Interactive Template)

A structured, saveable experiment form to log hypotheses, owners, dates, results, links, and next steps so improvement work stays visible and repeatable.

Interactive Tool

Experiment Tracker

Use this form to record experiments so your team can capture hypotheses, owners, results, links to data, and next steps. Keep experiments visible during weekly continuous improvement (CI) reviews: sort or filter by status and start date to prioritize follow-up. Suggested ID format: EXP-YYYY-### (team may adopt another scheme).

Tips: write a measurable hypothesis (what you expect to change and how you will measure it), include links to raw data where possible, and mark experiments that are standardized so they can be added to Standard Work.

Team-assigned identifier. Suggested format EXP-YYYY-### (required to make records easy to reference).
A concise title that summarizes the experiment (one line).
Person responsible for running the experiment and reporting results (name or role).
Where the experiment takes place (machine, cell, line, product family, or process).
Enter date in YYYY-MM-DD format. (If your platform supports date pickers, this could be upgraded.)
Planned or actual end date in YYYY-MM-DD format (leave blank if ongoing).
Current stage of the experiment. Use this to filter during CI reviews.
Helps teams decide what to act on during limited review time.
State the hypothesis and the metric you will use to test it. Example: 'If we change X, cycle time will decrease by 15% measured as average seconds/unit.'
Summarize outcome and key data points. Include whether the hypothesis was supported and by how much.
Mark Yes if the experiment outcome has been adopted into Standard Work or procedures.
Paste URLs or location references for dashboards, spreadsheets, photos, or test logs.
Concrete next actions, who will do them, and by when. Useful for follow-up at the next CI review.
Practical insights, cautions, or changes to try next time. These are the items you want to preserve as organizational knowledge.
Comma-separated keywords to help categorize experiments (e.g., changeover, poka-yoke, maintenance).
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.