What is the hardest part of moving from COO to CEO?

The guides name delegation and the shift toward the board and external stakeholders. Kaykas-Wolff adds a mechanical cause: the operating systems and AI agents a COO built still escalate to that person after the promotion, so the new CEO keeps doing the old job by default.

What should a COO do with their AI agents when promoted to CEO?

Sort every agent by whose job it serves, name an owner other than the new CEO for each operating agent, re-sign the delegation matrix with those names, change escalation targets the same week, and retire agents that only made sense for the old job. Kaykas-Wolff recommends doing this between the board decision and the announcement.

What should a board ask a new CEO who was promoted from COO?

At the first board meeting the new CEO runs, ask which agents still escalate to them and which of those belong to someone else. A long list means the transition has not really happened yet.

How can a COO prepare for the CEO role before a promotion?

Write a register of everything the COO has automated, with a second named person next to each agent who could own or pause it. Kaykas-Wolff calls it the most useful succession document a COO will produce, whether or not the promotion comes.

COO to CEO Transition: Hand Off the Agents You Built as COO

I have made this move once. I joined Visiting Media as chief operating officer in May 2024 and the board made me CEO that November. Before that I spent four years as president and COO of Lytics, so most of my recent working life has been in the second chair, with a short and very recent stretch in the first.

The pages that rank for this transition mostly agree with each other. Baringa tells the aspiring CEO to build financial fluency and find the courage to delegate. An essay in Corporate Board Member describes the shift as moving from participation to ownership, because there is no longer anyone above you to check in with, and it notes that most COOs stay effective in the role for three to five years before it starts to work against them. Nearly all of them say to groom your own successor early.

I agree with all of it. The advice assumes the COO’s operating system is made of people and spreadsheets.

What a COO actually builds

A good COO builds machinery. The weekly metrics review and the escalation paths are what keep a company running on a Thursday afternoon when nobody senior is paying attention. More and more of that machinery is now software that acts on its own: agents that reconcile the pipeline, chase overdue approvals, draft the Monday operating summary and decide who gets paged at night.

Whoever builds those agents tends to own them. When I wrote about CEO succession planning for an agent fleet, the uncomfortable finding was how often my own name sat in the owner column of the register. A COO who automates the job ends up as the human in the loop for most of it.

Then the board promotes you.

The agents don’t get the memo

On your first day as CEO the title changes and almost nothing else does. Every escalation path still ends at your phone. The pipeline agent still sends you its exceptions, the approval chaser still treats you as the approver because six months ago you were, and the delegation matrix you signed as COO still names the COO, who is now you, sitting in a different chair and reading the same alerts.

That is the mechanism behind the failure every guide warns about. They describe the new CEO who can’t stop running operations as a personality problem, a control habit to be coached away. Some of it is. Much of it is plumbing. If the operational exceptions land in front of you every morning, you will act on some of them, and each one you act on teaches the organization (and any agent that learns from your corrections) that you are still the operator.

Habit is hard enough to break without software reinforcing it daily.

Hand off the fleet before you hand off the title

There is usually a gap between the board deciding and the company hearing about it. Use that gap for the handoff, because once the announcement goes out your calendar fills with the outward-facing work the guides describe, and the plumbing never gets touched again. This is the order I would work in:

Sort the register by whose job each agent serves. Most agents a COO builds serve the operating role. A few serve you personally, as a person with an inbox and a calendar. Keep that second group honest and short.
Name an owner for every operating agent who is not you. Usually a VP, or whoever is acting in the operations role. If nobody fits, the agent is telling you something about the org chart that is worth hearing before the press release.
Re-sign the delegation matrix with the new names on it. Approvals route upward by default, and they will keep routing to you until a signed document says otherwise. I laid out how that matrix works in delegation of authority for AI agents.
Change the escalation targets the same week.
Retire what only made sense for the old job. Some agents existed because you, specifically, liked a certain report at a certain hour. Your successor in operations will want different ones. Shut yours down properly, with the consumers found first and the keys revoked afterward, the way I describe in retiring an AI agent.

Step four is the one people skip. The register gets updated, the matrix gets signed, and the pager still points at the new CEO for another quarter because the routing lives in a config file nobody remembered to open.

What the CEO needs from agents instead

The guides are right that the job tilts outward, toward the board and toward decisions about where the money goes. The fleet should tilt with it. Very little of what I would want from agents in the CEO seat is operational. Board preparation is the obvious one, including the quarterly page I argue belongs in every pack in the AI page in the board pack. Pre-reads for customer and partner meetings, too. And the boring, useful work of noticing when an operating number has drifted far enough that the CEO, as opposed to the COO, should care.

That last one sounds like the old job. The threshold is what changes. A COO wants to hear about a slipped deadline on Tuesday. A CEO wants to hear about the pattern of slipped deadlines in March, once whoever owns operations has already had a chance to fix it and either did or didn’t.

Rebuilding the fleet around that threshold does something coaching rarely manages: it takes the old job’s noise out of the new job’s morning entirely.

The empty COO chair

An empty COO seat with a full set of COO agents is a job someone is still doing, and the someone is probably you.

What the board should ask

Boards spend real time on the people side of a COO to CEO succession: who backfills operations and how the announcement is sequenced. I would add one question for the first board meeting the new CEO runs. Which agents still escalate to you, and which of those belong to someone else?

If the answer is a long list, the transition has not happened yet, whatever the org chart says. A director who sits on technology boards can ask that without it landing as an accusation, and it is the same kind of question I suggest in AI agent access reviews, applied to a single person at the moment their role changes.

Start the register while you are still COO

I had six months in the COO chair at Visiting Media. Lytics gave me four years. The longer stint is the one that builds habits a new CEO has to unwind, and today a lot of those habits would be running as code on a schedule, owned by the person who is about to leave the job. If you are a COO who thinks the top seat is coming, write the register of what you have automated now, with a second name next to every agent. It costs you an afternoon. It is the most useful succession document you will produce, and you will need it whether or not the promotion arrives.

This article is part of the Executive Leadership cluster, focused on board governance and the operating discipline required to run AI systems responsibly at the executive level.

From COO to CEO: The Operating Machinery Still Reports to You