Why IT Ends Up Holding the Bag

When failures surface, think performance issues, outages, or breaches, healthcare IT is expected to fix problems it didn’t create. In many cases, the cost to remediate far exceeds the original implementation investment.

Consider a regional health system that quickly acquired several outpatient clinics. The transactions moved quickly, but infrastructure standards, network capacity, and identity management were never planned for. Within months, clinicians faced system slowdowns and access problems that disrupted patient flow. IT was held responsible for the instability even though the root cause was the absence of technical governance during the acquisition process. Once IT was brought into future acquisition planning earlier, performance at new clinics improved beyond expectations.

Organizations that avoid this pattern treat IT as a strategic partner, not a cost center, involve technology leadership in enterprise planning, and tie IT performance directly to business and clinical outcomes.

What CIOs Can Do to Counter This Dynamic

From both working in the hospital system to now being on the outside, here are three moves that change the equation.

1. Alignment Across Multiple Teams and Stakeholders

First, align technology initiatives explicitly to health system priorities — patient access, clinician efficiency, financial performance, and risk mitigation. When IT speaks the language of the business, it becomes harder to treat as a back-office function.

2. Translation From Tech Jargon to Real Business Impact (and Risk)

Second, translate technical metrics into business impact. Infrastructure reliability, cybersecurity posture, and system performance directly affect patient trust, brand reputation, and revenue. Patients notice when registration takes 45 minutes or when a breach makes the news, and they choose care elsewhere.

3. Set Expectations Around Roles and Ownership

Third, build shared ownership of outcomes. In effective models, IT and clinical or operational leaders jointly own results. IT manages infrastructure while service lines manage application performance. Accountability is distributed across the organization rather than concentrated inside IT.

The Biggest Mistake Healthcare IT Leaders Make When Defending Themselves

The most common misstep is accepting full responsibility for failures without surfacing the broader governance, vendor, and decision-making context. When IT frames issues as purely technical problems to be fixed, it unintentionally absorbs accountability that belongs to fragmented ownership and misaligned incentives across the enterprise.

When IT Does Share Responsibility: Lead with Facts, Not Defensiveness

The most effective response is discipline, not defensiveness. Lead with a fact-based assessment of what happened, why it happened, and which controls or decision points failed or were missing. That approach reinforces IT’s role as a trusted, accountable partner — one focused on continuous improvement, organizational resilience, and long-term performance.

Breaking the Cycle Starts With a Seat at the Table

IT doesn’t take the fall because it fails more than other departments. It takes the fall because it’s often the last one invited to the planning conversation. The CIOs who break this cycle aren’t just better communicators — they’re embedded in strategy before the decisions are made.