COO

You design the operating system of a company where humans and agents work together. The agent runs the routine operations; you run the operating model. The COO role becomes more consequential as more of the company runs on agentic execution.

Elevationprimary Emergencesecondary Convergencepartial

Family

Executive

Equivalent legacy role

COO, Chief Operating Officer, President (in some structures), Chief of Staff at smaller orgs

Reports to

CEO (sometimes Board for operating partnership)

Works alongside

CEO · CTO · VP Sales · Director of Customer Success · Head of People Operations · Workflow Architect · Governance Specialist

The work

You own how the company operates — across functions, across teams, across the agent-human hybrid that defines AI-native work. The CEO sets direction; you make the company run. The Workflow Architect and Governance Specialist design pieces of the operating model; you own the integration of the pieces into a coherent whole.

Day-to-day, you:

Design the company's operating model. How work flows across functions, where the gates are, how exceptions get handled, how the AI-native operating system holds together. This is the central design problem at AI-native scale, and it's yours.
Run cross-function execution. When something needs to happen across Sales, CS, Product, Engineering, Finance — you make sure it does. The agent helps coordinate; you handle the judgment.
Develop executive team coherence. Your peer executives have to operate as a team, not as separate function heads. The COO often holds the responsibility for making that real.
Own operating reviews. Weekly, monthly, quarterly — the rhythm by which the company sees itself. You design the rhythm and run the reviews that matter most.
Validate at risk-graded gates. Routine operations distribute to executives. Major cross-function operational decisions, executive escalations, major operating-model changes, and CEO-delegated decisions require your direct involvement.
Handle the operational dimensions of major decisions. Restructures, acquisitions, market expansions, product pivots — the operating consequences of strategic moves are yours to design and execute.
Partner with CEO on strategy execution. Strategy is the CEO's; operating execution is yours. The seam between them is continuous partnership.
Steward the agent operating model at company scope. Together with CTO, Workflow Architect, and Governance Specialist, you ensure the AI-native operating system actually works for the whole company.

What success looks like

Concrete outputs at this tier:

Operating coherence. The company runs as a coherent system. Cross-function execution works; surprises are rare.
Strategic execution. Strategic decisions move from formulation to operational reality at the cadence the strategy needs.
Executive team partnership. Peer executives operate as a team. Friction is productive, not corrosive; alignment is real.
Operating-model health. The AI-native operating model is well-designed, well-governed, and improving. The substrate the company runs on is solid.
Operating efficiency. The company achieves outcomes with appropriate cost and effort. The COO catches drift.

What does not count as success: meetings held, dashboards built, headcount grown, operating manuals produced that no one reads.

What makes this work interesting

The interesting part is not the operational mechanics. It is the design of how a company actually runs in an era where execution scales differently.

You design the company's operating system. With AI-native operations, the operating model is genuinely load-bearing — it's not just a back-office concern but the substrate of everything the company does. The COO sits at the center of that.

Operating-model design is genuinely new work. No textbook describes how to design the operating system of a company where most execution happens through agents. You're part of inventing the practice. The patterns you develop will inform how AI-native companies operate.

You sit at the executive team's center of gravity. The CEO sets direction; the COO often holds the team together operationally. The role is partly peer-to-peer with the CEO and partly partnership with each other executive.

Cross-function execution becomes possible. With operational coordination absorbed and the operating model explicit, the company can actually act across functions in ways that legacy operations made difficult. The COO is the architect of that capability.

Operating efficiency becomes a design problem. Cost-per-outcome, throughput, retention, expansion — all become more sensitive to operating-model design than to individual heroics. The COO has more leverage on these metrics than any other role.

You navigate hard organizational decisions. Restructures, comp changes, major operating shifts, cross-function role changes — the operational complexity belongs to the COO. The decisions are consequential and hard.

The role's strategic weight is real. Companies that scale well with AI-native operations have COOs who designed for it. Companies that don't, usually have COOs who treated the operating model as a back-office concern.

Partnership with the CEO is the most leveraged work. The CEO-COO partnership is one of the most powerful executive relationships in any company. At AI-native scale, it becomes more so.

What may not appeal. If the COO role you wanted was the "right-hand operator" who runs the business day-to-day so the CEO can focus on strategy, that role distributes substantially in AI-native operations. Operations distribute to the operating model and the executive team; you design and govern more than you operate. COOs who liked the operational immersion sometimes find the new role more strategic and abstract. You also share executive partnership with the entire executive team rather than being the singular CEO partner; political dynamics can be more complex.

Who thrives in this role

The aptitudes that matter most at T3 are systems-thinking, executive-judgment, and integration aptitudes — different from operational-rigor strengths alone.

You think in systems. Companies are systems; operating models are systems; the AI-native operating model is a system of systems. COOs who see structure produce coherent organizations; COOs who don't produce fragmentation.

You hold contradictions without flattening them. Speed vs safety. Standardization vs autonomy. Cost vs quality. Good operating design navigates these tensions; bad design collapses them. The both/and is the work.

You partner well with the CEO and peer executives. COO is fundamentally a partnership role. COOs who can hold a strong perspective while genuinely partnering produce strong companies; COOs who can only dominate or only defer produce friction.

You write clearly. Operating-model documentation, executive memos, cross-function communications — clear writing is core. COOs who can write clearly produce alignment.

You handle hard organizational decisions. Restructures, performance escalations at executive level, comp changes, cultural decisions. The capacity to hold hard conversations and act through them is part of the job.

You're comfortable with delayed and diffuse feedback. Operating-model changes show their consequences over quarters and years. COOs who need fast feedback struggle; COOs who can design with patience produce strong systems.

You can manage your CEO well. The CEO is your primary partner; the partnership is negotiated continuously. COOs who can give the CEO honest feedback, push back productively, and execute against the CEO's strategic intent are the ones who succeed.

You hold values under pressure. Operating decisions test cultural commitments. COOs whose values shift with quarterly pressure produce cultures that don't hold; COOs whose values hold produce trust.

Less essential than before: capacity to personally run every operational matter, mastery of specific operational tools, the ability to be the singular operational hero. The role values judgment and design over personal execution.

Skills to develop to get there

The aptitudes describe disposition. The skills below are what you actively build.

Operating-model design. Specifying how the company runs across functions. How to practice: document your current operating model. Identify where it fails most. Redesign one major piece per quarter; measure outcome.

Executive partnership. Working substantively with peer executives. How to practice: one substantive executive-to-executive engagement per week. Track what propagates into operating coherence.

CEO partnership. Holding a productive partnership with the CEO. How to practice: after each major CEO interaction, reflect on what worked. Where did you contribute? Where did you defer? Where might you have pushed harder?

Hard-decision execution. Translating strategic decisions into operational reality. How to practice: for each major strategic decision, write the operational implementation plan. Where execution disappoints, name what was missing from the plan.

Operating-rhythm design. Designing the cadence by which the company reviews itself. How to practice: audit your current operating reviews. Which produce decisions, which produce theater? Adjust.

Cross-function arbitration. Resolving conflicts and tradeoffs between functions. How to practice: after each arbitration you handle, write a one-paragraph reflection. What worked? What would you do differently? Build pattern recognition.

AI-native operating-model judgment. Reading whether the operating model is producing the outcomes strategy needs. How to practice: quarterly review of operating model versus strategic outcomes. Identify drift. Address with Workflow Architect and Governance Specialist.

Strategic writing. Memos that align executive team and board on operational matters. How to practice: write one operating-strategy memo per quarter. Have CEO and peers challenge. Refine.

Pick the skill that maps to your most recent operational disappointment. Practice it for a quarter.

How this differs from the legacy COO role

Legacy COO (pre-AI)	COO (AI-native)
Substantial time running operations day-to-day	Operations distribute to the operating model and executive team; COO focuses on operating-model design
Operating model is implicit, lives in COO's head	Operating model is explicit, documented, applied through agentic execution
Cross-function execution requires COO's personal involvement	Cross-function execution is designed to work with risk-graded COO involvement
Operating reviews are status updates from each function	Operating reviews are decision-making forums; status absorbs into agentic reporting
Best COOs are the most operationally relentless	Best COOs are the deepest systems thinkers and strongest executive partners
Career path: COO → CEO at similar-scale company	Career path: same, plus CEO at AI-native company, transformation executive, board specialist

The role is not a more rigorous operations head. It is a different kind of work — designing and stewarding the operating system of an AI-native company.

Which role evolution patterns are in play

Elevation (primary). The role's center of gravity rises from operational management to operating-model design and executive partnership.
Emergence (secondary). A substantial portion of the work — AI-native operating-model design at company scope, agent governance at the executive level, cross-function operating coherence in an agentic operating model — is genuinely new responsibility for the COO role.
Convergence (partial). Boundaries with CTO and Workflow Architect blur as the AI-native operating model touches both technical and organizational systems. The COO co-owns the operating model with technical and emerging-role partners more than legacy COOs co-owned anything.

Specialization and Absorption do not meaningfully apply.