Where is Kevin from IT?
New technology brings new possibilities. But beneath all those new layers, there is often still one person who knows how everything really works. And Kevin has left, or wants to retire.
We keep happily building
AI is developing at speed, debates about espionage and technology dependency keep resurfacing, Microsoft 365 occasionally goes down, and software vulnerabilities keep appearing.
And what do we do? We keep happily building. Another cloud solution, another integration and, of course, AI everywhere.
All good things, but the stack keeps getting higher and the dependencies keep growing.
Somewhere underneath that stack is Kevin
Kevin from IT set everything up once. Kevin knows why certain settings are the way they are. Kevin also knows why that one checkbox absolutely must not be cleared.
Except: Kevin has left, or wants to retire.
And the documentation? It lives somewhere in C:\Users\Kevin\Temp\Production_final_v7.xlsx. Good luck with that.
If one person or one service disappears, how much comes down with it?
Do you know your own dependencies?
We talk a lot about the risks of new technology, and rightly so. But do we still know how our own IT environment fits together? Which systems depend on one another? What happens when a supplier fails, a vulnerability appears, or the person with all the knowledge leaves?
Maybe alongside all the innovation, we should look a little more often at what we already have in place.
Not everything needs to become more complicated. Good IT sometimes starts with an overview, good documentation and knowing where your dependencies are.
Want to know where you stand?
Bureau Mos IT is happy to look at it with you. Not necessarily through a large IT programme or a complicated advisory report, but simply by looking together at dependencies and what could be smarter.