7 reasons IT always gets the blame — and how IT leaders can change that

When business benchmarks fall short of expectation, it’s time to find a reason. Unfortunately, the fingers often point to IT, which isn’t surprising given the essential role the department plays in so many key business areas. Yet, as IT leaders well know, their department actually helps the enterprise become more productive and efficient.

What should you do if your department has become an easy target for failures that can’t rightfully be attributed to IT operations or services? Here are seven strategies for turning around that organizational perception.

1. Poor communication — and ‘outsider’ status

Many IT professionals have trouble using effective communication skills, says Abbe Depretis, an associate teaching professor of business communication at Carnegie Mellon University’s Tepper School of Business. She observes that while most IT leaders are smart, and know much more about technology than other C-level execs, most don’t take the time needed to explain that information in ways a non-expert can understand.

It becomes easy for enterprise leaders to blame IT for just about anything, given that they often have trouble understanding what IT is doing anyway, Depretis says. “So the department serves as a red herring to distract from the real culprit,” she adds.

Additionally, because IT teams are frequently siloed away from other departments, they’re often viewed as being distant and not part of the team. “It becomes a lot easier to blame an outsider for a crisis than it is to blame one of your own,” she says.

Sharpening communication and creating better alignment with the business can go a long way toward altering these ingrained attitudes toward IT.

2. Mismatching goals

Blame often stems from a mismatch between a technology’s promise and its implementation reality, says Justice Erolin, CTO at software development and staff augmentation company BairesDev.

Erolin notes that C-level leaders often view IT through the lens of ROI and efficiency, whereas tech leaders understand that IT isn’t a magic button that can cut costs overnight.

“When projects fail to move the needle for a client, or solve a real business problem, trust erodes,” Erolin warns.

Furthermore, non-technical leaders often treat promising initiatives as “just a tech experiment,” he says, rather than integrating them into a long-term business strategy. This leads to a state of “pilot purgatory,” he adds, in which projects stall, creating frustration that gets directed at IT.

Here, getting on the same page with business leaders regarding the strategic value of IT can help.

3. Underinvestment in IT and change management

People know that technology is a powerful tool — so powerful that they often begin to treat it like magic, says Matt Beran, industry analyst at IT management platform provider InvGate. As a result, C-level leaders often have a deeply rooted hope that technology will somehow save them.

“Yet technology doesn’t save anyone or anything by default,” Beran warns. “It saves you when you’ve done the hard, unglamorous work of implementing technology properly and preparing your people how to use it effectively.”

Too often, enterprises underinvest in their technology capabilities during the good times and then act shocked when those weak capabilities can’t bail them out during bad spells, Beran says. “IT then becomes the scapegoat, since it’s easier to point at a department and say, ‘Why didn’t this work?’ than it is to ask, ‘Why didn’t we invest in making this work when we had the chance?’ The blame isn’t really about IT failing; it’s about the organization failing to treat technology as the strategic investment it needs to be.”

4. Misplaced blame on visible symptoms rather than root causes

C-level leaders tend to blame IT during a crisis, especially when a failure surfaces through a technology symptom, even when the root cause is broader, says Oscar Moncada, CEO at cloud migration and infrastructure management company Stratus10.

“An outage, breach, or performance issue becomes the visible trigger, so attention naturally turns to IT,” he states. “This is often compounded by colleagues’ limited understanding of complex environments and how many tradeoffs IT teams manage daily.”

The mistake many CIOs make is focusing on the fault instead of the underlying process, Moncada says. “A post-mortem culture asks why something happened, how it was missed, and how it can be prevented or mitigated the next time — without turning the issue into a blame game,” he explains.

CIOs can counter these claims by consistently communicating the real state of enterprise infrastructure and security. “This means clearly surfacing risks, constraints, deferred work, and future needs, and then pairing those realities with concrete solutions,” he says.

It’s important to make tradeoffs visible ahead of time, Moncada says. “When leaders understand what isn’t getting done and why, they’re far less surprised when issues arise,” he explains.

5. Vague ownership boundaries

Many C-level leaders fault IT for various shortcomings due to the fact that technology now touches virtually every business asset, making ownership boundaries unclear, says Bhumika Shah, an AI researcher at the University of the Cumberlands.

“When revenue, customer experience, or compliance suffers, the most visible failure is usually a system, application, or data flow,” she notes. “Therefore, in many organizations, IT is still perceived as a support function rather than a business partner, making it the default place to point to when outcomes go wrong.”

The biggest mistake IT leaders make is becoming defensive or overly technical, Shah says. “When CIOs respond with system diagrams, uptime statistics, or vendor explanations, they unintentionally reinforce the perception that IT is disconnected from business outcomes,” she explains.

6. IT has become an organizational scapegoat

Xi He, CEO of software development firm BoostVision, agrees that IT often gets blamed because it affects almost every business activity, but adds that because its work is largely invisible when things run smoothly, it can be an easy scapegoat.

“Any failure in systems, data, or uptime becomes a visible pain point for operations, sales, or customer experience — and the natural reaction is to point to IT, even if the underlying problem involves other teams, unclear processes, or budget constraints,” he says. “In crises, people seek a tangible culprit, and IT is the easiest target.”

Xi says that CIOs can counter a negative perception by building transparency and trust before problems arise. “This means reporting not just incidents but outcomes, explaining trade-offs, and connecting technical decisions to business impact,” he explains. “The IT leader who documents why a system choice was made, what risks were considered, and how mitigation is handled, creates credibility that pays off the next time an issue arises.”

A mistake Xi frequently sees is IT leaders becoming defensive or buried in technical explanations when blamed with a failure. “This often reinforces the perception that IT is opaque or aloof,” he notes. “A better approach is framing the problem in business terms: what happened, why it mattered, and what is being done to prevent a recurrence.”

7. IT is viewed as a cost center

In many boardrooms, technology is still viewed as a cost center rather than a strategic driver, says Abhishek Bhatia, CEO at vehicle tracking systems provider ShadowGPS. Therefore, when something breaks, there’s the assumption that IT should have prevented it, Bhatia states.

“Actually, most failures are a cross-functional process in which budget, risk tolerance, and business decisions all play a role, yet IT becomes the focal point because it owns the infrastructure,” he says.

To escape the cost center label, Bhatia advises CIOs to reposition IT from reactive support to proactive risk management. “This means translating technical risk communication into business language before a crisis happens,” he says, adding that regular board-level reporting on current system resilience, cybersecurity posture, technical debt, and any resource gaps will help build shared accountability.