Why Project Management Matters Even in Healthcare Businesses

The short version: Healthcare businesses run on clinical excellence, but clinical excellence has never once stopped a system rollout, a new location or a staffing change from going wrong. Project management matters here for the same reason it matters anywhere else: someone needs to own the plan, the timeline and the budget so good clinical work isn't undone by bad admin. I've watched a well-run clinic lose tens of thousands of pounds because nobody was in charge of a project that everyone assumed was "just a website update."

The physiotherapy clinic that taught me this the hard way

A few years ago I worked with a group of four private physiotherapy clinics in the Midlands. Excellent clinicians, loyal patient base, decent word of mouth. They wanted a new booking system tied to a redesigned website, partly because their existing one didn't sync with their calendars and partly because two of the four sites were double-booking patients most weeks.

They budgeted six weeks and about £8,000 for the whole thing. It took eleven months and cost closer to £40,000 once you added the lost bookings, the temp receptionist hours to manually manage the mess, and the developer's overtime.

Nothing about that was down to bad clinicians. It was down to nobody owning the project. The practice manager was meant to be running it alongside her actual job of running four clinics. The developer built what he thought they wanted. The clinic owners assumed the practice manager was checking his work. She assumed they'd tell her if something looked wrong. Three months in, nobody had tested the new system with an actual patient booking a real appointment. When they finally did, it double-booked the same slot at two different sites on the same afternoon.

That's not a technology problem. That's a project management problem, and it's the exact same problem I see in software companies, agencies and manufacturing businesses. Healthcare doesn't get a pass on it just because the people doing the clinical work are highly trained.

The uncomfortable bit healthcare owners don't want to hear

Here's the part that clinic owners, GPs, dentists and care home operators tend to resist: being brilliant at treating patients doesn't transfer into being brilliant at running change. It's a completely different skill, and the fact that someone spent seven years training as a physiotherapist or a decade as a consultant doesn't make them any better at scheduling a system migration than someone who's never touched a patient chart.

I think a lot of healthcare businesses quietly believe their clinical rigour will carry over into their operations. It doesn't. Clinical protocols are about following a known, tested process on one patient at a time. Project management is about coordinating multiple moving parts, several people, a budget and a deadline, all of which move and change while you're mid-way through. Those are different muscles, and most healthcare businesses never build the second one because they've never had to. Then they launch a new EHR system, open a second site, or bring in a new billing platform, and the wheels come off in exactly the way my physiotherapy client's did.

What "a project" looks like inside a healthcare business

When people hear "project management" they picture construction sites or software teams with sprint boards. In a clinic, practice or care home, a project is anything with a start, an end, a budget and more than one person involved. That covers far more than most owners realise:

• Switching patient record or booking systems
• Opening a second location or expanding an existing one
• Bringing on a new insurance panel or billing provider
• Rolling out new equipment that needs staff training
• Rebranding or redesigning the website and patient portal
• Recruiting and onboarding a wave of new clinical staff at once
• Passing a CQC or equivalent inspection with corrective actions attached

Every one of those has a real deadline, a real budget, and real consequences if it slips. None of them are clinical work. All of them get treated as an afterthought squeezed in around clinical work, which is precisely how my physiotherapy client's rollout turned into an eleven month mess.

The number that should worry you

The Project Management Institute has tracked, year after year in its Pulse of the Profession research, that organisations across industries waste well over $100 million for every $1 billion they spend, purely down to poor project performance: scope creep, missed deadlines, and work that has to be redone. Healthcare businesses rarely spend a billion pounds on anything, but the ratio holds at small scale too. My physiotherapy client's £8,000 project became a £40,000 one. That's a five-fold overspend, and it's a completely ordinary outcome for an unmanaged project, not a rare disaster.

Five steps that would have saved that clinic £30,000

None of this requires hiring a full project management department. It requires someone taking on the role deliberately, even part time, and following a structure. Here's what I'd have put in place from day one of that booking system project:

• Name one owner. Not "the practice manager will keep an eye on it," one named person whose job that week includes checking progress against the plan, full stop.
• Write down the scope before anyone builds anything. What exactly does the system need to do, in a list specific enough that you could tick items off. "Sync calendars across four sites" is a scope item. "Better booking system" is not.
• Set a realistic timeline with checkpoints, not just an end date. Week two: staff can log in. Week four: test bookings work at one site. Week six: all four sites live. If a checkpoint slips, you find out in week two, not week ten.
• Test with real staff doing real tasks before go-live. A receptionist booking an actual patient appointment, not a developer clicking through a demo.
• Hold a short weekly check-in, fifteen minutes, same time, same people. That single habit would have caught the double-booking bug in week three instead of month five.

That's it. No software required beyond a shared spreadsheet or a free Trello board. The discipline is the whole point, not the tool.

Do you need to hire a project manager, or can someone learn it on the job

For most small healthcare businesses, hiring a dedicated project manager isn't realistic and honestly isn't necessary. A practice manager, a senior nurse, or an ops lead can pick up enough structure to run most internal projects competently, and it's one of the more accessible career pivots around: my piece on getting into project management with no formal experience covers exactly the route someone in a clinical or admin role tends to take, and it's usually faster than people expect.

Where it changes is scale. A single clinic opening a second site or switching one system is manageable in-house. A hospital group rolling out a new patient record system across eight locations, or a care home chain merging two providers' systems after an acquisition, is a different order of complexity. That's where bringing in someone with real project management background, even on contract for the duration of the project, pays for itself. If you're weighing that cost against the risk of another £40,000 mess, it's worth understanding what that role costs; the numbers in my breakdown of IT project management salary and whether it's worth pursuing give a fair sense of the market rate for someone who specialises in exactly this kind of systems rollout.

There's also a quieter option a lot of healthcare businesses miss: someone already on your team, often in an admin or ops role, who's naturally the one keeping lists, chasing follow-ups and noticing when things slip. That person is closer to a project manager than they realise. Looking at what a genuine project management career path from coordinator upward looks like can help you see whether that person could grow into the role formally, rather than you hiring in from outside every time something needs coordinating.

Choosing how you'll run the project

You don't need to import full corporate methodology into a GP practice, but picking some structure beats picking none. A rigid, plan-everything-upfront approach suits a system migration with a hard compliance deadline. A more iterative, adjust-as-you-go approach suits something like a website redesign where patient feedback should shape the next round of changes. If you want the plain-English version of the difference rather than a training course's worth of jargon, my guide to the main project management methodologies explained simply lays out which approach fits which type of project, and healthcare businesses tend to need both at different times, not one for everything.

One thing worth flagging for anyone running a bigger healthcare operation with a real IT function: if you've got developers, systems administrators or a digital team involved, the line between "project management" and "IT management" gets blurry fast, and it's worth knowing where the boundaries sit. My piece on whether project management falls under computer information systems is useful reading if you're trying to work out whether your next hire should come from a clinical operations background or a technical one.

What changes when you do this

Six months after the physiotherapy group's disastrous rollout, they brought in someone part time, two days a week, whose only job was running their next project: opening a fifth site. Same clinicians, same owners, same budget pressure. That project came in on time and roughly 8% over the original budget instead of five times over it. The difference wasn't talent. It was that one person owned the plan and checked it every week.

That's the whole argument for project management in healthcare businesses. It's not glamorous, it doesn't touch a single patient directly, and clinicians in the room often can't see the point of it until the project without it has already gone wrong once. But the businesses that build this muscle stop repeating the same expensive mistakes every time they try to grow, change a system, or open a new door.

Frequently asked questions

Do small clinics really need formal project management?

Not formal certification, no, but they need someone who owns the plan, the budget and the timeline for anything bigger than day to day clinical work, such as a system change or a new location. Without that, small changes routinely turn into expensive, drawn out messes, as they did in the physiotherapy clinic example above where a six week project stretched to eleven months.

What's the difference between operations management and project management in healthcare?

Operations management keeps the existing clinic running day to day, patients booked, staff rostered, supplies stocked. Project management handles anything with a defined start and end, like a system migration or a new site opening. Healthcare businesses are usually strong on the first and weak on the second because it happens far less often.

How much does it cost to bring in a project manager for a healthcare rollout?

Rates vary widely by scope and region, but a contract project manager handling a mid-sized systems rollout in the UK typically costs somewhere in the range of £350 to £600 a day, and far less if you upskill someone already on your team rather than hiring externally. Weigh that against the cost of an unmanaged project going wrong, which in real terms is often five times the original budget.

Can a practice manager or senior nurse become a project manager without leaving healthcare?

Yes, and it's one of the more natural transitions into project management because that person already understands the operational chaos of a healthcare business from the inside, which outside hires usually don't. It typically starts by running one small internal project, start to finish, then building from there.