The short answer.

A head of operations should own the company’s AI plan and spend the first month on four moves: map where work passes from one team to another, get two decisions from the CEO, get one owner and one piece of work from each team lead, and hand the building of workflows to those owners. The head of operations runs the plan, not every workflow.

Owning the plan is the first of three steps: plan it, develop the workflows, deploy them. Who should own AI in a company your size? explains why one named person owns the plan. This piece is for the person who has just become that owner and needs to know what to do on Monday.

Why the head of operations is the natural owner.

The head of operations is the natural owner of the AI plan because the head of operations already sees work move between teams. The head of operations knows where a new order waits for finance, where a client request bounces between two teams, and which report three people rebuild by hand every month.

That view is exactly what an AI plan needs. The best first workflows often sit where one team hands work to another, and a team lead looking only at their own team does not see the handoff. After years of experimenting, most companies have AI use in every team and a plan in none. The head of operations is the person placed to turn that undirected use into directed work.

What to do first: map the handoffs.

The first thing a head of operations does about AI is list every place where work passes from one team to another. Write each handoff as one line: which team sends, which team receives, what is handed over, and where it waits.

  • Sending team.The team that finishes a piece of work and passes it on.
  • Receiving team.The team that picks the work up next.
  • What is handed over.A record, a form, a file, an email, a conversation.
  • Where it waits or gets redone.The point where the receiving team chases, corrects or re-keys what arrived.

Keep the map to one page. The handoffs where work waits or gets redone are the shortlist for the first workflows across teams, and they are the part of the plan only the head of operations can write.

What to ask of the CEO.

A head of operations asks the CEO for two decisions and one commitment, and nothing more. The CEO sets direction; the head of operations runs the plan.

  1. Where the company is going.One or two sentences on what AI is for this year, in terms of the work: every candidate placed faster, every invoice right the first time. The plan ranks work against this line.
  2. Who owns the plan.The CEO names the head of operations as owner, in front of the leadership team, so team leads know whose page it is.
  3. A monthly read.The CEO reads the monthly page and settles the decisions on it: an order of work two teams disagree on, a budget question, a team lead who has no room.

Do not ask the CEO to pick tools or approve each workflow.

What to ask of each team lead.

A head of operations asks each team lead for one owner, one piece of work and one honest answer about time. Ask in a one-to-one, before anything is written.

  • One owner, by name.The person on the team who will keep the first workflow current and decide when it changes. Often the lead; sometimes the person who does the work best.
  • One piece of work.The piece of work the team repeats most, starting from records someone can export.
  • One answer about time.Whether the team has room this quarter. “Not now” is a useful answer: it sets the order.

What to ask each team lead about AI gives the full set of questions for that conversation.

What to keep off your own desk.

A head of operations keeps the building, testing and daily running of workflows off their own desk. Those belong to the owner inside each team, who knows the work.

  • Writing every workflow.The team owner writes down how the work is done. The head of operations checks that it is on the plan and owned.
  • Answering every AI question.Questions about a workflow go to its owner. Questions about accounts and access go to whoever runs IT.
  • Approving each use.The plan sets the rules once. A team lead does not need permission to run a workflow that is on the plan.
  • Choosing every assistant.Most companies already pay for ChatGPT, Claude, Copilot or Gemini. Use what you have.

What stays on the desk: the plan, the order of work between teams, the handoff map and the monthly review. How to run a monthly AI review covers that meeting.

A first-month checklist to copy.

Copy this list for your first month as owner.

  1. Handoff map.One page, one line per handoff between teams, with where work waits marked.
  2. Direction from the CEO.One or two sentences, written down: ____________
  3. Owner named.The CEO has named you as owner to the leadership team. Date: ______
  4. One-to-ones held.One per team lead. For each: owner ______, piece of work ______, room this quarter yes / not now.
  5. First workflows chosen.One per team that has room, and no more than two or three across the company.
  6. One handoff on the plan.The handoff where work waits most, with a sending owner and a receiving owner.
  7. Monthly review in the diary.Same day each month, owners of each workflow invited.
  8. Off my desk.Three things you have handed to someone else, with their names.

A staffing agency’s head of operations takes the plan.

Take a 120-person staffing agency with five teams: business development, recruiting, candidate compliance, payroll and billing, and account management. The CEO named the head of operations as owner of the AI plan.

Illustrative example.

  • The handoff map.The head of operations listed every handoff. Two stood out: recruiting passes each placed candidate to compliance, which chases missing documents by email; and timesheets pass from account management to payroll and billing, where they are corrected by hand before invoices go out.
  • The CEO’s direction.“Every placed candidate starts on the agreed day, and every client invoice is right the first time.”
  • The team leads.Compliance named its senior coordinator as owner and chose the new-starter document check. Payroll and billing named its supervisor and chose the weekly timesheet review. Recruiting said “not now” during its busy season and went on the plan for next quarter.
  • The handoff on the plan.The placement handoff from recruiting to compliance, with an owner on each side, so a new starter’s documents are requested once, in full, the day the placement is confirmed.
  • What stayed off the desk.The compliance coordinator and the payroll supervisor each develop their own workflow, starting from a free workflow template in the Workflows Directory. The head of operations holds the plan and runs the monthly review.

Each workflow runs in the agency’s own assistant, and a person decides at every step: the coordinator approves each document request, the supervisor every timesheet.

What is different in a company of under 200 people.

In a company of under 200 people, the head of operations owns the AI plan alongside a full day job, so the plan has to fit on one page and one monthly review. You do it yourself, with leads you know by name.

  • You may be the whole operations team.Put your own repeating work on the plan as a team of one. It often has the most handoffs in the company.
  • The handoff map fits on one page.Five or six teams have a short list of handoffs, so you see all of them at once.

Take the plan and start with the handoffs. FullyPowered Planner is where the plan lives: you set out your teams, their roles and the work between them, choose what to build first, and each team lead adds their own team. How organizations plan their use of AI covers the whole method, and we develop workflows with your owners in a 3-Day Workflow Sprint when you want the first one built with you.