← All articles
Business Presentations

Presentation for quality improvement

A practical guide to preparing a quality improvement project presentation: audience analysis, DMAIC and PDSA structure, data visualization, and sharing lessons learned.

Draw Editorial Team7 min read

Preparing a quality improvement project presentation is the process of conveying operational breakdowns, implemented test cycles, methodological steps, and measurable gains to stakeholders. Unlike standard status updates or sales pitches, a quality improvement (QI) presentation places proven quality methodologies, process maps, and time-series trends at its center to steer the audience toward taking action and institutionalizing change.

Core Dynamics of a Quality Improvement Presentation

General corporate presentations often focus solely on bottom-line outcomes or financial results. In contrast, a quality improvement presentation tells the story of the learning journey. Initial failed attempts, tested hypotheses, and process adaptations are integral components of the presentation. According to guidelines from the Institute for Healthcare Quality Improvement (IHQI), an effective QI presentation does not merely deliver a report; it shares the purpose, methods, data, and impact of the initiative. It drives organizational action by communicating SMART aims, the theory of change, process data, and lessons learned across PDSA (Plan-Do-Study-Act) cycles.

When putting your presentation together, you should avoid confusing the project's scope with audit and routine assurance phases. If your initiative is focused on upholding overall system standards, you can examine the steps for preparing a quality assurance presentation; if you are summarizing periodic measurement outputs, you can benefit from our guide on presenting quality control results.

Audience Analysis and Messaging Strategy

A successful presentation must be tailored to the organizational priorities of the listeners. Different stakeholder profiles identified in primary sources hold the following expectations:

  • Senior Executives: Return on investment (ROI), strategic alignment, risk mitigation, and the sustainability of gains.
  • Physicians and Clinical Experts: Clinical validity, dependable datasets, and tangible outcomes on patient health.
  • Nurses and Frontline Staff: Impacts on daily workflow, feasibility, teamwork, and workload balance.
  • Quality Improvement Leaders: Methodological rigor, data collection strategy, PDSA learning cycles, and potential for scaling change across other units.
  • Mixed Audiences: A balanced narrative must be constructed so representatives from each group find elements relevant to their own priorities.

Preparation Process and Methodological Prerequisites

Before moving to slide design, you need to compile the project's evidence base thoroughly:

  • Selecting a framework: Depending on your organization's methodological preference, determine whether to use Lean Six Sigma-based DMAIC (Define, Measure, Analyze, Improve, Control) or the Model for Improvement-based PDSA cycle. UC Davis CTSC resources emphasize structuring continuous quality improvement initiatives through data-driven models like DMAIC and scoping them with a project charter.
  • Baseline and post-intervention data: Pre-intervention baseline and post-implementation measurement records must be collected to demonstrate process improvement.
  • Theory of change documentation: The project charter, process flow maps, and driver diagrams should be kept ready.
  • Time planning: Although presentation guides frequently offer a focused 7-minute presentation framework, the duration should be adapted to your organization's format and must leave dedicated room for audience discussion.

Storytelling and Slide Architecture

A logical presentation flow reflecting the quality improvement journey follows this slide structure:

  1. Problem Definition and Context: The operational or user impact of the problem. A meaningful employee or user case that speaks to the audience and reflects the process behind the statistics.
  2. SMART Aim and Theory of Change: The SMART goal and driver diagram indicating what you intend to improve, in what timeframe, and by what percentage.
  3. Changes Tested: Which interventions were selected, pilot tests executed, and PDSA stages completed.
  4. Data and Results: Clear visual analyses displaying the intervention point and change over time.
  5. Lessons Learned: Candid assessments of what worked, what failed, and why.
  6. Next Steps and Spread: Standardization of gains, opportunities for spreading to other units, and a call to action.

Data Visualization and Essential Tools

The purpose of visuals used on slides is not to overwhelm with information, but to reinforce the core message. Instead of complex tables, the following tools should be preferred:

  • Process Maps: Illustrate existing operational steps and intervention points through a clear flow.
  • Driver Diagrams: Document the logic of change by linking the project aim to primary drivers and secondary interventions.
  • Run Charts and Control Charts: Visualize that improvement is not a random fluctuation, but that a sustained shift in the process average or variation occurred following the intervention.
  • Column and Bar Charts: Suitable for keeping comparisons straightforward across different categories or before-and-after interventions.

Case Example: Call Center Resolution Time Improvement

Below is an example 6-slide outline for a fictional operational support department's quality improvement presentation:

Slide 1: Title and Team. "Optimizing Customer Support Resolution Times: Call Operations QI Project." Team members and project leads are identified.

Slide 2: Problem and SMART Aim. Fictional data: First-contact resolution rate is at 52%. Fictional SMART Aim: Increase the first-contact resolution rate to 75% within 4 months and reduce average wait time below 10 minutes.

Slide 3: Root Cause and Theory of Change. Driver diagram and analysis: Knowledge base update delays, sign-off approval steps, and system response latencies are listed as primary delay drivers.

Slide 4: PDSA Cycles and Implemented Changes. Cycle 1: The updated knowledge base was tested with a 5-person pilot group. Cycle 2: Approval authorities were delegated to call representatives within set limits. Old and new process steps were compared with a flowchart.

Slide 5: Results. The intervention launch point is marked on a run chart. Fictional data: First-contact resolution increased from 52% to 78%, while average wait time declined.

Slide 6: Lessons Learned and Sustainability. Lessons learned from authorization errors encountered during the initial pilot rollout, updated standard operating procedures (SOP), and a rollout plan across all shifts are presented.

Common Pitfalls and How to Fix Them

The most frequent mistake in quality improvement presentations is concealing failed tests or unexpected results. In quality improvement methodology, an unsuccessful test cycle is not a loss, but a critical learning outcome. Transparently share trials that did not work and how they shaped the project.

Another common mistake is presenting only a single before-and-after metric. Standalone measurements can mask the natural variation or seasonality of a process. To demonstrate that change is sustainable, incorporate run charts or control charts reflecting trends over time.

Crowding slides with excessive text and intricate tables makes it difficult for the audience to stay focused. Instead of lengthy descriptions, adopt flowcharts, driver diagrams, and clean graphic layouts.

Validation and Pre-Presentation Checklist

  • Is the SMART aim defined on the slide with a clear rate, direction, and timeframe?
  • Were the messaging and points of emphasis adapted to the priorities of the audience (leadership, clinicians, frontline staff)?
  • Does the theory of change or driver diagram align with the interventions implemented?
  • Were the tested PDSA cycles and the lessons extracted from them summarized transparently?
  • Are intervention launch points and time-series trends clearly displayed on charts?
  • Were slides cleared of dense text, maintaining a clean and streamlined visual layout?
  • Was the presentation timing planned to leave sufficient room for audience engagement and questions?

Frequently Asked Questions

How long should a quality improvement presentation last?

In academic and corporate guidelines, quality improvement presentations are commonly structured around a core narrative framework of approximately 7 minutes. However, this duration can be shortened or extended according to your organization's meeting format; time must always be allocated for audience questions and discussion.

Is it necessary to show unsuccessful trials in the presentation?

Yes. The goal of a quality improvement presentation is to convey the learning journey, not just the final success. Showing which intervention failed to work, why, and how you adapted the process increases the credibility and methodological merit of the presentation.

Which visualization tools should be chosen for charts?

To demonstrate trends over time and the impact of interventions, run charts and control charts are recommended. Process maps should be used for workflow steps, and driver diagrams should be utilized for the project's logical framework.

← Back to blog