How Roles, Approvals and Ownership Change When AI Does the Groundwork

When AI does the groundwork, people stop producing first drafts and start setting standards, judging output and approving what goes out. Roles shift from doer to editor and owner. Approvals move to the points where work becomes hard to undo. Ownership attaches to named people for each fact, method and agent, never to the AI.

What changes in people's roles when AI does the groundwork?

People spend less time producing and more time directing and judging. A salesperson stops writing follow-ups from scratch and starts checking drafts against what the buyer said. A marketer stops drafting posts and starts deciding which are good enough. The expertise is the same; it is applied later in the process, and more often.

This is a bigger shift than it sounds. Judging a draft well takes more knowledge than writing an average one, because the reviewer has to spot what is missing as well as what is wrong. So the people whose roles change most are often the most experienced.

Juniors face a different problem. Much of the groundwork AI now does was how they learned the job. If they only ever check drafts, they may never build the judgement that checking needs.

Which new responsibilities appear?

Four responsibilities appear that most job descriptions never mention. Someone owns each set of facts, someone owns the method for each job, and someone owns each agent and its access. Someone also approves output before it takes effect. None is full-time in a growing business, but each needs a name.

The AI operating model sets out who owns each layer of the system. The point here is more personal. These duties land on people who already have full jobs, so write them into role descriptions and take something else off the list. Otherwise they get done badly, in the gaps.

Where should approvals sit when AI drafts the work?

Approval should sit where a mistake becomes hard to undo: before anything is published, sent to a customer, spent or written into a system of record. Everything earlier can be checked lightly or by script. Approving every intermediate step wastes the reviewer's attention, which is the scarcest resource in the process.

Outbound shows the pattern well. AI can build a campaign and load it paused, then a named person reads it and launches it. Loading is reversible in minutes, whereas a launched campaign has already reached inboxes. The guide to approval gates covers how to design the checkpoint itself.

Who is accountable when an agent produced the work?

The person who approved it, and behind them the person who owns the agent. Accountability cannot move to software, because software cannot answer for a decision to a customer, a regulator or a board. Every agent therefore needs a named owner, and every approval needs a name and a date.

Official guidance starts in the same place. According to the National AI Centre's Guidance for AI Adoption, the first of six essential practices is to decide who is accountable. The last is to maintain human control.

In practice, write it down. Record who approved each piece of work, and what the approval covered. "Looks good" in a chat thread is not a record; a tracker row with a name, a date and a status is. When something goes wrong, that record shows whether the process failed or a person did. Deciding who owns AI agents is the same question one level up.

How does a manager's job change?

Managers move from checking volume to checking judgement. When AI handles the groundwork, output rises fast, so counting tasks done stops meaning much. The manager's work becomes reviewing how people review, keeping methods current, and deciding which jobs AI should take next and which should stay with people.

Watch for rubber-stamping. A reviewer approving forty drafts a day will start approving without reading. So sample their approvals: pick a few each week and check them properly. If errors are getting through, the fix is fewer items per reviewer or better checks earlier, not a reminder to try harder.

Measurement changes too. According to Microsoft and LinkedIn's 2024 Work Trend Index, 59% of leaders worry about quantifying AI's productivity gains. Measure the outcomes each role exists for, such as meetings booked or reports delivered on time, rather than drafts produced.

How do you change roles without losing people's trust?

Say plainly what is changing and what is not. Rewrite role descriptions before the tools arrive, and train people for the judging work, not just the tools. People fear redesign more than tools, so silence reads as a threat. Leaders who explain the change and use the tools themselves get far better uptake.

The worry is real. BCG's AI at Work 2025 survey found employees at companies redesigning work comprehensively around AI were more worried about job security, 46% against 34%. However, the same survey found the share of employees positive about generative AI rises from 15% to 55% with strong leadership support.

Start with one role and one workflow. Agree with the people in it what the AI prepares, what they check and what they own. Then run it for a month and adjust before moving to the next team.

Skein works with leadership teams on these decisions, with a named person approving anything published, sent or spent; the AI leadership page covers how that work is run. That suits a business of 10 to 200 people whose staff already use AI on their own. A business still deciding whether AI fits at all needs a strategy conversation first.

Frequently asked questions

How does AI change job roles in a small business?

People spend less time producing first drafts and more time directing, checking and approving. A salesperson checks AI follow-ups against the call; a marketer edits and decides what publishes. The expertise stays the same, but it is applied later in the process. Experienced staff often see the biggest change, because judging well needs the most knowledge.

Who should approve AI-generated work?

The person accountable for the outcome. Content is approved by whoever owns the channel, customer messages by the sender, spending by the budget owner, and record changes by the record owner. Internal drafts and research need no approval each time, just a weekly spot check. Approve where mistakes become hard to undo, not at every step.

Who is responsible when AI makes a mistake?

The person who approved the work, and behind them the person who owns the agent or workflow. Software cannot be accountable to a customer or regulator, so responsibility stays with named people. Record who approved each piece and what the approval covered, so a mistake can be traced to the process or the person.

Will AI replace roles or change them?

In most growing businesses it changes them first. Groundwork such as drafting, research and formatting moves to AI, while judgement, relationships and approval stay with people. New duties also appear: owning facts, methods and agents. Leaders should say plainly what is changing, because uncertainty about redesign worries staff more than the tools do.

How do you stop reviewers rubber-stamping AI output?

Keep the volume each reviewer handles realistic, give them a short checklist, and sample their approvals each week by checking a few properly. If errors still get through, add automated checks earlier in the workflow or reduce the load. Reminding people to be careful does not work for long when the queue keeps growing.

Related reading