Somewhere in your organisation right now, there is a person in IT who has not finished a hot cup of tea since 2019. They are not fixing your laptop. Well, they are also fixing your laptop. But that is approximately 3% of what is happening. The other 97% is a sprawling, invisible, never-quite-finished operation that keeps your entire digital existence from collapsing into a smoking heap, and which receives the recognition typically afforded to the office air conditioning. Noticed only when it stops working.
The Perception Gap
Here is how most people understand IT: something breaks, IT fixes it, everyone goes home. Here is how it actually works. Something is about to break; IT notices, intervenes, patches, tests, documents, and prevents the break, and nobody knows anything happened. A ransomware probe is quietly turned away at the perimeter and nobody raises a ticket for that one. Stuff just seems to work.
This is IT's central existential problem. Success is invisible. Failure is a front-page incident report. There is no middle ground.
Patch Tuesday
Every second Tuesday of the month, Microsoft releases its security updates. Last month's drop included patches for 134 separate vulnerabilities. Eleven were rated Critical. One was already being actively exploited in the wild before the patch even landed. You might think: just push the patches out, done, home by five. You sweet, innocent person. Each patch needs testing, because patches occasionally break things, sometimes quietly in ways that only surface three weeks later. Multiply 134 patches across hundreds of devices, several operating system versions, a handful of legacy systems that predate some of the senior leadership team, and a user base who will click "remind me later" until the heat death of the universe, and you have a monthly project that is, charitably, not trivial. This happens every single month.
The Certificate Nobody Knew Existed
Somewhere in your infrastructure there is a digital certificate that expires in 47 days. Maybe it expired last Thursday and nobody has noticed because the system it protects is only used on the third Wednesday of the quarter. When it expires, something breaks with an alarming error nobody understands. The renewal itself takes four minutes. The other thirty-six are spent establishing which system it belongs to, who owns it, why it was not in the register, and quietly noting the seventeen other systems that may be in a similar condition. This is not an IT failure. This is IT locating invisible technical debt in real time, under mild pressure, while someone waits for their email to work.
"Can You Just..."
Two words that trigger a very particular internal experience. "Can you just add this person to the system?" Sure. Which system? They need four. Each has a different access model, two require manager approval, one has a licence cap, and the fourth is the legacy application whose workaround is documented in a Word file from 2017. Total elapsed time to "just add" this person: forty-five minutes. "Can you just set up a new project folder?" Of course, subject to inherited permissions, data classification if it is sensitive, retention policy if it crosses a regulatory boundary, and guest provisioning with a conditional access review if an external party needs in. "Just" is doing a lot of heavy lifting in these sentences.
The 3am Problem
Nobody thinks about IT at 3am, except IT. Planned maintenance exists because the only safe time to restart a production server or migrate a database is when the building is empty. So while you slept last night, someone applied a critical patch to your email server, verified the backups, investigated a security alert that turned out to be a misconfigured log source but could not be confirmed without forty minutes of looking, restarted a service that had been degrading since Thursday, and updated a six-month-old runbook. You woke up, your email worked, and you made no connection between these two facts. This is, genuinely, the ideal outcome.
The Honest Version
IT is not a support function. It is the operational foundation for everything your organisation does digitally, which is now most of what it does. You can live without HR for a long time, Legal for months, Finance until you want to get paid, but how long could your organisation last without IT? When IT is working well, you notice nothing. When it is underfunded, understaffed, or treated as an afterthought until something catastrophic happens, you will eventually notice a great deal, all at once, at the worst possible moment. The choice belongs to the organisation. IT will keep watching the tea go cold either way.
