The Number One Mistake Leadership Makes Hiring Internal IT

The Number One Mistake Leadership Makes Hiring Internal IT

Picture that you own a large facility and you hire a plumber to install all the plumbing throughout the building. The job gets done, and when it's finished, the plumber proudly hands you a summary showing just how much money they saved you compared to what you were originally quoted. You're pleased. It's a win.

The first couple of years, everything works exactly as it should. Hot water and cold water show up right where you need them. Every so often a pipe develops a crack and needs a repair, but that seems like ordinary wear and tear. The plumber comes back out, patches the section, and life goes on.

Then the repair calls start showing up more often than they used to. What used to be an occasional patch job becomes something you're dealing with every few months, then every few weeks. And it's not just more frequent, it's bigger each time, no longer a single joint here or there but entire runs of piping that need attention.

Eventually it gets bad enough that you bring in a second plumber just to get another set of eyes on it. That's when you finally learn what's actually been happening behind your walls. The piping installed throughout your building was never the material it should have been. It was a far cheaper, lower grade product that was never built to handle the pressure and volume of water your facility actually needs to move every day. All those years of "savings" the first plumber showed you were really just the cost of substandard material catching up with you, one crack at a time.

Now you're not looking at a repair. You're looking at ripping out and replacing the piping behind every wall in the building, a project that can easily run into hundreds of thousands of dollars, sometimes more, and one that nobody could have predicted just by looking at the invoices from year one.

This is exactly the shape of what a company discovers, sometimes years too late, when they realize they hired the wrong IT person. Someone quietly built an entire environment out of the technology equivalent of that cheap piping, all in the name of savings nobody thought to question until the day it was already failing.

The Pattern We See Over and Over

Here's how it usually starts. A company hires an internal IT person, maybe someone on staff who was "good with computers" and got promoted into the role. Either way, this person now owns the technology environment, and they know, consciously or not, that the fastest way to prove their worth to leadership is to point at a number and say "look what I saved you."

That instinct isn't malicious. Most of these people genuinely believe they're doing right by the company. But when cost cutting becomes the primary way someone measures their own value, every decision starts running through that filter. Renew the support contract, or let it lapse and pocket the difference? Replace aging equipment with something comparable, or grab something cheaper off a retail shelf? Keep the backup running, or quietly let it expire because "we haven't needed it yet"?

Each of those decisions looks small in isolation. Each one comes with a number that leadership can see and appreciate. What leadership usually can't see is the risk stacking up behind that number.

A Real Example We're Watching Unfold Right Now

We have a long time client dealing with exactly this. Leadership brought in a new internal IT person to replace someone who had built out a genuinely solid environment: enterprise grade equipment, redundant across multiple locations, set up specifically so that if one piece failed, the business kept running without anyone noticing.

The new hire has spent their time since then quietly swapping that environment out piece by piece, and not for anything comparable. Enterprise grade equipment is being replaced with the kind of consumer grade gear you'd find built for a home office, not a multi site business. We've even learned that once the current backup contract expires, the plan is to stop backing up the servers altogether.

On paper, every one of those moves probably shows up as a savings line somewhere. In reality, this company now has almost no margin for error. A single hardware failure, a single ransomware event, a single bad afternoon, and there is no redundancy left to catch them. The "savings" they're being shown right now were never real. They're borrowed against a future bill that hasn't come due yet, and when it does, it will be enormous.

Leadership in this case has put their trust in this new hire, believing this person has the company's best interests at heart. But when someone's primary way of proving their value is cost savings, that focus is not necessarily aligned with what a business actually needs to run successfully over the long term. The real question worth asking is whether leadership understands the risk being introduced here, or whether they are simply taking these updates at face value without knowing what sits behind them. Once again, this isn't a story about malicious behavior. It's a story about having the wrong person entrusted with decisions that carry this much weight.

Why This Feels Safe, Until It Isn't

The reason this pattern is so dangerous is that it doesn't feel dangerous while it's happening. The lights stay on. Email works. Nobody notices the aging server, the firewall that hasn't been updated in years, or the fact that "backup" now means a single copy sitting on the same network it's supposed to protect.

It feels stable. It feels efficient. It feels like proof that the IT person made the right call, because nothing has broken yet. But stable and current are not the same thing, and an environment can be stale for years before that staleness turns into an actual outage, breach, or six figure replacement project.

What This Means For You

If any part of this sounds familiar, that's worth sitting with for a moment. Not every internal IT hire falls into this trap, and cost consciousness isn't inherently a bad trait in a technology leader. The problem isn't that someone tries to save the company money. The problem is when saving money becomes the entire strategy, and growth, resilience, and modern capability get quietly sacrificed to keep that number looking good.

It's the same idea as a mechanic quietly removing the brakes from the back of your car to save you money. The savings are real right up until the day they aren't, and by then it's no longer a savings conversation at all.

The next post in this series digs into how to actually spot this before you hire someone, and what a genuinely good internal IT hire looks like in practice. The one after that tackles a question we think gets asked the wrong way almost everywhere else: what real risk looks like when a business puts all of its technology decisions in the hands of one person, no matter how skilled that person is.

For now, the honest question worth asking is simple. When you look at your own environment, are you looking at something that's actually healthy, or something that's just been quiet for a while?