Tool

PDCA Experiment Tracker & Results Dashboard

Interactive tracker to plan, run, record, and evaluate small PDCA experiments. Capture hypothesis, planned change, baseline and post-results for up to three measures, record lessons, and decide whether to adopt, adjust, or abandon. Submissions are saved for later review and dashboarding.

Interactive Tool

PDCA Experiment Tracker & Results Dashboard

Use this form to design and record small experiments using the PDCA cycle. Write a clear hypothesis, define the change you will test, record baseline measurements, collect results, and capture lessons so your team can learn and act quickly. You can enter up to three measured outcomes (common, practical measures work best).

Charting tip: For numeric measures, capture baseline and after values here. For richer charts, link this experiment to ongoing time-series data (see CapabilityEnhancementNotes).

Person or team responsible for the experiment (name, role, or team).
Short, descriptive title that helps people find this experiment later.
State the testable expectation and the reason. Example: 'If we reduce batch size to X, then changeover time will drop by 20% because smaller batches reduce setup iterations.'
Describe exactly what you will change, who will do it, and how. Include steps and any materials or approvals required.
How many days or work cycles you plan to run the test.
Use a date format that works for your team (e.g., YYYY-MM-DD).
Primary measure you expect to change (e.g., cycle time, defects per batch, on-time %).
Units for the measure (e.g., minutes, %, defects/unit).
Baseline measurement before the experiment (numeric).
Value collected after running the experiment (numeric).
Context for the measure: how it was measured, sample size, or special conditions.
Optional secondary measure.
Optional tertiary measure (e.g., safety indicator, quality defect type).
Summarize what happened during the experiment and the key outcomes. Mention any deviations from the plan.
What insights did the team gain? What unexpected issues appeared? What should be done differently next time?
After reviewing results, choose whether to adopt the change, adjust and re-test, or abandon it.
Rate how confident the team is in the decision (1 = low, 5 = high).
Record next steps, owners, and target dates for standardization, further testing, or rollback.
Anything that prevented a clean test or could affect scaling the change.
Short summary (1–2 sentences) the dashboard should show to help leaders understand the outcome at a glance.
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.