Executive leadership
The 2026 COO: A Board Specification for Operational Leadership
First published · Revised 22 October 2026
Operational leadership requires more than task oversight. Boards also need to examine how a candidate connects technology, people and decision-making under pressure.
From administrative oversight to architectural leadership
The disconnect between legacy recruitment expectations and modern operational requirements is profound. Two decades of GCC transformation work, scaling infrastructure for Huawei, Motorola Solutions, and SuperJet Oman, make one thing clear: the functional silos of the past cannot survive the velocity of the future. The 2026 COO must be able to dissolve the boundaries between technology, human behavior, and crisis management.
The modern mandate is reconstituted around three uncompromising imperatives: the inseparable fusion of technology and operations, the recognition of the Human OS as the governing limit of growth, and a crisis-proven resilience that prioritizes what survives over what looks good on paper.
The three operational realities
Operations and technology are closely connected. A decision about a system can change a workflow, a customer promise or an approval boundary. The COO needs to understand those connections and involve the people responsible for them.
Technology can amplify unclear responsibilities as readily as good practice. Before scaling a system, examine whether people understand the decisions it supports, the evidence they need and their accountability for acting.
Reality three: the mandate is crisis-proven resilience. The true job is not to manage the sunny-day scenario; it is to build what remains standing when the power goes out. Under extreme stress, technical systems may evaporate, but disciplined human systems endure. The 2026 COO is a veteran of stress tests: payment cycle collapses, supplier failures, regulatory shifts. They build for the worst case to ensure the best case survives.
The 8C competency blueprint
The 8C Framework turns the mandate into a competency blueprint, moving an organization from hero-dependent performance to system-driven excellence. Clarity: name reality without defensiveness, eliminating the optimism bias that masks structural decay. Conditions: ground strategy in actual regulatory, cultural, and resource constraints. Control: implement governance that enables performance without bureaucratic weight. Capability: audit and construct execution capacity before the first milestone, not after it.
Compliance: clarify obligations, commitments and boundaries. Calibration: agree the evidence for assessing progress. Correction: make it possible to revise an approach when that evidence changes. Continuity: consider how useful practices survive changes in people and circumstances.
The board mandate: redefining executive evaluation
Boards can examine industry experience alongside a candidate’s ability to understand an unfamiliar situation and build workable decision structures. Past titles alone do not answer those questions.
Three prompts do most of the work. Boundary dissolution: describe a transformation where you dissolved the silos between operations, IT, and HR to deliver a single integrated outcome. Human OS resilience: provide evidence of a human system you built that remained functional during a genuine crisis, and how it compensated for technical failure. Integrated architecture: explain how you ensure technology bets are treated as operational imperatives rather than capital expenditures.
The ideal archetype is the builder. A taskmaster helps you survive the next quarter. A builder ensures you have an enterprise left to lead.
Questions to explore
What does a modern COO actually do?
The 2026 COO fuses operations and technology into one discipline, treats the Human OS as the governing limit of growth, and builds crisis-proven resilience. The role is structural architecture, not task management: establishing identity, discipline, and governance before installing technical systems.
How should boards evaluate a COO candidate?
Stress-test architecture, not pedigree. Three prompts cover it: a transformation where they dissolved operations, IT, and HR silos into one outcome; evidence of a human system they built that held during a real crisis; and how they make technology bets function as operational imperatives rather than capital expenditures.