Template

PDCA Experiment Template & Evaluation Record

An interactive experiment planning and evaluation form to design, run, and record short PDCA cycles. Collects hypothesis, plan, measurement details, results, lessons learned, and a clear adopt/adjust/abandon decision so teams can make fast, evidence-backed choices and build a searchable experiment history.

Interactive Tool

PDCA Experiment Record

Use this form to plan, run, and record short PDCA experiments. Keep experiments focused, measurable, and timeboxed. Record baseline data, collection methods, and clear success thresholds so results are unambiguous.

Short descriptive name (where and what change).
Person accountable for running the test.
YYYY-MM-DD or approximate.
YYYY-MM-DD or approximate. Keep experiments short where possible.
If we do X, then Y will change by Z because... (state expected mechanism).
Step-by-step actions, who performs them, timing, and any controls.
Typical short experiments: 7–14 days; adjust to metric frequency.
The single measure used to decide success (e.g., defect rate, cycle time).
Current value of the primary metric before the test.
Quantitative threshold (e.g., +10%, delta >= 5 units) required to call the test successful. Be specific.
Practical minimums: for event counts consider 30–50 events; for rates or proportions use larger samples. Record your chosen minimum.
Prefer randomization to avoid bias. If not possible, explain why.
What exactly will be collected, how, where it's stored, and who collects it. Include timestamps, identifiers, and measurement frequency.
Summarize observations and any notable events during the test.
If A/B-style test, enter control outcome as numeric value.
If A/B-style test, enter treatment outcome as numeric value.
Optional: p-value, confidence interval, or practical significance notes. If not using formal stats, explain your practical decision rule.
What worked, what didn't, surprises, and operational considerations for scaling.
Action items, owners, and deadlines if adopting or adjusting.
e.g., line ID, shift, process area, technology. Helps future search and grouping.
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.