Have you tried my Leadership Heroes & Archetypes Quiz yet? No? Give it a go here. Join us now at the Integrity Leaders Community: From technical expert to trusted leader. For first-time managers in tech, seeking clarity on their leadership style (and who have a healthy love of sci-fi). More info at the bottom!

Listen to this week’s podcast episode, Ep.250: From Commodore 64 To AI; Technology, Cybersecurity, Change and What it All Means for Leadership, with Brian Beck, click here to listen now.

When business owners demand new technology without a clear outcome, they create operational noise. This week, I discover why successful adoption requires executive vision and clear human alignment.

As we mark our 250th edition of this podcast and newsletter, I've been reflecting on how technology and uncertainty have often been front and centre in the leadership conversations I’ve had over the last 5 years (longside other big topics of the day like COVID, Remote Work and/or Empathy).

Whatever sector you work in, it seems nearly impossible to read industry news without running into discussions about artificial intelligence, digital transformation and rapid change. Even the mainstream headlines have been full of ‘AI’ news lately. And yet… beneath the excitement and anxiety, the core challenge remains consistent: how do we adopt new technologies in a way that will strengthen our business without losing the human foundation that makes our teams work?

Perfectly placed to answer that question is this week’s podcast guest, Brian Beck, who specialises in cybersecurity and technology strategy. Brian’s journey in technology spans thirty-five years, his love of tech began with early video game consoles like Pong, Space Invaders and the Commodore 64 (full disclosure, we spent a while at the start of the podcast talking video games and our shared experiences of early gamer life). Over the decades, he grew alongside the industry, moving from repairing the first HP LaserJet printers (which I’ve been known to refer to as ‘infernal machines’) to managing server networks and guiding executives through early cloud computing right the way up to his work today with AI and cybersecurity.

Brian recalled a pivotal moment when Microsoft first introduced “the cloud”. He attended a presentation designed to explain the architecture, complete with thirty-five dense slides covered in arrows, diagrams, and technical acronyms. Looking around the room, he realized that nearly everyone present was completely lost, including himself.

That experience became a lightbulb moment, as he realised that the primary barrier between a business and new technology isn't lack of features or capabilities, but a translation problem. When “IT” is treated merely as a reactive cost centre rather than a strategic enabler, leaders struggle to understand how new systems serve their goals. In the case of the cloud, those complex diagrams simply meant having a secure server hosted off-site that your team could access anywhere.

We see that translation failure play out with artificial intelligence today just like the dot-com era or Y2K, the current wave of change has triggered anxiety. Brian frequently gets calls from business owners stating urgently, "Brian, we need AI!" When he asks what specific problem they want to solve, the answer is often a vague, "We need it for... something."

Deploying technology simply because it’s popular is a recipe for operational confusion (dare I say… for disaster?!). Every meaningful business investment requires a defined target, an identified need and a clear return on investment, not to mention a credible plan for implementation and communication. If you can’t explain the specific business outcome you want to achieve, throwing software or other technology at the problem will only generate friction.

One of the greatest mistakes a leader can make during a technological shift is allowing fear of change to take root within the organisation. When employees hear that management is bringing in new automated tools, their immediate reaction is often defensive (and understandably so), they worry about job security, assume their expertise is being devalued, or feel their individual voice is being erased.

As Brian pointed out, the tools like LLMs, Agents and other automation/algorithmic tools under the banner of “AI” should be implemented as a complementary assistant for your team, not a substitute for human thought or critique. Its true value lies in helping your people cut through administrative fluff faster, giving them space to exercise critical thinking and creativity; it’s about amplifying the human voice rather than replacing it.

Like any effective change programme, leaders must actively coach their teams through this transition, removing fear before introducing the change (in this case technology). When you demonstrate that it’s being brought in to handle repetitive tasks and support their daily work, employees can stop viewing the technology as a threat and, instead of resisting adoption, they begin to embrace it as a helpful resource.

Using these tools effectively requires keeping a human firmly in the loop. Passing off entire communication channels or strategic decisions to automated outputs degrades your brand's reputation; whether you use a tool to help draft an email, outline a project, jumpstart an idea, the output must be filtered through human judgment, authentic tone, critical thought/review and your personal standards or brand values. Technology can certainly help start the engine, but human expertise must drive the vehicle.

Beyond operational and cultural aspects, there is a critical angle that receives far too little attention in executive discussions: cybersecurity and risk management.

We’re currently experiencing what industry experts call "AI sprawl." Automated features are being embedded into virtually every piece of software and hardware on the market, from accounting platforms to single-function printers (even your fridge?! Although that may be a rumour…) often these features are activated by default without the user or business owner ever requesting them, or potentially being aware of them.

This expansion creates massive security and liability risks, for example when employees use free, unvetted online tools to process internal files, they may inadvertently feed sensitive financial data, proprietary strategies or ideas, and even client details into external, public models and/or allow the company that owns that LLM or tool to make use of that data for future training of their models etc.

If an organisation lacks a clear AI usage policy or governance framework, its security margin shrinks to zero. Allowing employees to use a chaotic mix of disconnected platforms also creates multiple vectors of risk that no IT department can properly monitor. So, the lesson is: adopting new software cannot be left as an informal experiment, leaders must establish clear boundaries, evaluate their software ecosystem, select the most appropriate tools for their needs and ensure their foundational infrastructure is secure before scaling new tools.

Achieving operational stability requires a commitment to consistency. Small businesses often fall into the trap of straddling multiple environments, using one provider for email, another for file storage, a third for office software and a patchwork of third-party applications for communication (I am, as I admitted to Brian, 100% one of these small businesses…).

This fragmented approach creates credential chaos, increases subscription overhead and complicates security in the case of ‘AI’, it can also make it very difficult to keep track of what data is where and what your vulnerabilities might be. A major part of effective technology leadership is picking a unified platform standard and committing to it. Whether your organisation chooses a Microsoft environment or a Google framework, establishing a single operational foundation allows you to streamline security protocols, set usage guidelines and scale efficiently. As Brian says: every platform has drawbacks, but committing to one standard brings order to operations.

Ultimately, setting technical standards is only half the battle; the rest comes down to how you lead your people. When I asked Brian about his best memory of being led, he recalled a senior executive who modeled true collaborative leadership. Instead of issuing top-down directives, this leader sat down, shared his high-level vision and actively asked for input.

When Brian offered a different perspective based on his frontline experience, the executive listened carefully and then they blended their ideas. Next, the senior leader provided "deflector shields" (safe cover from organisational friction) so the team could test and prove the new approach. That combination of executive protection, open listening and mutual trust allowed their division to lead the entire organisation in performance.

Navigating technological change isn't about chasing every shiny new tool that hits the market, nor is it about letting anxiety dictate strategy. It requires stepping back, establishing a secure structural foundation and leading your people with clarity and presence.

When you treat technology as a strategic enabler rather than an isolated change project, you can strip away the hype and focus on what truly matters: supporting your team, protecting your business and delivering genuine value to your clients.

True operational strength comes from aligning your systems with your human talent.

-

Listen to the full episode now, as I chat two of my favourite things (video games, and leadership… also Star Trek, towards the end. So THREE of my favourite things) with Brain, at: https://smartlink.ausha.co/leading-with-integrity/ep-250-from-commodore-64-to-ai-technology-cybersecurity-change-and-what-it-all-means-for-leadership-with-brian-beck

Or, if you prefer video then you’ll find it on YouTube too: https://youtu.be/qedRE2PKWb4

Join me again next week for a very different topic, as I chat with M.K. Hoffman, the author of ‘Rant: A true story of one man’s fight against big banks and systemic corruption’ about the financial crash of 2008, business, ethics, leadership and the underlying, inspirational message that: everyone can make a difference.

I hope you’ll be there, and in the meantime: THANK YOU for reading, listening, supporting Leading with Integrity. There’s no show or newsletter, no future of leadership without each and every one of you.

Be a Leader Not a Boss,

- David

P.S. My apologies for the delay this week, we’re a day late due to technical difficulties (bit of an irony there given the topic and Brian’s expertise).

In case you don’t know me that well, I’m David Hatch and I’m here to help you lead like a Starfleet Captain.

If you’re a new manager or first-time leader in a tech, expertise or specialist driven workplace and you’re feeling lonely, stuck, overwhelmed, or simply ready for your next chapter in leadership, the Integrity Leaders Community offers conversations, courses, resources and support to help you grow one step at a time. If you have a healthy love of sci-fi and want to learn more about leadership, then this is the community for you! Solopreneurs also welcome. 😉