In short
- Three things need an owner: each AI-supported process, the upkeep of the AI set-up, and risk.
- In a small firm one person holds all three. In a large one they are separate roles.
- Companies that report the largest gains from AI also report senior leaders who own it.
- The harder problems are human: fear, hidden knowledge, and lost ways of learning the job.
For the definition of AI-first, see the guide.
Three responsibilities
Whatever the organization chart looks like, three jobs have to be done by someone.
- Own each process end to end. One person answers for the result of a process that AI supports, including the parts the AI does.
- Keep the AI set-up working. Prompts, settings and connections between systems need upkeep as tools change.
- Answer for risk and compliance. Someone has to know which AI systems are in use, what data goes into them, and which rules apply.
Structure by company size
| Size | Typical set-up |
|---|---|
| Micro and small (1–49) | The owner or one manager holds all three responsibilities. No new roles. |
| Medium (50–249) | One named owner for AI, usually an operations or IT lead with set time and a budget. Rarely a data-science team. |
| Mid-market (250–999) | An executive owner and a small steering group. AI leads inside business units, backed by a central team for shared tools, data and governance. |
| Enterprise (1,000+) | Separate roles for process ownership, upkeep, and risk, often in a central team. |
See name one accountable AI owner for the steps.
What leaders do
In McKinsey’s 2025 survey of 1,993 respondents, about 6% of organizations credited AI with 5% or more of operating profit. They were three times more likely than others to strongly agree that senior leaders show ownership of and commitment to AI. Their leaders were also more likely to use AI themselves.
It is the most consistent pattern in the survey data: where AI is left to the IT department, results are weaker.
Leaders’ own use is not enough, though. In a survey of 179 leaders in Poland, 83% used AI daily, while about 70% of their organizations had not moved beyond pilots.
The people side
Structure is the easier part. Three human problems have evidence behind them.
- Fear closes people down. AI adoption has been linked to lower psychological safety, and fear of job loss to staff hiding what they know. See protect psychological safety during a rollout.
- Juniors can lose their way to learn. When AI takes the routine work, newcomers may lose the practice that makes them experts. See keep the entry-level tasks that newcomers learn on.
- A person plus AI is not always best. Who does what should be tested by task. See check by task type.
Where this may be heading
Microsoft’s 2025 Work Trend Index describes three phases. First, AI assists each employee. Then AI agents join teams and take on specific tasks. Finally, people set direction for agents that run whole processes (Microsoft).
It is useful as a map of where the three responsibilities above will grow: more processes to own, more set-up to maintain, more risk to answer for.
Practices
Practices on ownership and on people. What to do first comes first.
- Protect psychological safety during an AI rollout AI projects can make staff afraid to speak up and unwilling to share what they know. Say early what AI means for jobs, and consult the people affected. Do first · Effort: medium (weeks, a few people)
- Keep a person checking anything that goes to a customer or carries legal weight Before AI output leaves the company or is relied on in a decision, a named person checks it against real sources and signs it off. Make the check a step in the process, with time allowed for it. Do first · Effort: medium (weeks, a few people)
- Train staff on the tools you actually chose Show every user what your chosen AI tool is, where it goes wrong, and what they must check. Use your own tasks and your own rules, give people time to practise, and include temporary staff. Do first · Effort: medium (weeks, a few people)
- Know the rules that already apply to your AI use Most of the rules that bind your use of AI are not AI laws. You answer for what your AI says and does under the consumer, privacy, advertising and professional rules you already follow. List your AI uses and match each to its rules. Do first · Effort: low (days, one person)
- Name one accountable AI owner Give one named senior person the responsibility for AI: priorities, budget, risk and results. Shared responsibility tends to mean nobody decides. Do first · Effort: low (days, one person)
- Write a one-page AI-use policy staff will actually read Put the rules for AI on one page: which tools are allowed, what must never be typed in, who checks the output, and who to ask. Then build the most important rule into the work itself, because a page alone gets ignored. Do first · Effort: low (days, one person)
- Test AI knowledge instead of asking staff to rate their own People judge their own skills poorly. To find out what your staff know about AI, use a short knowledge test or a second opinion, not only a self-rating. Do next · Effort: medium (weeks, a few people)
- Claim only what your AI has been tested to do If you tell customers that your product or service uses AI, or how well it works, hold the evidence before you say it. Regulators treat “AI-powered” and “98% accurate” as factual claims like any other. Do next · Effort: low (days, one person)
- Give AI assistance to newer staff first When you roll out an AI assistant for a well-defined task, start with your less experienced people. Studies find they gain the most. Do next · Effort: low (days, one person)
- When AI output goes wrong, correct it fast and in the open Decide now what happens when an AI error gets out: who is told, who withdraws or corrects the work, and who checks how far the problem goes. In the documented cases, firms that owned up quickly were treated far better than firms that defended the error. Do next · Effort: low (days, one person)
- Check AI advice on money, tax and law before you act on it When you use an AI tool as an adviser, check its advice on money, tax and law against a reliable source or a professional before you act. In a small firm, nobody else will catch a wrong answer. Do next · Effort: low (days, one person)
- Set the limits before the tool acts Before an AI tool sets a price, sends a message or takes a step for you, write down what it must never do, how far it may go, and what needs a person. Build those limits into the tool, then test inside them. Do next · Effort: low (days, one person)
- Check now and then what staff can do without the AI On a sample of cases, have people do the work without the AI and compare the result with their usual work. Start with the people who check AI output and the people still learning the job, and set the tools that learners use to give hints, not answers. Do later · Effort: medium (weeks, a few people)
- Keep the entry-level tasks that newcomers learn on Before you automate routine work, check whether it is how juniors learn the job. If it is, keep some of it for them, or replace the learning another way. Do later · Effort: medium (weeks, a few people)