Before/After Case Study Template

A practical, structured before/after case-study template with guided prompts, metric guidance, anonymization checklist, visual suggestions, reproducible artifacts list, and adaptation notes so teams can capture transformations with the context and implementation detail others need to adopt the pattern responsibly.

Before / After Case Study Template

Use this template to document a transformation so other teams can evaluate, adapt, and reproduce a pattern with realistic expectations. Keep answers concise but concrete: name sources, cite metrics and timeframes, and note assumptions or constraints.

1. Headline & Executive Summary

Headline: One-line summary of change and primary outcome (e.g., "Reduced average machine changeover time by 45% — saving 8 production hours/week").

Executive summary (3–5 sentences): Brief context, what was done, key quantitative outcome(s), and sustainment status.

2. Problem Statement (Context & Why It Mattered)

  • Describe the operational, customer, financial, safety, or quality problem in plain language.
  • Scope: which site/line/team/process/customers were affected?
  • Constraints or critical dependencies (e.g., regulatory, union agreements, legacy systems).

3. Baseline Metrics (Before)

List measurements, units, data sources, and measurement windows used to define the baseline.

  • Primary baseline metric(s): value, unit, date range, source (e.g., ERP, MES, manual logs).
  • Secondary/contextual metrics: variation, sample size, known data quality issues.
  • How baseline was validated (spot checks, audit, stakeholder confirmation).

4. Intervention Description

Describe the change clearly enough for another team to evaluate feasibility.

  • What was implemented? (procedures, tools, equipment, roles, training, software, dashboards)
  • High-level timeline: major milestones with dates.
  • Owners and roles: who sponsored, who led, who executed, who maintained?
  • Key decisions and trade-offs (what was explicitly excluded or deferred).

5. Experiments, Pilots, and Tests Run

Document both formal experiments and informal trials.

  • Hypothesis for each experiment (what you expected).
  • Design (sample, control/comparison, duration).
  • Results and interpretation (including unexpected outcomes).

6. Outcomes (Quantitative & Qualitative)

Report results with the same definitions used for baseline.

  • Primary outcome(s): before and after values, percent change, time windows, and data sources.
  • Secondary outcomes and leading indicators (e.g., error rates, cycle time, customer satisfaction).
  • Qualitative effects: staff feedback, customer anecdotes, changes in behavior or culture.
  • Confidence and statistical vs operational significance (e.g., sustained over X weeks).

7. Adoption & Sustainment Tactics

How the improvement was embedded into daily operations.

  • Training and documentation provided.
  • Process controls, checklists, or audits instituted.
  • Ownership and handoff plan (who is responsible for ongoing performance).
  • Monitoring: which KPIs are tracked, cadence, and escalation thresholds.

8. Learned Countermeasures (What Prevents Backsliding)

  • Risks identified after implementation and steps taken to mitigate them.
  • Trigger conditions for re-evaluation or rollback.

9. Reproducible Artifacts (What to Copy)

Attach or link to tangible artifacts that other teams can reuse:

  • Standard operating procedures, templates, checklists, training slides, data-extraction queries.
  • Before/after visuals: charts with labeled axes and data ranges, annotated photos, workflow diagrams.
  • Code, scripts, or configuration files (sanitized or anonymized).

10. Anonymization & Confidentiality Checklist

Ensure the case study is shareable while protecting privacy and IP.

  1. Remove or generalize customer names, supplier IDs, and employee identifiers.
  2. Replace specific financial figures with ranges if required by policy.
  3. Strip or sanitize screenshots that reveal internal systems or credentials.
  4. Get approvals from legal, privacy, or commercial teams as required.

11. Scope, Assumptions & Transferability Notes

Help readers decide whether the pattern is relevant to them.

  • Key assumptions behind success (skill levels, available tools, culture).
  • Boundaries: where this approach likely applies and where it probably won't.
  • Suggested adaptations for different scales, industries, or regulatory environments.

12. Quick Narrative Template

Use this short narrative when publishing internally or externally:

"Context: [one sentence]. Challenge: [one sentence]. Intervention: [one sentence]. Result: [one sentence with metric]. Sustainment: [one sentence]."

13. Suggested Visuals & Data Presentation

  • Before/after time-series chart with consistent axes and annotation of when interventions occurred.
  • Before/after KPI table with data sources and measurement windows.
  • Process flow diagrams highlighting removed steps or added controls.

14. Common Mistakes to Avoid

  • Reporting percentages without units or time windows.
  • Failing to describe data sources or validation methods.
  • Presenting an isolated anecdote as generalizable proof.

15. Optional Annexes

Attach supporting files or links: raw data extracts, experiment logs, stakeholder approvals, and templates referenced above.


Tip: When converting this template into a team-specific collection, consider adding an interactive submission form so contributors provide the required fields consistently (baseline definition, data source, owner, attachments).


Discussion

Comments and conversation will live here.