Job description template

AI Enablement Lead job description

Also known as: AI Enablement Specialist, AI Productivity Lead, Head of AI Productivity or AI Capability Lead

Get people across the company using AI well on their real work, and prove it.

What the AI Enablement Lead is for

The person whose job is getting the rest of the company good at AI. Not by running the tools or writing the strategy, but by finding the work where AI genuinely helps, changing how teams do it, and showing honestly what changed.

Most companies have now bought AI licences. A few people use them brilliantly, most use them occasionally for small things, and some don't use them at all. Usage dashboards show logins, not better work, and leadership is starting to ask what they are getting for the money. Training sessions on their own produce a spike and a fade. The AI Enablement Lead exists to close that gap: someone who owns turning access into capability, team by team, on the work people actually do, with numbers a finance director would accept.

AI Enablement Lead responsibilities, stage by stage

AI enablement runs as a cycle: discover, prioritise, train, measure, scale, then round again. Here's what this role owns in each part of it.

1

Discover

  • Interview people across teams about what they actually do each week and how they already use AI, officially or not.
  • Run the maturity scorecard or a short team survey to get an honest baseline of skills, confidence and blockers.
  • Find the real blockers: unclear data rules, managers who don't protect time, tools that don't reach the systems people use.
2

Prioritise

  • Turn the pile of 'we could use AI for that' into a scored list of specific, recurring workflows.
  • Choose three to start: one quick win, one high-frequency workflow and one leadership will notice.
  • Baseline each workflow (time per instance, volume, an existing quality signal) before anything changes, and write down who said so.
3

Train

  • Run live sessions on a team's real work, not generic prompt tips, including when the tool gets it wrong in the room.
  • Write short workflow guides and shared skills that a team can follow without the lead in the room.
  • Agree a plain, one-page usage policy with IT, security and legal so people know what they can and can't paste in.
4

Measure

  • Re-measure tracked workflows against their baselines and report hours back, quality and turnaround with sources.
  • Write a one-page progress report leadership trusts, including what didn't work.
  • Drop vanity measures (logins, prompt counts, satisfaction scores) as headline evidence.
5

Scale

  • Recruit and support a champions network so each team has a first port of call who owns its guides.
  • Take what worked in the first teams to the next ones, adapting rather than repeating.
  • Keep the library of guides and skills current, with owners and a review rhythm, so it outlasts any one person.

Skills to hire for

Must have

  • Uses AI tools daily on real work and can tell a good output from a plausible one
  • Sees work as steps with inputs, decisions and outputs, and can find where AI fits and where it doesn't
  • Has run training or workshops for non-technical people on their own work
  • Writes short, clear guides people follow and reports leadership trusts
  • Measures honestly: names sources, separates estimates from evidence, resists inflating numbers
  • Works well with IT, security and legal, and with sceptical managers

Nice to have

  • Has led a Copilot, ChatGPT Enterprise, Gemini or Claude rollout beyond the pilot
  • Change management, operations or process improvement background
  • Has built and kept alive a champions or super-user network
  • Facilitation or coaching experience
  • Experience in a regulated industry or with strict data handling rules

What good looks like

Use these to set expectations when you hire, and to check in at six and twelve months.

At six months

  • Discovery done across most teams, with a written summary leadership has read
  • Three named workflows measurably better than their baselines, with sources
  • A one-page usage policy agreed with security and legal, and actually used
  • A sponsor who has done at least one thing for the programme the lead couldn't do alone
  • The first champions recruited, with time agreed by their managers

At twelve months

  • A champions network that runs its own check-ins and sessions
  • Tracked workflows across several departments, reported quarterly with honest numbers
  • A library of current guides and shared skills, each with an owner
  • New teams onboarding from the library, not from the lead personally
  • Leadership describing the programme in terms of work that changed, not licences bought

AI Enablement Lead interview questions

Each question comes with what a strong answer sounds like. Score each answer before the panel talks, and agree your bar before the first interview.

1.Tell me about a time you changed how a team did a specific piece of work. Not a tool rollout: a piece of work.

Listen forA specific workflow, a clear before and after, what they did versus what the team did, and an honest answer to 'is it still done that way?', even if it isn't.

2.Walk me through how you used AI in your own work this week. Pick one task.

Listen forSomething specific and unglamorous, what they changed in the output, where they deliberately don't use it, and a recent failure described without embarrassment.

3.On your first day a director asks how much time AI will save the company this year. What do you say?

Listen forThey don't give a number. They explain they'd measure specific workflows first, describe how, and offer real figures from a first team soon after.

4.How would you decide whether the programme is working after six months?

Listen forOutcomes on named workflows with sources stated, and scepticism about logins, prompt counts and satisfaction scores as headline evidence.

5.Tell me about someone who really didn't want to change how they worked. What did you do?

Listen forCuriosity about the real objection, acknowledgement that the sceptic had a point, and honesty about not winning everyone over.

6.What would you deliberately not do before you've run discovery here?

Listen forSpecific restraint: no company-wide webinar, no new tool evaluations, no grand strategy deck until they've listened.

7.Our security team is nervous about AI. How would you work with them?

Listen forInvolving them early, asking what worries them, treating concerns as design constraints, and never going round them.

8.What would you need from me as your sponsor?

Listen forConcrete asks: a note to managers that makes the time legitimate, a decision on the policy, protected champion time, reading the monthly report.

Red flags

Some of these look like strengths in an interview. Ask what actually changed.

  • Talks about licences, logins and adoption percentages as success
  • Quotes confident ROI or time-saved figures from a previous role without saying where they came from
  • Has strong opinions about which AI vendor is best before asking how your teams work
  • Very impressive personal demos, but no example of changing how a team works
  • Opens with 'I'd start by training everyone'
  • Describes sceptics, security or legal as obstacles to get round
  • Can't describe a time AI got something wrong in their own work

AI Enablement Lead job description template

Copy it, then replace the [highlighted] fill-ins with your details. Or build a tailored version in the generator.

ai-enablement-lead-job-description.txt
Customise it in the generator

AI Enablement Lead, [Company]

About the role

[Company] has rolled out [tools, e.g. Microsoft Copilot / ChatGPT Enterprise / Gemini] and some of our people already use them well. Most of us don't yet, and we want to change that on the work we actually do, not in theory. As our AI Enablement Lead you'll own turning access into capability: finding where AI genuinely helps across [teams or departments], changing how those teams work, and showing honestly what changed. You'll report to [sponsor, e.g. COO] and work closely with IT, security, L&D and team managers.

What you'll do

  • Run discovery conversations across [teams] to find how people work today, how they already use AI and what's in the way
  • Choose a small number of specific, recurring workflows to improve first, and baseline them before anything changes
  • Run live sessions on teams' real work and write short workflow guides and shared skills people can follow without you
  • Agree a plain, one-page AI usage policy with IT, security and legal
  • Measure tracked workflows against their baselines and write a short, honest progress report for leadership each month or quarter
  • Recruit and support a network of AI champions so every team has a first port of call
  • Keep our library of guides and skills current, owned and reviewed

What you'll bring

  • Daily, hands-on use of AI tools on real work, and a clear sense of where they're strong and weak
  • Experience changing how a team does a specific piece of work, and evidence that it changed
  • Experience running training or workshops for non-technical people
  • Clear, short writing: guides people follow and reports leaders trust
  • An honest approach to measurement: you name your sources and don't inflate numbers
  • The judgement to work with IT, security, legal and sceptical managers rather than around them

Nice to have

  • Experience taking a [tools] rollout beyond the pilot
  • A background in operations, process improvement, change management or L&D
  • Experience building a champions or super-user network that lasted
  • Experience in [industry] or with strict data handling rules

How we'll measure success

  • Hours back, quality and turnaround on named workflows, against baselines taken before the change
  • Number of teams with at least one workflow running the new way, with a guide that has an owner
  • An active champions network that runs its own check-ins
  • A usage policy people know and follow
  • Leadership confidence in the numbers you report

Questions about the AI Enablement Lead role

What does an AI enablement lead do?

They get people across the company using AI well on their real work. In practice that means discovery conversations with teams, choosing a few specific workflows to improve, running sessions on that real work, writing guides people follow, measuring what changed against a baseline, and building a champions network so it keeps going without them.

What's the difference between an AI enablement lead and an AI champion?

An AI enablement lead is a hire whose whole job is the programme across the company. An AI champion is usually a volunteer inside one team who spends a small, agreed amount of time being the first port of call and owning that team's guides. The lead recruits and supports the champions; the champions are how the lead's work reaches every team.

Who should an AI enablement lead report to?

Whoever has authority over the teams that need to change and will genuinely sponsor the work. That's often the COO, the CIO or the Chief People Officer. Reporting into IT works when IT already has strong relationships with the business; reporting into L&D works when the programme is mostly about skills. Either way, the lead needs a sponsor who will make decisions and give managers permission to spend time on it.

Does an AI enablement lead need to be technical?

They need to be fluent, not technical. They should use AI tools daily, know where they're strong and weak, and be able to tell a good output from a plausible one. They don't need to write code or build models. Workflow thinking, teaching and honest measurement matter more than engineering skills for this role.

How is this different from an AI engineer or a data scientist?

Engineers and data scientists build AI into products and systems. The enablement lead helps people use AI tools in their everyday work. The two roles should talk, but the enablement lead's measure of success is how work changed across teams, not what was built.

Is one AI enablement lead enough?

For a while, if they build a champions network early. One person can't personally enable hundreds of people. What scales is a clear role for champions in each team, a library of guides with owners, and a small enablement team (co-leads, a champions lead, an L&D partner) as the programme grows.

Hiring one? Give them the kit from day one.

Membership is the working kit for your new AI Enablement Lead and the small enablement team around them: their co-leads, whoever runs champions, an L&D partner. The Role Book, every training deck in your brand, the impact tracker and board pack, and the team tools, under one price for your organisation.

See what's in Membership

Doing this job already?

One useful thing a week for people running AI enablement: a session outline, a survey question, a slide, a way to prove it's working.

Free weekly newsletter. One useful thing per issue. Unsubscribe in one click. Privacy.

All AI enablement roles