Example
One sets out and implements a working solution to an IT problem. One applies standard engineering principles (Yes stu, not all "computer science" folks fail to understand them) to the design, implementation and support of said solution. One applies standard business principles (because those have been studied and applied as well) to issues surrounding the solution, including return on investment and ensuring that the solution resolves the business need it is supposed to solve.
In other words, one creates a solution that works.
One is then told to change the solution by some muppet in management who thinks he knows IT because he once wrote a spreadsheet. Protests that proposed solution will fail go unheard, because protests through the management chain are intercepted by lying, self-serving managers, and protests outside the management chain are simply ignored. Like most managers, this is one who got their job because they lie, cheat and steal with impunity and gets lots of practice because that's what management does. Unfortunately, you don't get much practice lying, cheating and stealing in IT, because computers can't be lied to, cheated or stolen from.
Solution breaks. IT guy gets blamed, not the fucking asshole manager who ordered the mess in the first place, or the illiterate butt-kissing sycophantic accountants or salespeople who usually populate the management layers of IT.
Lather, rinse, repeat. Which is why I work for myself now, so that I can simply ignore these lying scumbags if they decide to screw around with what works. Dilbert isn't just a cartoon, and the pointy-haired boss isn't an oddity, it's the standard.
So if there's an IT problem, don't blame the people working in IT. Look at the management, because that's invariably those who created the problem in the first place, and it is invariably that class of creature that perpetuates the problem.
But they're really good at deflecting blame.