<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Evolving Digital Leadership</title>
        <link>https://www.evolvingdigitalleadership.com/</link>
        <description>Insights on digital leadership, the AIAR framework, and navigating technology disruption.</description>
        <lastBuildDate>Sun, 12 Jul 2026 05:55:11 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <copyright>All rights reserved 2026, James Brett</copyright>
        <item>
            <title><![CDATA[Stop Watching the AI Tsunami - Leading your people through the fear of AI]]></title>
            <link>https://www.evolvingdigitalleadership.com/blog/StopWatchingTheTsunami</link>
            <guid isPermaLink="false">https://www.evolvingdigitalleadership.com/blog/StopWatchingTheTsunami</guid>
            <pubDate>Sun, 12 Jul 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[A practical guide for leaders on turning their people's fear of AI into adoption]]></description>
            <content:encoded><![CDATA[<p>In 2019, I opened my book <em>Evolving Digital Leadership</em> with a warning: &quot;Artificial intelligence will commoditize a significant number of jobs, including software development.&quot; I described AI as a tsunami wave, and I wrote that leaders who assumed it would arrive slowly and obviously would be unpleasantly surprised.</p>
<p>It sounded dramatic at the time. It isn&#39;t dramatic anymore. It&#39;s this quarter&#39;s operating reality.</p>
<p>But here&#39;s what I didn&#39;t fully anticipate, and what I now watch every day as a CTPO leading an AI transformation: the hardest part of this wave isn&#39;t the technology. It&#39;s the fear.</p>
<h2>This time, it&#39;s personal</h2>
<p>Every previous wave of digital disruption had a comfortable feature for technologists: it happened to <em>other people</em>. Automation came for the factory floor, the bank teller, the travel agent — and engineers built the software that did it. Digital leaders have spent thirty years disrupting everyone else&#39;s profession.</p>
<p>AI is the first wave that erodes the value of the disruptors themselves. For the first time, engineers are watching a machine do the thing that made them valuable — writing code, designing systems, debugging, testing — and do it fast, cheaply, and increasingly well. Every stage of the software development lifecycle is changing at once: how we specify, how we build, how we review, how we test, how we ship, how we support. Even the deep operating assumptions are flipping. For two decades we optimised our teams for focus — one thing at a time, sequential flow, limit work in progress. With AI, the leverage now comes from parallelisation: one person orchestrating many streams of work simultaneously. That isn&#39;t a tooling change. It&#39;s a paradigm change, and it invalidates hard-won instincts.</p>
<p>So let&#39;s be honest about what your people are feeling, because they may not say it out loud in your town halls: <em>fear</em>. Fear of being replaced. Fear that a decade of craft mastery just got devalued. Fear of being exposed as slower than a colleague with a chat window. This fear is not irrational, and it is not a weakness. It is an accurate reading of a genuinely changed environment.</p>
<p>The leadership mistake is not that we have fearful people. It&#39;s that we pretend we don&#39;t.</p>
<h2>The self-fulfilling prophecy</h2>
<p>Here is the cruel mechanic at the centre of this moment: <strong>AI transformation succeeds only through adoption, and fear is the single biggest blocker of adoption.</strong></p>
<p>Fear produces resistance. Resistance shows up quietly — the engineer who &quot;tried Copilot and it wasn&#39;t very good,&quot; the team that adds an AI review step so heavy it&#39;s slower than the old way, the architect who can list twenty reasons the output can&#39;t be trusted. Each objection sounds technical. Underneath, most of them are protective.</p>
<p>And resistance creates exactly the outcome people fear. The individuals, teams, and organisations that don&#39;t adopt AI will not be made redundant <em>by AI</em>. They will be outcompeted by the people, teams, and organisations that did adopt it — who ship faster, learn faster, and cost less per outcome. The prophecy fulfils itself: <em>I resisted the thing I feared, so the thing I feared happened.</em></p>
<p>In the book I called this dynamic by its older name. Darwin&#39;s natural selection prunes out those least suited to a changing environment — slowly, passively, without malice. In the digital ocean, the pruning is neither slow nor optional. Waiting to see how AI plays out <em>is</em> a decision, and it&#39;s the one natural selection punishes first.</p>
<h2>Get off the beach</h2>
<p>The dominant mental model of AI right now — in the media, in the pub, in your engineering stand-ups — is the tsunami. A single, monstrous, unavoidable wall of water. And what do people do when they believe a tsunami is coming? They stand on the beach, transfixed, watching the horizon. Some deny it&#39;s real. Some argue about how big it will be and when it will land. Nobody standing on the beach is getting ready to do anything except be swept away.</p>
<p>I want to offer you the reframe I use with my own teams: <strong>AI is not one tsunami. It is a surf break — set after set of waves, arriving continuously.</strong> Some waves are tricky and will dump you. Some are fun. Some are enormous and only for the brave. But none of them can be survived from the beach, and none of them need to be. Surfers don&#39;t control the ocean; they get <em>on the wave</em>, and the wave&#39;s energy — the same energy that terrifies the people on the sand — becomes the thing that propels them.</p>
<p>The wave doesn&#39;t care whether you&#39;re afraid. It only cares whether you&#39;re on your board.</p>
<p>That reframe matters because it changes what fear is <em>for</em>. On the beach, fear is paralysis. On the board, fear is information — it sharpens attention, it tells you which waves to respect. The goal for a leader is not to eliminate the fear in their organisation. It&#39;s to move people from the beach into the water, where fear becomes useful.</p>
<p>This is exactly the problem <em>Evolving Digital Leadership</em> was written to solve. The book&#39;s central argument is that when the environment changes faster than humans naturally adapt, leaders must practise <strong>Unnatural Selection</strong>: deliberately evolving faster than the pace of change rather than waiting for change to select against them. And the engine of Unnatural Selection is a four-step loop — the evolution helix — that maps directly onto the AI moment: <strong>Awareness, Intention, Attention, Reflection.</strong></p>
<h2>Awareness: name the fear before it names you</h2>
<p>Every cycle of evolution starts with awareness, and right now the most important awareness a leader can build is emotional, not technical.</p>
<p>When we&#39;re stressed, we regress to lower levels of awareness and become reactionary — we react instead of choosing how to respond. That&#39;s what fear-driven AI resistance is: a reaction masquerading as a considered technical position. You cannot argue someone out of a reaction with a benchmark.</p>
<p>So start by naming reality, out loud, as the leader: <em>&quot;This is the first time our profession&#39;s own value is being disrupted. It&#39;s reasonable to find that confronting. I find it confronting.&quot;</em> You will be amazed what that sentence unlocks. Fear that is named can be examined; fear that is unnamed runs the show from the shadows.</p>
<p>Then extend the awareness outward. What is actually changing in your SDLC, and what only feels like it is? Where does AI genuinely outperform your people, and where does their judgement still carry the value? Which of your own instincts — like optimising for sequential focus — are now liabilities? Awareness is knowing where the waves are actually breaking, rather than where the people on the beach are pointing.</p>
<h2>Intention: define what riding the wave means for you</h2>
<p>Fear fills any vacuum where intention should be. If your people don&#39;t have a clear, positive picture of what success looks like <em>with</em> AI, their imaginations will default to the negative one: replacement.</p>
<p>Intention works because of how our filtering minds operate — we notice what we&#39;ve decided matters. A team whose intention is &quot;protect our current way of working&quot; will notice every AI failure and hallucination. A team whose intention is &quot;become the most AI-leveraged team in our industry&quot; will notice every opportunity. Same ocean, different waves.</p>
<p>The book&#39;s three Unnatural Leader intentions translate directly:</p>
<p><strong>Personal — be passionately curious.</strong> Curiosity is the emotional opposite of fear, and it&#39;s a choice. Make AI exploration something your people are <em>rewarded</em> for, not something they do guiltily between &quot;real work.&quot;</p>
<p><strong>Team — move from performance management to growth.</strong> If your people believe AI metrics will be used to rank and cull them, you will get theatre, not adoption. If they believe you are investing in growing them into AI-augmented roles, you will get experimentation. Growth is the antidote to the self-fulfilling prophecy.</p>
<p><strong>Stakeholders — build mutually beneficial relationships.</strong> Your board wants AI efficiency; your teams fear AI displacement. The leaders who thrive will be the ones who can hold both truths and broker honest deals between them, rather than promising each side a comfortable lie.</p>
<h2>Attention: get in the water</h2>
<p>Intention without attention is a wish. Attention is what you actually <em>do</em> — and in an AI transformation, what leaders spend attention on is broadcast to the whole organisation as the real strategy, whatever the slide deck says.</p>
<p>Put your attention where adoption happens: use the tools yourself, visibly. Ride small waves before big ones — pick contained, low-risk problems where AI can produce a fast, felt win. Restructure the work to exploit parallelisation instead of forcing AI into your old sequential flow. And ring-fence real time for people to practise; nobody learns to surf during a board meeting about surfing.</p>
<p>Expect wipeouts. A team&#39;s first AI-heavy project will produce some rubbish. Surfers don&#39;t interpret falling off as evidence the ocean is broken — but organisations routinely interpret one failed pilot as evidence AI &quot;doesn&#39;t work here.&quot; Which is why the last step of the loop matters most.</p>
<h2>Reflection: how every wave makes you better</h2>
<p>Reflection is what converts experience into evolution — it&#39;s the step that turns one loop of the helix into an upward spiral instead of a circle. It is also the step that busy organisations skip first, and in an environment moving this fast, skipping it is fatal: you make the same mistake at higher speed.</p>
<p>Make reflection routine and collective. After each AI experiment ask: What did we try? Where did it genuinely help, and where did it fail? What did that do to our fear — is it shrinking with contact, or growing? What will we try on the next wave that we couldn&#39;t have known before this one?</p>
<p>Notice what this does to fear over time. Reflection turns every wave — including the ones that dumped you — into evidence that you can learn faster than the environment changes. That evidence, accumulated ride after ride, is what confidence actually is.</p>
<h2>It&#39;s not cheating</h2>
<p>One more piece of fear deserves its own paragraph, because I hear it constantly from brilliant engineers: the quiet feeling that using AI is <em>cheating</em> — that work done with a model is somehow less legitimate, less craftsmanlike, less <em>theirs</em>.</p>
<p>I wrote a chapter about this mindset in 2019, before AI made it urgent, and its title is the whole message: <strong>It&#39;s Not Cheating.</strong> You don&#39;t get any points in life for doing things the hard way. The value of an engineer was never the typing; it was the judgement, the design, the understanding of what should be built and why. AI hasn&#39;t erased that value. It has concentrated it.</p>
<h2>The choice on the beach</h2>
<p>Natural selection doesn&#39;t negotiate, and it doesn&#39;t wait for people to feel ready. But it has one weakness: it only catches those who stand still.</p>
<p>The fear in your organisation is real, rational, and — handled well — useful. Your job as a leader is not to promise people the ocean will calm down. It won&#39;t. Your job is to get them off the beach: name the fear, set the intention, put your attention in the water, and reflect after every ride so each wave makes you better than the last.</p>
<p>The people who do this won&#39;t just survive the AI era. They&#39;ll spend it the way surfers spend a good swell — working hard, wiping out sometimes, and grinning the whole way through.</p>
<p>Grab your board.</p>
<hr>
<h3>Go deeper</h3>
<p>This article is built on the Unnatural Selection framework from my book <em><strong>Evolving Digital Leadership: How to Be a Digital Leader in Tomorrow&#39;s Disruptive World</strong></em> (Apress) — a practical guide to Awareness, Intention, Attention, and Reflection, written for leaders who want to evolve faster than the pace of change.</p>
<p><strong>Get the book on Amazon or at apress.com.</strong></p>
<p><em>James Brett is a Chief Technology &amp; Product Officer, author, and leadership coach. Written by a practitioner. Still practising.</em></p>
<h2>Getting Started</h2>
<p>If this resonates, the <a href="/starter-kit">AIAR Starter Kit</a> is a free resource that walks you through the framework with practical exercises you can apply immediately.</p>
<p>Written by a practitioner. Still practising.</p>
]]></content:encoded>
            <author>James Brett</author>
        </item>
    </channel>
</rss>