5.8 Knowledge Check


Take the Knowledge Check


  1. What are the three components that a Key Driver Diagram connects?
  2. Which of the following best describes a “Key Driver” in a KDD?
    1. A specific, testable action your team will try
    2. A major factor that influences whether you’ll reach your aim
    3. A tool used to collect measurement data
    4. A formal policy change
  3. True or False: Change ideas should be broad, high-level strategies rather than specific, testable actions.
  4. In the Effort/Impact Matrix, which type of change idea should generally be tackled first?
    1. High Effort / High Impact
    2. Low Effort / High Impact
    3. Low Effort / Low Impact
    4. High Effort / Low Impact
  5. When should a team typically build its Key Driver Diagram?
    1. Before the AIM statement is written
    2. After the AIM is defined and before launching change ideas
    3. Only after PDSA testing is complete
    4. Timing doesn’t matter

  1. Did this module help you identify potential key drivers or change ideas in your current work?

Knowledge and Awareness

  1. 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.
  2. B) A major factor that influences whether you'll reach your aim.
  3. False — change ideas should be specific, testable actions (the “hows”); key drivers are the broader “whats” that change ideas act on.
  4. B) Low Effort / High Impact — these “quick wins” generally get tackled first because they deliver the most value for the least resource investment.
  5. 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

  1. 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.