There’s a conversation that happens a lot in growing companies – Someone mentions, almost casually, that the team loses “a little bit of time” to IT problems. Password resets, VPN weirdness, printers doing whatever printers do. They say it like it’s just weather. Like, yeah, it rains sometimes.
And that’s the thing. The tools that worked at ten people are quietly falling apart at forty, but nobody’s really noticed because the workarounds became habit. Someone restarts the server. Someone else keeps a spreadsheet of logins. Everyone copes. But coping isn’t a strategy. And the signs that a business has outgrown its setup tend to be pretty obvious once someone actually points them out.
The Firefighting Problem
This is probably the most common one, and also the one people are weirdest about admitting. If the IT approach is basically “wait for something to break, then scramble,” that’s not managing technology. That’s just reacting to it.
This is where itsm tools start to make sense for a lot of mid-sized businesses. Instead of everything running on “someone shouts and someone else fixes it,” there’s actual structure. Tickets get tracked. Issues get prioritised. Patterns get spotted before they turn into outages. Not exciting. But it works, and it stops the IT person from spending their entire life in firefighting mode.
A recent piece in Computer Weekly flagged something that captures this perfectly. A huge proportion of UK organisations are spending heavily on new technology but still don’t have a formal strategy behind any of it. The money’s flowing. The thinking isn’t. And that gap between investment and planning? That’s where the fires start.
Nobody Can See What’s Actually Going On
This one’s more subtle, and it’s easy to underestimate why it matters so much. When a team is small, everyone knows everything. You could probably name every device on the network. But then the company grows. Remote workers, contractors, a pile of SaaS subscriptions that nobody’s quite sure who authorised. Ask “what happens when that server goes down?” and the answer is a long silence.
Not a dig. That’s genuinely where most businesses end up. They grow into complexity without ever deciding to. The National Cyber Security Centre published something called the 10 Steps to Cyber Security that’s worth a look. It’s aimed at medium to large organisations but honestly, the principles apply earlier than most people think. Some of it feels like common sense. Some of it (the bits about network monitoring and access control, particularly) is probably going to be a bit uncomfortable. In a useful way.
Can’t secure what can’t be seen. Can’t plan what isn’t understood. Sounds like a motivational poster, fair enough, but it’s true. If the answer to “who has admin access to our cloud storage?” is a shrug, that’s not just an IT problem. That’s a business risk sitting there in plain sight.
New Hires Make Everything Worse
OK, that heading is deliberately dramatic. But there’s a version of this that’s real and weirdly underappreciated. In a well-set-up business, onboarding someone new should be straightforward. Laptop, accounts, permissions, done. Maybe a day. In a business that’s outgrown its IT? Every new hire exposes the cracks. There aren’t enough licences. Nobody documented the onboarding process because the last three people just “figured it out.” The shared drive is full. Someone’s still using a personal Gmail account for work files.
The frustrating part is that this is fixable. Not overnight, and not cheaply, necessarily, but it’s not some impossible infrastructure overhaul. A lot of it comes down to documenting what’s already there, figuring out what’s redundant, and actually planning for the next ten hires instead of just the current one. There’s actually a broader pattern here that keeps showing up across the tech space. We looked at something similar in our piece about AI coding assistants, where the same dynamic was at play. Tools adopted because they’re available, not because there’s a plan. Growth treated as something that just happens rather than something to prepare for.
Anyway. None of this is revolutionary. But it’s the kind of thing that gets waved away until it bites. And by that point, the fix has already cost more than it would’ve six months earlier. So maybe just… poke around the setup. Ask the uncomfortable questions. The answers might sting a bit, but at least they’ll be there.
Conclusion
Most growing companies don’t make a conscious decision to neglect their IT setup. They simply grow past it. What once felt scrappy and efficient at ten people becomes fragile and opaque at forty, but because the problems emerge gradually, they get normalized. Workarounds become culture. Friction becomes background noise.
The shift happens when someone stops treating those issues as “just how things are” and starts seeing them as signals. Signals that the business has reached a level of complexity that needs structure, visibility, and intent behind it. Whether that means introducing ITSM tools, formalizing onboarding, or just mapping out what actually exists across systems, the goal isn’t perfection. It’s awareness.
Because the real risk isn’t that things break. It’s that they keep sort of working just inefficiently enough to slow everything down, and just invisibly enough that no one takes ownership of fixing them.
Frequently Asked Questions
What are the early signs a company has outgrown its IT setup?
Common signs include frequent IT issues being handled reactively, lack of visibility into systems and access, inconsistent onboarding processes, and reliance on informal workarounds like shared spreadsheets or undocumented fixes.
What is ITSM and why does it matter for mid-sized businesses?
ITSM (IT Service Management) refers to structured approaches and tools used to manage IT services. It helps businesses move from reactive troubleshooting to proactive management by tracking issues, improving workflows, and identifying recurring problems before they escalate.
Why is “firefighting” a problem in IT management?
A firefighting approach means teams only respond after issues occur, which leads to repeated disruptions, lost productivity, and burnout. It also prevents long-term improvements because there’s no time or system for identifying root causes.
How does poor visibility affect business operations?
Without clear insight into systems, devices, and user access, businesses face higher risks of downtime, security breaches, and inefficiencies. It also makes planning and scaling much harder because decisions are based on incomplete information.
VISIT MORE: APEX MAGAZINE
