Module 5
Take the Knowledge Check
- What are the three components that a Key Driver Diagram connects?
- Which of the following best describes a “Key Driver” in a KDD?
- A specific, testable action your team will try
- A major factor that influences whether you’ll reach your aim
- A tool used to collect measurement data
- A formal policy change
- True or False: Change ideas should be broad, high-level strategies rather than specific, testable actions.
- In the Effort/Impact Matrix, which type of change idea should generally be tackled first?
- High Effort / High Impact
- Low Effort / High Impact
- Low Effort / Low Impact
- High Effort / Low Impact
- When should a team typically build its Key Driver Diagram?
- Before the AIM statement is written
- After the AIM is defined and before launching change ideas
- Only after PDSA testing is complete
- Timing doesn’t matter
- Did this module help you identify potential key drivers or change ideas in your current work?
Knowledge and Awareness
- A Key Driver Diagram connects the team's AIM, the Primary (Key) Drivers that influence reaching it, and the Secondary Drivers and/or Change Ideas that put those drivers into action.
- B) A major factor that influences whether you'll reach your aim.
- False — change ideas should be specific, testable actions (the “hows”); key drivers are the broader “whats” that change ideas act on.
- B) Low Effort / High Impact — these “quick wins” generally get tackled first because they deliver the most value for the least resource investment.
- B) After the AIM is defined and before launching change ideas — the KDD translates a clear AIM into the drivers and ideas the team will actually test.
Reflection
- This is a reflection question with no single correct answer. A strong response names a specific driver or change idea relevant to the learner's own workflow (e.g., the ED telepsychiatry consult line scenario) and briefly explains why the module's KDD structure (Aim → Primary Drivers → Secondary Drivers → Change Ideas) helped clarify it.