8 Biggest IT Management Mistakes and How to Avoid or Recover from Them

IT Management Mistake 1: Vendor Lock‑In

Severity: 2 – Vendors may lure you with low prices and endless promises, but once they gain control they become hard to replace, creating pricing leverage and risking job loss for IT managers.

While bulk discounts and tighter integration can be benefits, reliance on a single supplier reduces flexibility; switching providers can be difficult, especially when source code is withheld.

Howard advises diversifying across multiple cloud providers and working closely with procurement to avoid over‑dependence on any one vendor.

IT Management Mistake 2: Treating the Cloud as an Extension of the Data Center

Severity: 2 – A migration from a private VMware cloud to AWS led Best Egg to a critical server failure shortly after launch, demonstrating that cloud servers are not simply interchangeable data‑center machines.

Key lessons: design infrastructure specifically for the cloud, monitor cloud costs, build redundancy, and automate server replacement.

IT Management Mistake 3: Over‑Designing Business Cases

Severity: 1 – Securing approval for large IT spend often requires a solid business case, but without an executive champion the effort can be futile.

Mark Settle notes that only when senior business leaders are willing to back the proposal will it succeed.

IT Management Mistake 4: Hiring Below Skill Level

Severity: 2 – One incompetent hire can undermine an entire team; hiring decisions are often clouded by ego.

Derek Johnson recounts a case where a charismatic candidate with a PhD and patents was rejected by the CTO, leading the candidate to join a competitor that later destroyed the startup.

IT Management Mistake 5: Promoting the Wrong Internal Candidate

Severity: 2 – Internal promotions can be beneficial, but promoting for the wrong reasons (loyalty, career path, ego) can cause frustration and turnover.

Giancarlo Di Vece describes a scenario where a promoted developer left after three months due to misfit.

IT Management Mistake 6: Applying Agile to Core Systems

Severity: 3 – Using the same rapid‑delivery mechanisms for core services (email, ERP) can be disastrous; strict change control is required for mission‑critical systems.

Howard recommends drawing firm boundaries between agile‑friendly workloads and core infrastructure.

IT Management Mistake 7: Saying “Yes” Too Frequently

Severity: 2 – Constantly approving risky requests creates security gaps and compliance issues.

Richard Henderson stresses the need for a clear exception‑handling process and asset‑management tooling.

IT Management Mistake 8: Hiding Problems

Severity: 3 – Concealing project failures only erodes credibility; early disclosure enables faster recovery.

Settle advises building strong relationships with CFOs and business leaders so that bad news can be delivered constructively.