Explore an example use of a driver diagram, including the formulation of an aim statement with SMART goals. Then learn how your team can identify primary and secondary drivers that impact your quality improvement goals. You can learn more about identifying primary drivers by exploring fishbone diagrams and root cause analysis.
Transcripts
1
00:00:07.035 –> 00:00:10.075
A driver diagram is a visual framework that helps teams
2
00:00:10.595 –> 00:00:11.795
organize their improvement efforts.
3
00:00:12.855 –> 00:00:14.915
It connects a project’s overall aim
4
00:00:15.215 –> 00:00:18.195
or the goal you want to achieve with the primary drivers,
5
00:00:18.205 –> 00:00:21.955
which are the key factors or domains influencing that aim.
6
00:00:22.925 –> 00:00:26.035
These primary drivers are then broken down further into
7
00:00:26.035 –> 00:00:29.835
secondary drivers, which represent specific actionable steps
8
00:00:29.835 –> 00:00:31.635
that teams can take to make an impact.
9
00:00:32.585 –> 00:00:33.895
Let’s apply this to a healthcare
10
00:00:33.895 –> 00:00:35.015
quality improvement project.
11
00:00:35.965 –> 00:00:40.255
Imagine our aim is to reduce 30 day hospital readmissions
12
00:00:40.275 –> 00:00:41.895
by 3% in the next year.
13
00:00:42.835 –> 00:00:46.285
Importantly, aim statements should be framed as smart goals.
14
00:00:47.175 –> 00:00:50.405
Smart goals are specific, measurable, achievable,
15
00:00:51.125 –> 00:00:52.165
relevant, and timely.
16
00:00:52.785 –> 00:00:56.085
In this example, a driver diagram could help us identify the
17
00:00:56.085 –> 00:00:58.405
major factors that influence readmissions.
18
00:00:58.815 –> 00:01:01.125
These could include things like effective discharge
19
00:01:01.365 –> 00:01:04.525
planning, post-discharge, follow-up, and patient education.
20
00:01:05.185 –> 00:01:06.575
These are our primary drivers.
21
00:01:07.865 –> 00:01:09.595
Your team can use a variety of tools
22
00:01:09.595 –> 00:01:11.515
and frameworks to identify primary drivers.
23
00:01:12.695 –> 00:01:15.885
These might include the five why’s, a root cause analysis,
24
00:01:16.445 –> 00:01:17.445
a fishbone diagram,
25
00:01:18.065 –> 00:01:21.715
or other forms of brainstorming for each primary driver.
26
00:01:21.935 –> 00:01:24.835
We then list out specific secondary drivers, such
27
00:01:24.835 –> 00:01:27.395
as scheduling follow-up calls within 48 hours,
28
00:01:28.195 –> 00:01:29.675
ensuring medication reconciliation
29
00:01:29.895 –> 00:01:32.115
or creating patient friendly discharge instructions.
30
00:01:32.785 –> 00:01:35.075
This framework not only helps us understand the
31
00:01:35.075 –> 00:01:37.635
relationships between different actions and outcomes,
32
00:01:38.175 –> 00:01:40.995
but also ensures that everyone on the team from frontline
33
00:01:40.995 –> 00:01:42.995
staff to leadership is aligned
34
00:01:43.015 –> 00:01:44.475
and working toward the same goal.
35
00:01:45.795 –> 00:01:48.095
So whether you’re tackling infection prevention,
36
00:01:48.285 –> 00:01:50.055
improving patient satisfaction,
37
00:01:50.195 –> 00:01:52.015
or optimizing workflow efficiency,
38
00:01:52.855 –> 00:01:55.935
a driver diagram helps break the problem into manageable
39
00:01:55.935 –> 00:01:57.895
parts while keeping the big picture in sight.