6 min read AI Process Improvement People

How to Hire for AI Transformation Success

The Clarity Question

Your organisation needs AI transformation leadership.

The question isn’t whether you need this capability. It’s which capability you actually need.

Strategic direction? Technical building? Business translation?

These are three fundamentally different roles.

The Standards Tell You Something

Microsoft’s AI Transformation Leader certification explicitly states candidates are “not expected to write any code”. Google’s Generative AI Leader path is designed “for anyone with or without hands-on technical experience”.

Meanwhile, real job postings ask for “Evangelise AI and be the public face for the business, set governance and strategy, capture business user needs, AND have the ability to prototype and pilot new AI-enabled service models.”

That’s not one role. That’s three different jobs.

Why This Matters Now

Only 1% of AI deployments reach “mature” status. 42% of firms abandoned most AI initiatives in 2025—up from 17% the year before. 63% of AI leaders are planning to leave within the year.

And 70% of AI adoption challenges stem from people and process, not technology.

Getting the hire right transforms these numbers.

Three Viable Approaches

The Strategic Transformation Leader shapes policy, manages stakeholder engagement, and directs development teams.

This person doesn’t write code. They create the conditions for technical teams to succeed.

They need: executive sponsorship, budget authority, a development team to direct, and change management resources.

The AI Engineer builds solutions, prototypes capabilities, and deploys working systems.

This person needs: clear strategic direction, access to quality data, technical infrastructure, and business context for what they’re building.

The Paired Leadership Model combines strategic and technical expertise in two complementary roles. Strategic Leader + AI Engineer working as partners. This is the Navigator and Shipbuilder partnership in practice.

This approach costs more upfront and delivers better outcomes because neither person is stretched across incompatible skill sets.

Define Success Before You Define The Role

A Head of Operations trying to hire their first AI transformation lead starts with the business case.

What does success actually look like in 6 months? In 12 months?

Then works backwards: what ecosystem does this person need to achieve it?

Data quality and access? Technical resources? Budget authority? Developer support? Change management team? Executive sponsorship?

If the business case promises enterprise-wide transformation and you’re resourcing one hire with no support structure, something needs to change.

Either expand the ecosystem or right-size the ambition (this isn’t pessimism. It’s scoping.)

Why Not Product Managers or Business Analysts?

You wouldn’t change out your ERP system with one person. You’d assemble a team: project managers, business analysts, process engineers, trainers, change managers, technical specialists.

So why is AI transformation different?

Because AI is new and unproven, and because your employees are already using it.

Shadow AI is everywhere. The Marketing Manager is using ChatGPT to draft campaign briefs. The Finance Analyst is using Claude to reconcile spreadsheets. The Head of Sales is using AI to summarise call transcripts.

They’ve identified their own use cases. They’ve already done the discovery work.

What they haven’t done is connect these isolated experiments into anything systematic. (You do have someone coordinating this, right?)

Start Where The Work Already Is

A strategic leader who can build relationships identifies where AI is already delivering value in your organisation.

They find the Finance Analyst who’s cut reconciliation time by 40%. They talk to the Marketing Manager who’s maintaining brand voice while producing twice the content. They document what’s actually working.

Then they pair with an engineer to test whether these isolated wins can scale.

Can the Finance Analyst’s prompt become a tool the entire team uses? Can the Marketing Manager’s approach work across all campaigns? Does it hold up when 50 people are using it instead of three?

Some experiments will scale. Some won’t. You need both the strategic leader to identify the opportunities and the engineer to validate whether they’re technically sound.

The Business Case Should Acknowledge Scale

Your first hire (or first pairing) proves the concept.

They find the high-value use cases. They build the first working solutions. They demonstrate ROI.

And your business case should explicitly state that success means growing the team.

When you’ve validated three high-impact use cases, you’ll need process engineers to embed them into workflows. When you’re rolling out organisation-wide, you’ll need change managers. When you’re maintaining production systems, you’ll need technical support.

This isn’t scope creep. It’s honest scoping.

The alternative is hiring one person, proving AI (sort of) works, then wondering why adoption stalls when they’re the only one who knows how anything works.

The Ecosystem Creates The Role

If you can provide executive sponsorship, budget authority, and a development team: hire for strategic leadership.

Someone who can shape policy, manage change, and direct technical work without personally writing code.

If you have strategic direction sorted, and need solutions built: hire for technical capability.

Someone who can prototype, deploy, and iterate. Give them clear requirements and the infrastructure to deliver.

If you’re building something genuinely novel: consider the paired approach. Strategic + Technical partnership from day one.

What Candidates Should Ask

If you’re interviewing for an AI transformation role, these questions tell you whether the organisation has thought this through:

  • What will success look like in 6 months? In 12 months?

  • What ecosystem exists to support this work? Data access, technical resources, budget authority, developer support, change management capability, executive sponsorship?

  • Who else is working on AI transformation, and how does this role connect to their work?

  • What happens when we prove this works? Is there commitment to scale the team?

If they can’t answer these questions with specificity, that tells you something about readiness.

The Craft of Getting This Right

AI transformation isn’t failing because organisations lack ambition.

It’s failing because they’re asking one person to fill three different capability gaps simultaneously, then providing no ecosystem to support any of them.

The fix isn’t complicated.

Define what you actually need. Resource it properly. Stop conflating strategic leadership with technical building with business translation.

Microsoft and Google have already told you which roles need code. Listen to them.

Match your hire to your ecosystem. Match your ecosystem to your ambition. Acknowledge in your business case that proving it works means building out the team to scale it.

Watch how much faster you move when everyone knows what they’re actually supposed to be doing.

What’s your experience? Does role clarity accelerate AI transformation, or am I overestimating its importance?

Related reading: Ideas Were Never the Bottleneck widens the question: once articulation is the gate, the talent pool you can hire from has just multiplied.