We get asked to fix a lot of "project management problems" that turn out to be program management problems in disguise. The distinction sounds academic until you're three months into a multi-system rollout and nobody can explain why the EHR upgrade team and the pharmacy inventory team keep stepping on each other's timeline.
A project has an end. A program has an outcome.
A project manager is accountable for delivering a defined piece of work: migrate this system, roll out this device fleet, complete this integration. A program manager is accountable for something bigger and less concrete — the business outcome that several of those projects are supposed to add up to, like "reduce medication errors across all three facilities" or "cut new-patient onboarding time in half." Put a project manager in charge of that outcome and you'll get excellent execution on the wrong things, because nobody is asking whether the individual projects still make sense together as priorities shift.
Where this breaks down in healthcare specifically
Healthcare IT initiatives rarely stay contained to one system. An EHR upgrade touches scheduling, billing, pharmacy, and clinical documentation, often run by different vendors on different timelines. Each of those is a legitimate project with its own project manager. But someone has to own the sequencing between them — because if pharmacy's system goes live two weeks before the EHR integration it depends on, you don't have a delay, you have a patient safety incident. That sequencing and cross-project accountability is program management. It's a different skill set from running a single workstream, and it requires the authority to say no to a project timeline that looks fine in isolation but breaks the larger plan.
The tell that you need a program manager, not another project manager
If any of that sounds familiar, adding another project manager to the mix usually makes it worse, not better — one more voice with partial visibility and no authority over the whole. What the situation needs is someone accountable for the outcome across all of it, with the standing to make the sequencing calls project managers shouldn't have to make alone.
- Multiple project teams report different status colors on the same underlying initiative
- Decisions get re-litigated in every steering committee because no one owns the tradeoff
- Vendors are managing their piece well, but the pieces don't fit together at handoff
- Leadership can't get a single, honest answer to "are we on track"
That's the seat we're usually brought in to fill. If you're seeing these symptoms in an active initiative, let's talk about what's actually happening underneath them.