Your Healthcare Org Isn't Ready For Another Tech Initiative

Healthcare organizations don’t have a shortage of ideas.

AI, cloud migration, interoperability, infrastructure modernization, cybersecurity, new analytics capabilities, operational improvements—the list of opportunities continues to grow.

The challenge is that the list is usually longer than the organization’s capacity to execute it.

After more than 30 years in healthcare technology, I’ve noticed something that shows up repeatedly across organizations of different sizes and levels of maturity. I’ve seen this play out across organizations of different sizes and levels of maturity. Leaders often spend significant time evaluating the technology itself: What can it do? What will it cost? How quickly can we implement it? What value will it create?

But there is another question that deserves just as much attention:

Is the organization actually ready to absorb the change?

In many cases, the technology itself works exactly as intended, but what ends up slowing things down is everything surrounding it.

When Ambition Outpaces Capacity

Healthcare leaders are being asked to modernize technology, modernize technology, reduce costs, strengthen security, enable new capabilities, and support patient care—all at the same time.

That’s a difficult balancing act.

When a promising opportunity emerges, it’s natural to focus on the potential benefits. Improved resilience and business continuity, reducing administrative burden, and interoperability capabilities are all valuable outcomes. But when it’s time to ask the question of capacity, confidence tends to waver.

Many healthcare teams are already operating at or near capacity. They’re keeping critical systems available, supporting clinicians, managing upgrades, responding to security threats, maintaining infrastructure, addressing regulatory requirements, and supporting day-to-day operations.

A new initiative doesn’t make any of those responsibilities disappear. I’ve seen organizations announce well-intentioned programs only to discover six months later that the same people needed to support the new work are already stretched thin supporting existing commitments.

The strategy wasn’t wrong, but asking organizations to absorb more change than it could reasonable support is a reasonable frustration.

Executive Alignment Doesn’t Equal Organizational Readiness

It’s common for a leadership team to be ready to move long before the rest of the organization is.

I’ve worked with CIOs and executive teams that had a clear vision, strong sponsorship, and a thoughtful roadmap. They understood where they wanted to go and why it mattered.

What they didn’t take into account were their resource constraints. This could look like infrastructure teams needing new skills. Or clinical leaders focusing on immediate patient-care demands. Or managers trying to balance competing priorities.

One of the biggest mistakes organizations can make is assuming that agreement equals readiness. People may support the strategy and still lack the capacity to execute it. They can believe in the long-term direction and still need training, additional resources, clearer governance, or simply more time.

Why Good Technology Can Still Struggle

I’ve seen organizations begin exploring AI before establishing the governance needed to manage it. I’ve seen major initiatives launch while teams were still absorbing the last major transformation. And I’ve seen projects move forward before stakeholders had fully agreed on the problem they were trying to solve.

People need to be aligned, stakeholders need to be involved, and organizations need a clear plan for how the work will get done.

If not, organizations often find themselves revisiting decisions, adjusting priorities, or slowing initiatives that initially appeared straightforward.

Aside from connecting systems, implementing tools, or enabling new capabilities, much of the work also consists of helping people understand the value of change and how it can affect their day-to-day responsibilities.

Workforce Readiness Deserves More Attention

One area I believe healthcare leaders should pay particular attention to is workforce readiness.

Healthcare technology is changing quickly. Cloud capabilities continue to expand. Interoperability requirements continue to evolve. AI is creating new opportunities across healthcare operations. Cybersecurity expectations continue to increase.

That creates pressure on teams that may have spent years—or decades—developing expertise in a different environment.

I have a great deal of empathy for that situation. When someone has spent 20 years supporting a particular technology stack, introducing new platforms, tools, and expectations can create understandable uncertainty.

That shouldn’t automatically be interpreted as resistance to change. Often, people need support—training, coaching, clear expectations, opportunities to develop new skills, and enough time to build confidence.

Organizations that recognize that reality are better positioned to bring their workforce along with the transformation rather than expecting people to simply adjust to it.

CHECK OUT: Turning Patient-Generated Health Data Into Actionable Insights

Before Adding Another Initiative

Before committing to another major technology effort, leaders should take time to understand what they’re asking the organization to absorb.

That means looking beyond the technology itself and assessing:

Current team capacity and existing project commitments
Skills and capabilities that may need to be developed
Stakeholders who need to participate
Governance and decision-making requirements
Operational and clinical impacts
Workforce concerns and change readiness
Dependencies across other initiatives
Potential sources of change fatigue

These conversations may not generate the same excitement as discussing the newest technology, but they often determine whether a roadmap can actually be executed.

While some organizations are ready to move quickly, others may need to build skills, strengthen governance, align stakeholders, augment internal teams, or create additional capacity before moving forward.

As a result, the roadmap should reflect the reality of the organization expected to deliver it.

So before adding another AI program, cloud initiative, interoperability project, cybersecurity effort, or technology investment to the roadmap, ask a few questions:

Do people have the capacity?
Do we have the right capabilities
Are the right stakeholders involved?
Do teams understand why the change is happening?
Have you created space for the work that comes with it?

After more than three decades working in healthcare technology, I’ve found that these conversations can be just as important as the technology conversation itself. Because making sure your organization is ready for the technology is just as important as the technology being ready for your organization.

If you’re ready evaluate your organizations readiness, I’m happy to connect.