5 ways of thinking that can fell IT leaders

Here’s a great article in techrepublic.com that lays out 5 dangerous ways of thinking and how they can damage IT leaders. While I agree with the author’s points, I can think of many more that I’ve encountered over the years.

Here’s one example: An IT leader needs to know when to scrap a project, even if it was their idea. I’ve seen many a failing project kept alive simply because the manager didn’t want to admit they had made a mistake. This sort of situation costs the company greatly, and is obvious to everyone.

How about you? What dangerous ways of thinking have you encountered?