Most companies don’t plan to put one person in charge of all their technology. It just ends up that way — the person who set things up, the one who always knows the passwords, the one everyone calls when something breaks. And for a long time it works. Then the company grows, and suddenly one person’s calendar is the ceiling on everyone else’s progress. This guide is about how that happens, how to spot it, and what to do about it.
What does it mean when the IT person is the “lid”?
A lid is a single point everything has to flow through. When one person is the only one who can deploy, unlock, fix, approve, or understand how a system works, your organization can only move as fast as that person’s calendar allows. The person isn’t the problem — the structure is. One human being, no matter how capable, is a bottleneck by definition once the work outgrows them.
How does one person become the bottleneck?
It rarely looks dramatic. It’s a slow accumulation:
- Informal ownership. Over time, the IT person ends up the only one who knows how the domain, the servers, the Wi-Fi, and the SaaS accounts are wired together.
- Tribal knowledge. The important details live in their head — not in documentation, because there was never time to write it down.
- Heroics get rewarded. Every time they save the day, the organization learns “we don’t need a system, we have [person].” The firefighting becomes the job description.
- Growth outpaces headcount. The company adds people and customers, but the IT function stays one person deep.
- No backup. Vacations and absences aren’t a break — they’re the moment everyone discovers how much depended on one person.
None of these are anyone’s fault. They’re what happens when capability quietly becomes dependency.
What are the warning signs your IT setup is limiting growth?
Listen for these phrases, because they’re the sound of a lid in action:
- “We have to wait for [person].”
- “Only [person] knows how to do that.”
- “Don’t touch that — [person] set it up.”
- “We can’t launch that feature until [person] has time.”
- “It’s been down since [person] left on vacation.”
There’s a more measurable version too: the number of requests piling up, the average time before anyone else can make progress, and how many basic operations fail when the IT person is away. If your technology stops working in their absence, you don’t have an IT team — you have a single point of failure.
Why does this happen even with great IT people?
Because the best IT people are the most likely to become lids. A genuinely skilled, conscientious IT person will say yes to everything, learn everything, and quietly carry it all — which is exactly how the organization becomes dependent on them. Leadership reinforces it, because “it works.” The bus factor is the real name for the risk: how many people would have to be hit by a bus before the organization can’t function. For many companies, the answer with their IT function is one.
What does the lid cost your business?
The costs are concrete and they compound:
- Speed. Every technology-dependent decision waits on one person.
- Revenue. Features, launches, and customer requests get delayed — or don’t happen at all.
- Burnout. The IT person burns out from carrying everything, and everyone else burns out from being blocked by them.
- Risk. Security patching, backups, and access management all depend on one person remembering to do them, on time, forever.
- Opportunity. The business can’t take on work it could otherwise handle, because “IT can’t support it.”
The most expensive part is invisible: all the growth that didn’t happen because the organization quietly learned not to ask.
How do you remove the lid?
The fix isn’t replacing the person — it’s removing the single point of failure. In practice that means:
- Document everything. Passwords, architecture, procedures, and the “why” behind decisions. If it isn’t written down, it’s tribal knowledge.
- Share access. No credential, account, or admin role should exist in only one person’s head.
- Build coverage. A second person who can at least keep things running while the primary is out — through cross-training, a peer, or a partner.
- Automate the routine. Monitoring, patching, backups, and user provisioning should run on schedules, not on one person’s memory.
- Plan for absence. Publish what happens when the IT person is unreachable, and test it.
- Bring in redundant support. This is exactly the gap managed IT services exist to fill: a partner who provides coverage, documentation, and 24/7 monitoring alongside your in-house person instead of replacing them.
The goal isn’t to sideline your IT person. It’s to make them the accelerator of the business instead of its ceiling — which is more rewarding for them too. We wrote separately about how offloading the routine IT work pays off in morale and revenue.