Insights — Executive Recruitment — 4 min read
CEO vs COO
The CEO/COO split fails most often not because the wrong people were hired, but because the boundary between direction and execution was never actually drawn.
In short
A CEO owns strategic direction, capital allocation, board and investor relationships and external representation. A COO owns the operational execution of that strategy — the internal machinery of delivery, process, and day-to-day performance across functions. Not every business needs a COO; almost every business of any size needs clear CEO accountability. Whether both roles exist should depend on complexity of operations, not on imitating a larger competitor's structure.
The CEO/COO relationship is one of the most frequently misunderstood pairings in senior leadership, largely because the two roles sound close but are structurally different. A CEO owns where the business is going; a COO owns how well it runs while it gets there. Confuse the two and you either duplicate a role or leave a genuine gap uncovered.
This matters more than it might appear, because a poorly drawn boundary between CEO and COO does not just create friction between two people — it creates confusion throughout the leadership team about who actually decides what.
Two different jobs, not two levels of the same job
It is tempting to think of COO as 'CEO in waiting' or a deputy. That framing causes problems. The roles are not a hierarchy of the same skillset — they require genuinely different orientations. A CEO spends disproportionate time outward and forward: markets, capital, the board, the leadership team's shape. A COO spends disproportionate time inward and present: process, delivery, cost discipline, operational risk.
| Decision area | CEO | COO |
|---|---|---|
| Overall strategic direction | Owns | Informs, executes |
| Capital allocation and investment priorities | Owns | Provides operational input |
| Board and investor relationships | Owns | Rarely involved directly |
| Cross-functional operational performance | Sets expectation | Owns |
| Process, systems and delivery discipline | Sponsors | Owns |
| External representation and market-facing profile | Owns | Rarely involved directly |
| Day-to-day leadership of operational functions | Delegates | Owns |
When a business needs both
A COO earns its place when operational complexity has genuinely outgrown what the CEO can hold alongside strategic and external responsibilities — multiple sites, multiple business units, a complex supply chain, or rapid headcount growth that requires someone dedicated to making the machine run well every day.
- The CEO is spending most of their week on operational firefighting instead of strategy, capital and the board
- The business has scaled to a size or complexity where no single person can credibly hold both direction and delivery
- The CEO's specific strength is external — capital, deals, market — and delivery needs a dedicated internal owner
- A planned CEO succession benefits from a COO who is being deliberately developed and tested
Most businesses that think they need a COO actually need their CEO to stop doing operational work that a strong leadership team, properly delegated to, should already be handling.
When it is the wrong appointment
Appointing a COO does not fix an absent strategy, an overloaded leadership team below it, or a CEO who is unwilling to let go of operational control. In each case the COO either duplicates work the CEO refuses to release, or is set up with a title that implies authority they will never actually be given.
In smaller and mid-market businesses, the practical alternative is usually a properly empowered Managing Director owning both strategy execution and operations under a CEO who is genuinely focused externally — or simply a CEO who delegates well to functional leaders without adding a layer between them.
Where the two roles collide
Friction almost always concentrates in one place: decisions that are simultaneously strategic and operational, such as a major restructuring, an acquisition integration, or a significant systems change. These require the CEO and COO to have an explicit, agreed process for who decides what, rather than working it out mid-crisis.
The reporting relationship matters as much as the split
A COO who reports to the CEO, sits on the leadership team, and is genuinely trusted with delegated authority functions very differently from a COO who reports to the CEO on paper but is expected to seek approval for everything. The second pattern produces a COO in title only, and the business does not get the operational leverage it paid for.
Succession is a legitimate reason to appoint a COO — but say so
Boards sometimes appoint a COO with an unstated intention of testing them as a future CEO. That is a defensible strategy, but it should be explicit to the individual and to the board, not left ambiguous. An unstated succession agenda distorts how the COO role is defined and how its holder is assessed.
A short test before creating a COO role
- 01Is the operational complexity genuinely beyond what a well-supported CEO and leadership team can handle?
- 02Is the CEO's time currently consumed by delivery work that should sit lower in the organisation?
- 03Can the board name, specifically, the decisions the COO would own versus the CEO?
- 04Is this a genuine structural need, or an attempt to solve a leadership-team capability gap with a new layer instead?
- 05If succession is part of the intention, has that been made explicit rather than implied?
Recruiting a permanent executive?
Long-term ownership of a defined executive remit, recruited against what the appointment has to deliver rather than against a job title.
Related services
Written by
International Sales & Market Development Director, Evans Sales Consultancy
Published 17 September 2026 — 4 min read