Leadership, Communication, and Education
Core concepts
Leadership items test judgment about people and process. Know situational leadership - directing, coaching, supporting, and delegating as a person's competence and commitment change - and the distinction between transactional and transformational approaches. Change management frameworks such as Kotter's steps emphasize urgency, coalition building, and short-term wins; exam answers generally favor early involvement of frontline staff over top-down announcement.
Project management basics matter: charter, scope, stakeholders, roles and responsibilities, risk register, milestones, and post-implementation review. Communication upward should be framed in clinical and financial terms, not in engineering detail; SBAR (situation, background, assessment, recommendation) works well for escalations.
Education is where many candidates lose points. Competency is not attendance. A defensible program defines required competencies by role, verifies them through observation, testing, or return demonstration, documents the result, and reassesses on a schedule and after incidents or new equipment.
Traps
- Applying a technical fix to what is actually a communication problem.
- Reporting training completion rates as if they demonstrated competence.
- Announcing a change without engaging the people who must carry it out.
- Delegating a task without matching authority and accountability.
- Overloading a message with technical detail when leadership needs risk and cost.
Rule of thumb
For any new device rollout: identify stakeholders, define a competency checklist, train super-users first, go live with floor support, and audit actual use at 30, 60, and 90 days. Document the competency verification, not just the class roster.