Before/After Case Study Template

A structured interactive template to author annotated before/after case studies that capture context, baseline, diagnosis, actions, timeline, measurable outcomes, sustainment practices, reproducibility notes, and practical resources. Collects consistent fields so teams can adapt, compare, and reuse proven approaches.

Interactive Tool

Before/After Case Study Template

Write a practical, reproducible before/after case study

Use this form to capture the essential elements that make a transformation useful to other teams: what the context and baseline were, how the problem was diagnosed, what actions were taken, how outcomes were measured, and what was done to sustain the improvement. Aim for clear, actionable descriptions and concrete metrics. Avoid promotional language—document trade-offs, resources, timelines, and any special assumptions.

Suggested lengths: Executive summary ~75–200 words; other text fields as needed. If parts are confidential, mark them below. You can submit now and return later to edit.

Who is submitting this case study? Include role or team.
Optional — helpful if reviewers need clarification.
Where did this work occur? Department, plant, or team.
Short descriptive title (e.g., 'Reduce rework on Line 3 by 45% in Q2').
Briefly describe the situation, what changed, and the primary outcome. 75–200 words suggested.
Describe the environment, scale, baseline performance, constraints, customers affected, and any relevant history. Include baseline numeric values when available.
What specific problem or opportunity did you address? Who noticed it and why did it matter?
What analysis or investigation led you to choose the solution(s)? Mention methods used (e.g., Pareto, 5 Why, process mapping, data analysis) and key findings.
Describe the specific changes, decisions, process steps, roles, tools, materials, and resources used during implementation. Be concrete enough for another team to try the same approach.
Enter start date (YYYY-MM-DD).
Enter end or evaluation date (YYYY-MM-DD).
Short timeline of key milestones, approvals, pilot phases, and major events.
Primary metric to show impact (e.g., 'Defect rate', 'Throughput', 'Cost per unit').
Numeric baseline value before changes. Add units in the next field.
Numeric value after implementation (same measurement method).
Unit or percent (e.g., %, items/hour, $/unit).
How was this metric measured? Data sources, sampling, any smoothing or normalization used.
Optional secondary metric (e.g., 'Cycle time', 'Customer complaints').
What was done to sustain improvements? Document standard work, ownership, audits, training, controls, or system changes that keep the gains.
What contextual factors, assumptions, or special capabilities must another team consider before trying this? Mention dependencies and preferred preconditions.
Key insights, surprises, trade-offs, and what you would do differently next time.
People, time, equipment, software, external support, and an estimated total cost (use numbers and currency where possible).
Optional numeric estimate (enter a number, e.g., 12500). Mention currency in Resources field if needed.
Reference manuals, SOPs, diagrams, dashboards, or templates that support reproduction. Paste URLs or inventory names.
Suggested phrase for a representative image (e.g., 'assembly line 3 improvement before/after').
Mark 'Yes' if it contains proprietary or sensitive information that should not be published publicly.
If confidential, do you consent to provide a redacted public summary for wider learning?
Optional: anything the curator should know when reviewing or publishing this case study.
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
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.

Discussion

Comments and conversation will live here.