AI implementation lead

All US firms, nationally representative; reference period Nov 2025 - Jan 2026. 18% firm-weighted, 32% employment-weighted, expected to reach 22% within six months; 50-60% (60-70% employment-weighted) for very large firms in Information, Professional Services and Finance. Among adopters, the most common functions are Sales and Marketing 52%, Strategy and Business Development 45%, IT 41%. This is a count of firms, not of occupations or of people: it says where AI entered a company, never which roles changed. Two further cautions the authors state themselves - the survey questions were revised between supplements, and 23% of firms report workers using AI in tasks against 18% firm-level adoption, so some use is arriving without a company decision at all.

An employer has put it into production. Can move the baseline — weighted by scale and how similar the setting is.

Canada, federal institutions. The directive says the assistant deputy minister responsible for the program using an automated decision system, or another senior official named by the deputy head, is responsible for documenting client feedback, unexpected impacts, human overrides and system failures; for using those findings to identify issues and take corrective action; and for informing clients of recourse options to challenge the decision. Federal administrative decisions only; the responsible person is a senior official, not necessarily whoever implemented the system.

Failure, rollback, regulation or cost is suppressing adoption. Can lower an assessment or widen its uncertainty.

Mainland China, and the occupational classification only. The ministry's stated reason is that as large models spread across industries, 'the number of practitioners is growing rapidly and the range of posts is becoming more varied' — that is the authority of record saying this work now exists at classifiable scale, and it is the whole of what this record establishes. It gives no headcount, no wages and no employer names. It is a 公示 (public notice for comment): at this date the categories were proposed, not yet written into the national occupational catalogue, and a national occupational standard was still to be drafted.

Verifiable change in hiring, headcount, hours or job scope. Highest weight — but causal attribution still has to be argued, not assumed.

The United States federal executive branch only, not private employers. What it establishes is that this role is required to exist by rule rather than created at each organisation's discretion. Three things need saying. First, the memorandum rescinds and replaces 2024's M-24-10 and deliberately redefines the role: it describes the Chief AI Officer as a champion of the agency's AI goals who promotes AI innovation, adoption and governance, so this record supports a role that leans towards driving adoption while keeping governance duties. Second, it requires an agency to identify an officer — not a headcount, a budget or a team; an agency may name its existing chief information officer. Third, a rule requiring a post to exist and that post actually doing the work are two different layers, and this site records it at the policy layer, where one record changes no task judgement on its own.

Regulation, subsidy or public procurement is requiring or funding adoption — the mirror of a constraint. It shows adoption is being required, not that it has happened, so one mandate is never enough on its own; two independent ones are.

The EU, and only for deployers of high-risk AI systems — the companies that buy and use them, not the providers that build them. What it establishes is that giving a specific person the competence, training, authority and support to oversee such a system is a legal obligation in the EU rather than a management choice; Article 26 also requires deployers to monitor operation and, on finding a risk, to inform the provider and the market surveillance authority. Regulation (EU) 2026/1744 (the Digital Omnibus on AI, published 24 July 2026) moved the application of these obligations from 2 August 2026 to 2 December 2027 for systems that are high-risk under Annex III, and to 2 August 2028 for those that are high-risk under Article 6(1) and Annex I; so this is a rule on the books that does not yet apply. The law does not say who that person must be and does not require a dedicated post — a company may spread the duty across function heads. Attaching it to this occupation is our inference about where it lands in practice.

Regulation, subsidy or public procurement is requiring or funding adoption — the mirror of a constraint. It shows adoption is being required, not that it has happened, so one mandate is never enough on its own; two independent ones are.

There is no established path into this job, which cuts both ways: nobody can say you are unqualified, and nobody can tell you what qualifies you. What people are actually hired on is evidence that they have made one thing land end to end in a real organisation — a before number, an after number, and an honest account of what broke. One such story beats any certificate, and certificates are what most of the market is selling.

Your leverage is that you know where this company's work actually breaks, which no vendor and no model has. The risk is structural rather than technical: this function is funded as a transition cost, and transition budgets end. The people who stay are the ones who moved from running the programme to owning a number the business already cares about.

Stay and strengthen

Attach yourself to a number that predates you

Programme budgets get cut in the year after the excitement. A function measured on cycle time, conversion or cost per order is measured on something the business cared about before AI arrived and will care about after.

Reshape the role

Write down the boundary nobody has written

In most companies what the tools may do unsupervised has been decided by default, by whoever configured them. Turning that into a written, agreed policy is unglamorous, it is the thing that prevents the incident, and it is a deliverable with your name on it.

Adjacent move

Move into the function you were helping

You have spent a year learning how one function actually works, in more detail than most people in it. Operations, finance and customer service all now need someone who understands both the work and the systems, and those seats are permanent in a way a transformation programme is not.

Cross-industry

Do it from the outside, for many companies

The pattern knowledge you build — which sequence works, where pilots die, what the second year looks like — is worth more across ten companies than inside one, and most companies will never hire a full-time version of this role.

Both, and which one it is at a given company is worth checking before you take it. It is a real job where it owns a budget and a number the business already tracked. It is a title where it owns a programme, a tool inventory and a steering meeting. The second version is funded as a transition cost, and transition costs end.

This role's clock is different from every other page on this site: the risk is not that a machine does it, it is that the transition finishes and the function dissolves back into the departments it was helping. The signal is where your budget line sits. If it is a project or programme line, ask each year whether it renewed and by how much. If it moved into a department's operating budget, the job has become permanent — and that move, not any announcement, is the thing to watch.

Enough to tell a real evaluation from a demo, and to know when a vendor's answer is evasive. Beyond that, the scarce input is knowledge of this company — which step is the real bottleneck, whose numbers move, who will resist — and that is collected by walking around, not by reading documentation. The common failure is a technically strong lead who automates the step that was easiest to automate rather than the one that mattered.

Because the index measures how much of the work automation is taking over, and almost none of this job's work is. That is not the same as safe, and the page says so on every task: this role exists because a transition is under way. Read the low number as a description of the work, not as a promise about the headcount — those are different questions, and this site keeps them apart on purpose.

Ask for one thing: a case where it did not work, and what they did next. Anyone who has actually put tools into a working business has that story, because the first attempt usually fails on something nobody predicted. A vendor who only has successes has either not shipped or is not telling you about the part you most need to hear.