AI Adoption Lead Job Description

I have sat in briefs where the title meant “train the staff on Copilot.” Briefs where it meant “change how HR and the frontline work.” Briefs where it was a Head of AI in disguise. Those are three searches. Publish one JD for all three and you will meet confident talkers, not operators. Same problem I keep hitting on how to hire an AI Lead without getting it wrong: the title is doing too much work.

If the pain is “nothing in production,” you need an AI engineer, not this role. If the pain is “we bought the licences and nothing moved,” keep reading. Almost everyone has the tools. Almost nobody has changed how they work — I wrote that about agencies in Yes, AI Can Do About 80 Per Cent of My Job. It is the same pattern inside the business.

What the role actually is

An AI Adoption Lead sits between the technology and the people who have to use it on a Tuesday. They do not train the foundation model. They do not own the architecture. They pick a named workflow — onboarding, rostering, merchandising, case management — and they make the change livable.

That is adoption. It is not awareness. The wider version of that problem is in AI adoption in Australia. And if what you really need is someone to orchestrate the whole function, that is closer to the role nobody’s hiring for yet than to a trainer with a nicer title.

Purpose
Lead the design, test and rollout of AI into named workflows so adoption is measurable — not a training-completion stat.

Outcomes worth putting in the JD

• Two to three priority workflows live in six months
• Frontline, HR or ops using the tool weekly, not once at launch
• A feedback loop into product, data and risk
• Managers who can explain the “why” without your slide pack

Responsibilities
Map the current workflow before anyone touches a tool. Run pilots with real users, not a steering committee. Write the playbooks, prompts, guardrails and fallbacks people will actually follow. Partner with WHS, legal, data and comms. Coach line managers — adoption dies when they have not changed how they run the week. Kill tools that do not earn their place.

You are not the Head of AI, the prompt intern, or IT’s ticket queue.

Experience that predicts success
Taken a tool from pilot to habit in a messy environment — retail, HR, contact centre, operations. Can sit with a store manager or an HRBP and not speak in frameworks. Enough AI literacy to challenge a vendor. Not enough ego to pretend they are the engineer. Change or operations beats a pure data-science CV for this seat. If you want the map of what sits around this role, use AI Roles Explained.

Reporting line
Say it. CPO, COO, CIO or Head of AI. Dual lines are how these roles stall.

Treat pay as specialist enablement, not junior L&D. Under-price it and you hire a trainer. Over-title it as Head of AI and you hire someone who wants a team of ten. Nearby briefs are on AI job listings, including the HR & AI Adoption Consultant profile.

Send the JD before it goes to market. Ten minutes on scope saves three weeks of the wrong shortlist. Candidates can register here. “I help HR and retail teams actually use AI” will always beat “passionate about transformation.”

‍

‍