A featured contribution from Leadership Perspectives: a curated forum reserved for leaders nominated by our subscribers and vetted by the CIOReview Advisory Board.

Must Have Ideas
Building Better IT through Practical Leadership


Jack Beale
Grounding IT Leadership in Hands-On Experience
Before I ever worked in IT, I was a welder and fabricator. I used CAD to design bespoke solutions for customers and then built them using heavy machinery. I think that gave me an engineer brain from day one and it still shapes how I handle processes and how I think about the real-world impact of my work.
I started in IT in 2018 as an apprentice at a freight forwarding company, supporting around 900 users across the UK, US and China. It taught me so much about what to do in IT and probably more importantly what not to do. I ended up redoing the cable management in their communications rooms out of hours and on one occasion I actually fell asleep under a desk halfway through. It taught me early on that neat cabling is not just for show. It is what makes troubleshooting quick when something goes wrong.
From there I moved to the data centre they used and I remember thinking I had finally made it as an ‘Engineer.’ Looking back that was a bit naive. I have since worked with some amazing engineers and if I am honest there was a bit of imposter syndrome in that feeling. Later I supported over 20 sites around the world.
Turning IT Reliability into Everyday Productivity
I joined my current organisation as their first internal IT hire, taking over from an outside provider. The first thing that needed attention was the network. Constant dropouts meant our editors could not work from the NAS without it going offline and it was a nightmare. The previous setup had grown over time and needed proper work, from inconsistent switch firmware to a network design that needed rethinking. I rebuilt almost all of it out of hours and the dropouts stopped.
The biggest lesson for me was that the team is the customer. It is their work and their daily workflows that IT affects. Good IT should not be heard.
Protecting Systems Without Disrupting Workflows
For me, balancing reliability, security and business continuity starts with server replication and a proper disaster recovery strategy. We follow the 3-2-1 backup rule, replicating our core infrastructure to a second site and then on to a dedicated data centre. If something goes wrong the aim is that users never know.
“It is the customer’s work and their daily workflows that IT affects. Good IT should not be heard.”
Security is a balancing act too. When a security rule causes friction I look at whether it is a learning issue or whether it has actually broken part of someone's workflow. Learning issues should be dealt with kindly and through positive reinforcement. If a core part of someone's workflow is broken then the rule or the system needs to be looked at as a whole.
Managing Change without Interrupting the Business
The biggest project I have delivered was a greenfield IT build in a 250,000 sq. ft. warehouse. It was completely empty, so we had to do everything from scratch. I delivered the IT infrastructure on my own, but I was lucky to work alongside some fantastic people who handled the electrical works and built the new office space. It took six months of 18-hour days and weekends.
That included rebuilding our TV channel from the ground up in the new facility. SDI and ethernet runs for the cameras, a custom network with VLAN segmentation and QoS rules, plus brand new desks and audio. For that part, I was essentially a broadcast engineer.
The hardest part was hitting tight deadlines and getting everything in the right order. Certain parts of the network had to be up and running first so the contractors could do their jobs, so it all had to be planned so nobody was sitting around twiddling their thumbs.
The business and the channel kept running the whole time. We built the new site alongside the old one, copied over what already worked to keep the move smooth and drastically improved the rest. The new network and systems were designed around high resilience, failover and room to scale.
My advice to anyone facing a similar build is to be adaptable. The plan will not cover everything, and you need to be able to think on your feet.
Building Trust through Responsive IT Support
I think IT should be treated like a customer service desk. We are here to help and support people in their roles, and we should not expect them to have the same knowledge as we do. There is a lot of arrogance in IT where people think users are silly for not knowing how to do something, but that is our job. We are there to help and guide.
Shadow IT is a good warning sign. In my experience, it usually happens when IT cannot respond fast enough, and there is a breakdown in communication or trust that things will be moved along quickly. With the IT landscape constantly changing and new products and tools arriving faster than ever, that supportive approach matters more now than it ever has.
The views expressed in this article are my own and do not represent those of Must Have Ideas.