Implementation: Fidelity, Adaptation, and Monitoring
What this domain tests
Implementation is where a sound plan meets real workflows. Candidates must understand core components (elements that must be delivered as designed) versus adaptable periphery, and the trade-off between fidelity-delivering intended content, dose, and quality-and adaptation to local context. Adaptation should be purposeful, documented, and tied to a specific barrier; unplanned drift is a threat.
Know the machinery: staff training and competency checks, protocols and job aids, workflow integration, caseload and staffing ratios, point-of-service data collection, supervision, and rapid-cycle improvement such as plan-do-study-act. Understand reach, dose delivered, dose received, and participant responsiveness as distinct measures. Risk management should cover consent, privacy, safety escalation, and continuity during staff turnover.
Traps
Common distractors confuse a pilot with full rollout, treat training attendance as competence, or claim a program was implemented because materials were distributed. Another trap recommends mid-course adaptation with no measurement plan, or assumes strong fidelity guarantees outcomes regardless of reach.
Rule of thumb
Track three numbers weekly: how many were eligible, how many were reached, and how much of the intended dose they received. A shortfall in any one explains most disappointing results.
Worked example
A clinic trained 40 staff, but only 12 delivered the screening. Documentation showed the form added six minutes to each visit. The defensible response is to shorten or automate the form, retest it with one team, and monitor delivery-not to retrain everyone or declare the program ineffective.