Systems Thinking
What this domain tests
Systems thinking means seeing patterns, relationships, and structures rather than isolated events, and intervening where leverage is highest. Candidates should understand micro-, meso-, and macro-level systems; structure-process-outcome framing (Donabedian); process mapping; variation; and the Model for Improvement with PDSA cycles.
Know the improvement tools cold, because questions trade on their differences: root cause analysis is retrospective after harm; failure mode and effects analysis (FMEA) is prospective and risk-weighted; plan-do-study-act is small-scale iterative testing. Add just culture, human factors, and reliability science - bundles, checklists, standardization, and independent double-checks. Familiar nursing-sensitive indicators, staffing models, throughput, length of stay, and readmission penalties, since these tie practice change to organizational outcomes.
Traps: choosing a person-focused fix ('re-educate the nurse,' 'write up the offender') for a latent system condition; substituting education for process redesign; confusing a process measure with an outcome measure; and approving a change without a balancing measure for the unintended consequence.
Rule of thumb - ask the substitution test: if three different competent people made the same error, the error lives in the system. Find the latent condition before assigning blame.
Worked example: three hypoglycemia events occur on one unit across different nurses and shifts. The systems move is to map the workflow, identify the latent condition (an insulin order set lacking a glucose parameter or a basal dose overlapping with mealtime coverage), then test a redesigned protocol with a PDSA cycle and track both hypoglycemia rates and glucose control as a balancing measure.