Some of what I’ve learned about leading healthcare IT teams didn’t come from a conference room or a project plan. It came from racing sailboats.
Sailboat racing is different from an afternoon harbor cruise. Once you are on the racecourse, decisions come faster, communication gets sharper and mistakes become harder to hide. No matter how experienced one person may be, the boat moves well and is competitive only when the crew works as one.
But here’s what I’ve also realized: The skipper’s job isn’t to do the crew’s work. It’s to set a clear direction, make timely decisions, assimilate the information coming in, and create the conditions for the crew to perform. Healthcare IT executives have a similar responsibility.
On a racing sailboat, everyone has a role. Someone is at the helm, steering. Someone is trimming the main. Someone manages the jib. Somebody is watching the wind or preparing for the next tactical maneuver.
But nobody really cares who did their individual job best if the boat isn't going fast.
I’ve seen the same dynamic on healthcare IT initiatives. IT has its responsibilities. So do clinical teams, revenue cycle, finance, operations, training, the software vendor and consulting partners. Each group brings distinct expertise, but the work succeeds only when those contributions come together around organizational readiness, clinical workflows and the needs of the people who will use the technology.
Problems start when teams become too focused on their own piece.
"My build is done."
"Testing completed our work."
"Training delivered the classes."
All important. But a hospital doesn't go live as a collection of completed workstreams. The organization goes live.
For a CIO or executive sponsor, this is one of the most important things to watch for. When status updates sound like individual accomplishments rather than a picture of organizational readiness, that's a signal.
The better question for every steering committee is not simply, “Is your workstream on track?” It is, “What evidence tells us we are ready to go live together?” That shift moves the conversation from activity to organizational readiness.
Imagine being halfway through a race. The wind shifts, the tactician calls for a tack, the helm starts turning the boat, and somebody says:
"Nobody told me that was part of my scope."
It sounds ridiculous.
Yet anyone who has spent enough time on a large technology implementation has probably heard some version of it.
Good racing crews don’t operate that way. Sometimes you’re doing your assigned job. Other times, you’re helping someone else because that’s what the boat needs. On a healthcare IT initiative, the same instinct matters, but it works best when responsibilities remain clear, emerging needs are surfaced quickly and leaders decide how the team should respond.
That instinct doesn’t appear on its own. Leaders build it by making shared outcomes visible, clarifying how decisions will be made and showing that raising a cross-functional risk is part of the job, not a failure to stay in one’s lane.
If leadership rewards people only for completing their own deliverables, that's what they'll focus on. If leadership rewards people for helping the project succeed, even when it means stepping outside their lane, you get a different kind of team.
CIOs set that tone. Not by giving a speech about teamwork, but by how they respond when someone raises a cross-functional issue.
You can leave the dock with a race strategy that makes perfect sense. Then the wind changes. Something gets tangled. A piece of equipment doesn't cooperate.
Ten minutes later, your perfect plan isn't very perfect anymore.
You adjust and keep racing.
Healthcare IT initiatives face the same kind of change. The destination may remain clear, but the route rarely stays exactly as planned.
Resources change. Testing exposes something nobody expected. Interfaces don't behave as planned. A workflow that looked great in a conference room doesn't work nearly as well in front of the people who have to use it.
What matters is how quickly the team recognizes it and whether people are comfortable talking about it.
One of the most dangerous phrases on a project is:
"I knew that was going to be a problem."
Especially when you hear it after the problem has already happened.
When someone says later, “I knew that was going to be a problem,” it usually means the risk was visible before the team had a reliable way to surface and address it.
This is where executive leadership has real leverage. A CIO who asks, “What are you worried about?” and listens carefully creates a different project dynamic from one who asks only, “Are we on schedule?” Both questions matter, but the first can reveal the information the schedule has not captured yet.
The person holding the wheel looks like they're running the boat. But anyone who has raced knows the person at the helm doesn't see everything.
Sometimes someone sitting on the rail, where crew members help balance the boat, sees a wind shift developing on the other side of the course before the person at the helm does.
A good skipper listens.
The same should be true on a healthcare IT initiative. Analysts, trainers, clinicians, consultants, project managers and frontline staff often see operational risks first because they are closest to the workflows, technology and people affected by the change.
They're often the first to recognize that something isn't quite right.
But permission to speak up isn’t enough. There has to be a mechanism: structured rounding with project teams, open office hours with the chief medical information officer and regular readiness check-ins that ask what could prevent teams, clinicians or operations from succeeding.
The executives who do this well aren't just approachable. They're building an early warning system.
When you cross the finish line after a good race, nobody says, "I won." It's almost always: "We had a great race."
Successful healthcare IT initiatives should feel the same way. They should not be remembered as IT’s implementation, the vendor’s project or the consultant’s success. The accomplishment should belong to the organization and to the people who made the change work.
How leaders talk about the initiative, who they recognize and whose contributions they make visible all shape whether people feel ownership of the change or feel that it simply happened to them.
The best crews aren't the ones with the fewest problems. They're the ones that see problems early, talk about them openly, adjust quickly, and keep moving toward the same destination.
Crews don’t build those habits on their own. They develop them because the skipper creates the conditions for clear communication, shared responsibility and quick adjustment. The best project teams I’ve worked with had executive sponsors who stayed engaged, asked hard questions and made it safe to raise concerns. They also kept the organization focused on crossing the finish line together.
For executive sponsors, the lesson is practical: keep the destination clear, make readiness a shared measure, create reliable ways for risks to surface and stay engaged when conditions change. Those habits do more than keep a project moving. They help the organization carry the change into daily operations.
That’s the kind of leadership that wins races and helps healthcare organizations navigate complex technology change with greater confidence.