Leadership, Communication, and Project Management
What this domain tests
This domain tests the non-technical work that determines whether good engineering is adopted: scoping projects, managing budgets and schedules, engaging clinical stakeholders, communicating risk, and leading change. Expect questions on project charters, work breakdown structures, RACI matrices, risk registers, earned value, and change management.
Core rules
- Charter first: define objective, scope, sponsor, success criteria, constraints, and exclusions before scheduling work.
- Plan the triple constraint: scope, schedule, and budget are linked; a change to one requires an approved change control.
- RACI: clarify who is Responsible, Accountable, Consulted, and Informed; only one person is accountable per deliverable.
- Risk register: log probability, impact, owner, response, and trigger; review it at each status meeting.
- Communication plan: identify audiences, message cadence, channels, and escalation paths. Clinicians need workflow impact, not a component list.
- Change management: engage early adopters, map workflow, provide training at go-live, and measure adoption.
Worked example
A hospital replaces 200 infusion pumps across 12 units. Reasoning: write a charter with a clinical sponsor; build a WBS covering procurement, wireless validation, drug-library build, training, and go-live; use a RACI to separate nursing, pharmacy, IT, and biomed duties; schedule a phased rollout by unit with a rollback plan; track earned value to catch slippage; hold daily huddles during go-live. Success is measured by pump availability and user-reported workflow, not just delivery date.
Traps that cost marks
- Treating a device rollout as a procurement task rather than a clinical change project.
- Having multiple accountable owners for one deliverable.
- Communicating only by email to frontline staff.
- Ignoring scope creep until the budget is gone.
- Measuring success only by on-time delivery.