Why Healthcare Marketing Work Gets Stuck, No Matter Your Team Size

When 'Being Responsive' Becomes Reactive

Smaller teams do move faster. Few people means fewer approval layers. A request can go from idea to execution in a single conversation. The advantage is real.

That same speed creates a vulnerability.

“On this other side of the scale, some of the smaller organizations, because you only have maybe a few people that are doing the work, you don't think about putting in those process steps. But that kind of creates its own sort of chaos too, because then everything just comes in as the top priority.”
- Alan Shoebridge

That line gets at something a lot of healthcare marketing and communications teams know firsthand. When work comes in through hallway conversations, email chains, Slack messages, and leadership drive-bys, speed starts to look more impressive than it really is. The team feels responsive because it is constantly reacting.

The problem is that reaction is not the same as prioritization: if everything is urgent, nothing has really been prioritized.

That pattern shows up all the time in healthcare website work. A department wants a page changed. A leader wants a homepage slot. A service line pushes for a campaign landing page. Compliance jumps in late. Nobody defined the request properly at the start, so the team burns hours cleaning up ambiguity that should never have been allowed in the front door.

Small teams do not need enterprise-grade bureaucracy. They do need enough structure to stop every request from arriving as a fire drill.

A simple intake form. A weekly prioritization review. Basic rules for what needs a brief before work starts. None of that is glamorous. All of it protects the team from becoming a reactive ticket desk.

That is the lesson smaller teams should borrow from larger ones. Not more ceremony. Just enough structure to keep speed from turning sloppy.

When Large Healthcare Marketing Teams Turn Rigor into Drag

Large teams build process for good reasons. Budget stewardship. Compliance review. Brand consistency. Vendor management. Cross-functional alignment. These aren't fake concerns. Process starts with a legitimate need.

But process has a way of lingering long after the original reason has faded.

In healthcare, process often starts with a legitimate reason. Budget stewardship. Compliance review. Brand consistency. Vendor management. Cross-functional alignment. Those are not fake concerns. But process has a way of lingering long after the original reason has faded. Steps get added. Exceptions disappear. Old review loops stay in place because nobody wants to be the one who removes them.

That is how rigor turns into drag.

“You have to put process in place to prioritize resources. That means, you probably need a request form. You probably need a review process.”
- Alan Shoebridge

The problem is not process itself. The problem is what happens when every kind of work gets pushed through the same machinery.

You see it when a modest website update gets routed through the same workflow as a strategic initiative. You see it when teams spend more time coordinating approvals than improving the work. You see it when everyone agrees the workflow is slow, but no one owns simplifying it.

That is the tension: Some process is necessary, but too much process becomes its own form of dysfunction.

Large teams do not need to behave like five-person shops. That is not realistic. But they should ask harder questions than they usually do. 

• What truly needs executive review?
• Which steps are still protecting the work, and which ones are just inherited habit?
• Where can smaller updates move on a faster track without compromising safety or quality?

That is what large teams should borrow from smaller ones: less procedural comfort, more willingness to trim the fat.

A tool without ownership is just another bill

This is where both small and large teams make the same mistake.

A business case gets made for a new platform, such as a new CRM or analytics suite. The contract gets signed. Then the organization acts surprised when adoption stalls.

“There’s this shiny new object, this new SaaS, this whatever that’s going to optimize your campaign. The teams scratch the surface, use part of it for a couple of weeks, and then forget about it.”
- Brad Muncs

A tool does not become a capability because you bought it. It becomes a capability when someone owns the workflow around it. That means setup, adoption, training, governance, ongoing use, and the annoying middle part where people change habits.

Smaller teams are vulnerable because they often buy capability without buying capacity. Larger teams are vulnerable because ownership gets diffused across the org chart. Different failure mode. Same waste.

Before adopting anything new, four questions should be answered clearly:

• Who owns it?
• How much time does that ownership require?
• What workflow is it improving?
• How will success be measured?

Look across the aisle

One of the most useful things healthcare marketers can do is study teams with different constraints than their own.

If you work in a smaller organization, look at how larger systems handle intake, prioritization, and ownership. Not to copy the bureaucracy. To borrow the discipline.

If you work in a larger system, look at how smaller teams protect speed, simplify decisions, and avoid turning every request into a process exercise.

That kind of cross-pollination is practical. It helps teams see where they have mistaken habit for necessity. The goal is not to operate like a bigger team or a smaller one. It is to build a model that fits your reality and drops the failure modes that come with it.