Stop Blaming Technology for Your Digital Bottlenecks

Healthcare marketing teams spend a lot of time debating technology. 

Should we switch platforms? Is the website holding us back? Do we need a better CRM? Those debates feel productive because technology is visible. It is concrete. It can be funded as a project. It promises a big, clean step forward. 

Governance does not give leaders the same clean story. It is slower, harder to see, and much less exciting to fund. Yet that is where a huge share of digital friction actually lives: ownership, prioritization, intake, and decisions that keep circling without landing.

The website and the rest of the digital stack are visible and end up carrying the blame because everyone can see them. The harder problem sits with conflicting priorities, repeated decisions, random requests, and work that somehow gets harder the more people touch it. Technology matters. It just does not rescue a team from bad governance

Therese Lockemy has seen this pattern from both sides, first inside major academic medical centers, then across health systems through Inner Path Digital. In my recent conversation with her (see YouTube & Spotify for full discussion), we got into why this keeps happening and what teams can do differently.

The real problem starts upstream

A lack of governance rarely introduces itself by name. It shows up as rework, stalled approvals, conflicting feedback, and teams burning time without making progress. A timeline slips. Feedback starts colliding. A priority that sounded clear in a leadership meeting turns muddy once real work begins. The team is busy, but the work does not move. Everyone feels the friction. Few people name the source correctly.

“Governance fails earlier than people think.” 
- Therese Lockemy

By the time a healthcare digital initiative looks stalled, the real breakdown has usually been in motion for weeks or months. The goals were broad enough to sound aligned, but not specific enough to guide decisions. Ownership was discussed, but not defined tightly enough to hold when trade-offs appeared. Too many stakeholders were invited to weigh in, and too few were given real accountability.

Healthcare makes this worse because the work is rarely confined to one team. Marketing may be driving the initiative, but IT owns part of the stack. Operations has a view on workflows. Access cares about conversion and scheduling. Clinical leaders have their own priorities. Service lines want visibility. Everyone has a reason to be involved. Without a clear model for who decides what, the project turns into an ongoing negotiation that never really ends.

That is why weak governance is so easy to miss. It does not arrive as a dramatic failure. It arrives as drift. Priorities get reinterpreted. Decisions get revisited. New requests slip in sideways. Teams spend more time reconnecting the dots than moving the work forward. By the time people start blaming the website or the platform, the project has already been slowed by something more fundamental: no shared discipline around how the work gets led.

A platform decision is not a strategy

This is where healthcare teams lose the plot. The platform decision starts absorbing strategic weight it was never built to carry. Can this system handle our needs? Should we switch? Are we on the wrong stack? Those are fair questions. They are not a strategy.

“The platform can’t solve the cross-functional problem.”
- Therese Lockemy 

A platform can support a strategy, enable a workflow, or remove technical constraints. It cannot tell marketing and IT how to share ownership. It cannot resolve which requests matter and which ones should die in intake. It cannot settle competing priorities across service lines, operations, access, and digital. It won’t create alignment where none exists.

That matters even more in healthcare because the patient experience doesn’t live in one system. The website connects to scheduling, CRM, analytics, forms, access workflows, and often a long tail of internal tools and approvals. So when teams treat the platform choice like the strategic decision, they end up expecting technology to compensate for weak governance. It never does. It just gives the organization a more expensive place to replay the same confusion.

The work gets better when the operating model gets clearer

This is the part teams tend to wave off as process. More structure. More meetings. More overhead. On paper, it looks like the boring work.

A clearer operating model is not as exciting as a new website launch or a platform migration. It does not give leadership the same big moment. You cannot point to it as easily. That is part of the problem. Teams keep underestimating the value of the work that actually makes execution easier.

Therese made a useful point on this. The structure is not creating the burden. It’s actually exposing where the burden already is. Without it, teams still spend the time. They just spend it in side conversations, repeated approvals, unclear handoffs, and meetings that exist because nobody is fully sure what was decided the first time.

What helps is not glamorous. It is a clearer way of working. That can mean:

• a better intake process, so every random request does not immediately compete with strategic work
• clearer briefs, so teams are not interpreting the same priority three different ways
• clearer roles, so people know who is deciding, who is contributing, and who just needs visibility
• better meeting design, so leaders stay informed without getting dragged into every working session

None of that feels dramatic in the moment. But it compounds. And over time, the organization gets something healthcare teams are usually short on: real capacity to move.

Before you blame the platform

Before blaming the platform, fix the parts of the work that create the most drag.

Start with three things.

1. First, get clearer on ownership. If nobody can say who actually decides, the work will keep circling. A simple responsibility matrix can help, but the point is clarity, not the template.
2. Second, clean up intake. Too many healthcare teams let random requests compete with strategic work as if they deserve equal weight. They do not.
3. Third, force sharper prioritization across functions. Marketing, IT, operations, and access do not need perfect alignment on everything. They do need a shared view of what matters now, what can wait, and what should die.

None of this is flashy. It will not give you the same excitement as a launch or migration. It will give you traction. That is the leverage teams keep looking for in the tool, when it actually sits in how the work runs. 

If this kind of friction is showing up in your website operations, it may be worth stepping back to look at the governance around the work, not just the technology underneath it. That is a conversation we often help healthcare teams work through.