What Has AI Ever Done for Us?

Why the most important role in your organisation probably does not exist yet.

Reg: Brothers and sisters. We are gathered here today because we have been asked, repeatedly, and at considerable personal expense, to invest in something called “AI.”

Stan: What’s AI?

Reg: Artificial Intelligence, Stan. The thing that every consultancy, conference, and LinkedIn thought leader has been telling us will change everything. And I put it to you, brothers and sisters: what has AI ever done for us?

Xerxes: Well, it automated our customer service.

Reg: Fine. Fine. But apart from automating customer service, what has AI ever done for us?

Stan: It writes my emails now.

Reg: Apart from automating customer service and writing Stan’s emails, what has AI ever done for us?

Xerxes: It does our data analysis in minutes instead of weeks.

Stan: It personalises our marketing.

Matthias: It predicts our demand forecasting.

Reg: Right. Fine. But apart from automating customer service, writing emails, analysing data in minutes, personalising marketing, and predicting demand, what has AI ever done for us?

(pause)

Xerxes: It helped us redesign the entire customer journey.

Stan: And it restructured how our teams make decisions.

Matthias: And it changed who we hire and why.

Reg: Oh. Well. But apart from automating customer service, writing emails, analysing data, personalising marketing, predicting demand, redesigning the customer journey, restructuring decision-making, and changing our entire talent strategy, what has AI ever done for us?

Xerxes: It made us question whether our company strategy even makes sense anymore.

Stan: And it exposed the fact that half our leadership team cannot explain what our strategy actually is.

Matthias: And it revealed that the people who understand the technology and the people who understand the business are not, in fact, the same people.

(long pause)

Reg: All right. Fine. Apart from automating customer service, writing emails, analysing data, personalising marketing, predicting demand, redesigning the customer journey, restructuring decision-making, changing our talent strategy, exposing the gaps in our leadership, and revealing a fundamental disconnect between our technical capability and our strategic understanding, what has AI ever done for us?

Xerxes: It made us realise we need a different kind of leader.

That last line is the one worth sitting with.

Because what has actually happened in most organisations over the last two years is this: AI arrived, and the default response was to hand it to the CTO. It was filed under “technology initiative.” It was budgeted as a line item. It was piloted, tested, and occasionally demonstrated at board meetings with the energy of a proud parent at a school play. The board nodded. The CTO presented. The pilot was declared a success.

And then nothing much changed.

Not because the technology failed. The technology worked. It worked brilliantly. It failed because the organisation did not know what to do with a technology that is not, at its core, a technology problem.

AI Is a Human Strategy

Let me say that again, because it is the point that most organisations are still missing: AI is not a technology strategy. It is a human strategy.

It changes how people think. It changes how decisions are made. It changes what “competence” means inside an organisation. It changes the relationship between the person and the process. It changes what “knowing something” is worth when a machine can produce the same output in seconds. It changes the psychology of expertise, the economics of judgement, and the architecture of trust within teams.

None of those are technology problems. Every single one of them is a leadership problem.

And yet look at where AI sits in most organisations. It sits with the CTO. It is budgeted against infrastructure. It is measured by deployment metrics: how many models, how many integrations, how many users. These are the measurements of a technology project. They tell you whether the plumbing works. They tell you nothing about whether the organisation is actually becoming more capable, more adaptive, or more intelligent as a result.

Here is the uncomfortable truth that the Life of Brian sketch, if it were set in a modern boardroom, would eventually expose: the Romans built roads, aqueducts, and sanitation. But the reason Rome lasted was not the infrastructure. It was the governance, the strategy, the human systems that decided where the roads went and who they served. The infrastructure was necessary. It was not sufficient.

AI is the same. The models are the roads. The strategy is where they lead.

The Psychology of the Gap

Through the lens of the STAR Operating System, this gap between technology capability and strategic leadership is not just an organisational design problem. It is a psychological one.

Self-Determination Theory identifies three fundamental human needs: Autonomy, Competence, and Relatedness. AI disrupts all three simultaneously. Autonomy is disrupted because the system begins to shape decisions that were previously made by human judgement alone. Competence is disrupted because the definition of “being good at your job” is being rewritten in real time. Relatedness is disrupted because the social dynamics of teams change when a non-human participant becomes part of the workflow.

When these needs are disrupted without deliberate leadership, the result is not adaptation. It is anxiety. People do not resist AI because they are Luddites. They resist it because their psychological operating system is detecting a threat to their core needs, and nobody has given them a framework for processing that threat.

Dual Process Theory adds another layer. AI operates on System 1, the fast, intuitive processor, before System 2, the slow, analytical processor, even knows it needs to evaluate. When an AI system delivers a recommendation that repeatedly “gets it right,” trust forms pre-reflectively. The person does not think, “I have assessed this system’s output and concluded it is sound.” They feel it. And once that feeling is established, System 2 stops auditing. The decision was made before the decision was made.

This is not a technology problem. This is a cognitive architecture problem. And it requires a leader who understands both the technology and the psychology, not one or the other.

The Missing Middle

Here is the gap nobody is talking about, and it is a gap that most organisations cannot close from the inside.

The CTO understands the technology but cannot translate it into commercial reality. The CEO understands the business but cannot interrogate the technology. The board understands the opportunity but cannot distinguish between genuine strategic capability and an expensive demonstration. And in the middle, where translation should happen, there is a vacuum.

This vacuum is not easily solved through a permanent hire. The skills required are too rare, the need is too urgent, and the combination of strategic fluency and technological depth does not exist in most talent pipelines. For some organisations, this will become a permanent senior role. For most, it will start as a fractional engagement, two days a week, embedded alongside the leadership team, building the capability while the organisation learns to sustain it. Whether that engagement is full-time and fixed-term or part-time and ongoing, the principle is the same: someone who charts the course while the organisation develops the muscle to hold it.

Enter the Forward Deployed Engineer, a role that has risen in prominence precisely because this vacuum exists. The FDE sits inside the client, understands their problems, and builds solutions in real time. They are not selling. They are not consulting. They are translating between what the technology can do and what the organisation actually needs. This is valuable work, and it is growing for good reason.

But the FDE operates at the implementation layer. They build the thing. They ship the thing. What is missing is the strategic layer above them, the person who can chart the course, who understands both the psychology of the organisation and the trajectory of the technology, and who can hold the C-suite accountable for decisions that will determine whether AI becomes a genuine competitive advantage or just another expensive pilot that never scales.

I am going to call this role the Forward Deployed Strategic Partner.

It barely exists yet. And the organisations that figure out they need it first will have a significant head start.

What the Forward Deployed Strategic Partner Actually Does

The Forward Deployed Strategic Partner is not a traditional consultant. Traditional consultants produce reports, deliver a presentation, and send an invoice. The FDS embeds inside the organisation, works alongside the leadership team, and leaves behind a capability that did not exist before they arrived. Whether the engagement is permanent or interim, the value is the same: someone who can hold the C-suite accountable for decisions that will shape the organisation’s trajectory for years.

They are tech-savvy, not in the sense that they can write code, but in the sense that they can interrogate an architecture, challenge an assumption about model capability, and distinguish between a genuine technical constraint and a failure of imagination. They operate at C-Suite level, not in the sense that they need a corner office, but in the sense that they can sit across from a CEO and a CTO simultaneously and translate between the two without losing either.

They understand behavioural science. Not as an academic exercise, but as a practical tool for designing organisations that can actually absorb AI into their decision-making culture. They understand that deploying AI without understanding how it changes human cognition is like installing a road system without understanding where people need to go.

And critically, they understand implementation as a sustained capability rather than a one-off project. They do not arrive to diagnose and depart. They arrive to deploy, decide, and build the organisational muscle that will sustain the work long after the engagement ends. This is the third point, and it may be the most important.

The Long Game: Implementation as a Muscle

Here is what separates the organisations that will genuinely benefit from AI from the ones that will merely spend money on it: the winners will treat implementation as a muscle, not a moment.

A pilot is a moment. A deployment is a moment. A board presentation is a moment. But the ongoing work of integrating AI into decision-making, retraining teams, redesigning workflows, auditing outcomes, and iterating on what works, that is not a moment. That is a discipline. And disciplines require sustained leadership, not just initial enthusiasm.

Most organisations are still in the “moment” phase. They have piloted something. They have deployed something. They have declared victory. And now they are wondering why the transformation they promised has not materialised.

The transformation has not materialised because they treated the deployment as the destination. It is not. It is the starting line.

The organisations that will win are the ones that build an implementation muscle, a permanent capability for absorbing AI into their operating system, iterating on what works, discarding what does not, and continuously developing the human infrastructure to support it. This requires a different kind of leadership than the one that got them to the pilot stage. It requires someone who understands that AI is not a technology project with a completion date. It is a permanent shift in how the organisation thinks, decides, and operates.

It requires a Forward Deployed Strategic Partner. Or at the very least, a leadership team that has started asking the right questions.

The Questions That Matter

So what has AI ever done for us?

It has revealed, with uncomfortable clarity, that the technology has outrun the leadership. That the people who can build are not the same as the people who can lead. That the companies which treat AI as a human strategy, a decision-making strategy, a talent strategy, will outperform those that treat it as a procurement exercise.

It has exposed the gap between the CTO who can deploy and the CEO who can direct. It has created a role, the Forward Deployed Strategic Partner, that most organisations do not know they need yet. And it has made clear that the long-term differentiator will not be who had the best models, but who built the best implementation muscle.

The Romans built roads. But what made Rome was where those roads led, who decided where they went, and how the organisation behind them adapted to the world they created.

AI is the road. The question is who is charting the course.

And in most organisations, that person does not exist yet.

Now. What has AI ever done for us?

Everything. The question is whether we have the leadership to make it count.

David Chadderton spent his twenties and thirties teaching people how to make life-or-death decisions at forty thousand feet. He now applies the same principles to consumer psychology, which, depending on the brief, can feel equally high-stakes. He’s the creator of the STAR Framework and the author of The STAR Framework: Rewriting the Rules of Consumer Engagement (NYC Big Book Award 2025), The STAR Operating System: Decode Mindset, Understand Motivation, Transform Human Behaviour, and Dear Algorithm, It’s Not Me, It’s You. By day, a Chief Marketing Officer. By night, a behavioural science obsessive who writes The Unoptimised Human because he can’t stop thinking about why people do what they do.