Why the COO Role Is the C-Suite’s Most Fluid: Archetypes, No-Blame Culture, and CEO Guidance

Futuristic boardroom with two executives at a long table overlooking a city skyline, featuring a holographic rocket and gear diagrams that symbolize a startup launch, innovation, and strategic growth.

I’ve long believed the COO seat is the most fluid role in the executive suite, and my perspective has been sharpened by learning from operating leaders who’ve scaled iconic companies. One conversation that stands out centers on Sara Clemens, most recently COO of Twitch and former COO of Pandora.

In this interview, we explore the nuances of the COO role, which can vary drastically across different companies. We cover:

The three main COO archetypes and which sorts of folks are best suited for those roles.

The tactical elements of being a COO, including Sara’s advice for what good strategy actually looks like, and how to truly create a no-blame culture.

Sara’s lessons on keeping pace as a company doubles in size, including her tips on sketching out “decision rights.”

Guidance for CEOs considering bringing on a COO to the executive suite.

From my vantage point in product management leadership, the variability of the COO mandate is a feature, not a bug. Great COOs adapt to the business model, stage, and CEO superpowers. The best partnerships I’ve seen start with explicit clarity: What outcomes matter most in the next 12–18 months? Which constraints are real? Where will product, operations, and go-to-market intersect—and who owns what?

On archetypes, I map product’s needs to the operator’s strengths. If we’re pursuing step-function growth, I look for a COO who is comfortable orchestrating ambiguous, cross-functional bets. When the priority is scaling reliability and margins, I align with a process- and systems-oriented operator. When the goal is organizational transformation, I look for a builder who can reset norms while protecting momentum. Getting this fit right improves execution, reduces decision latency, and clarifies how we measure progress.

On the tactical elements of being a COO and what good strategy looks like, I anchor on a few principles that have never failed me: strategy is a coherent set of choices, not a list of initiatives; it prioritizes outcomes over output and forces trade-offs. We translate those choices into a focused operating cadence—clear goals, crisp leading indicators, and reviews that separate signal from noise. In practice, that means elevating outcomes vs output OKRs, pressure-testing assumptions early, and linking roadmaps to measurable value creation.

Creating a no-blame culture isn’t soft—it’s operationally essential. Blame keeps teams defensive; learning keeps them fast. I’ve had success institutionalizing blameless postmortems, pre-mortems for high-risk launches, and a norm of writing down hypotheses before we run experiments. We fix the process, not the person. Over time, this builds psychological safety and enables the honest retrospectives that high-velocity product and operations teams depend on.

As companies double in size, complexity compounds. This is where “decision rights” become a force multiplier. I recommend codifying who is the decision-maker, who must be consulted, and who needs to be informed before work begins. Whether you prefer RACI, DACI, or RAPID, choose one, teach it, and use it consistently. Pair decision rights with single-threaded ownership for critical initiatives and you’ll reduce escalation churn, speed handoffs, and preserve accountability as headcount grows.

Keeping pace during hypergrowth also demands an operating rhythm that scales. I align quarterly planning with a lightweight monthly business review, ensure product roadmapping and sprint planning tie directly to company-level outcomes, and maintain a disciplined change-management channel so emergent priorities don’t derail committed work. When the cadence is consistent and the artifacts are simple, leaders can move fast without breaking trust.

For CEOs considering bringing on a COO to the executive suite, my guidance is straightforward: define the mandate in terms of outcomes, not tasks; be explicit about the seams between CEO, COO, and product; and decide how you’ll make decisions together before the first decision. Align on metrics, communication rhythms, and escalation paths. Hiring a great COO is not about finding a clone—it’s about designing a complementary partnership that compounds your strengths and closes your gaps.

The through line across all of this is clarity—of strategy, of responsibilities, and of learning. Get those right, and the natural fluidity of the COO role becomes your organizational advantage.


Book a consult png image

What does the article say about COO archetypes?

It notes there are three main COO archetypes and discusses which sorts of folks are best suited for those roles. This framing helps match the COO to the business model, stage, and CEO strengths.

What tactical elements of being a COO are highlighted?

The piece emphasizes that strategy should be a coherent set of choices and should prioritize outcomes over output, with a focused operating cadence and clear goals and leading indicators. It also highlights linking roadmaps to measurable value and testing assumptions early.

Why is creating a blameless culture important, and how is it implemented?

Creating a no-blame culture is described as operationally essential; it reduces defensiveness and speeds learning. The article recommends blameless postmortems, pre-mortems for high-risk launches, and documenting hypotheses before experiments.

What are 'decision rights' and how should they be used?

Decision rights become a force multiplier as headcount doubles. The author recommends codifying who makes decisions, who must be consulted, and who needs to be informed, using a framework like RACI, DACI, or RAPID.

What guidance does the article offer for CEOs considering bringing on a COO?

Define the mandate in terms of outcomes, not tasks; clarify seams between CEO, COO, and product; and decide how decisions will be made before the first decision.

How should leaders structure the operating rhythm to scale during hypergrowth?

Maintain an operating cadence by aligning quarterly planning with a lightweight monthly review, tying product roadmaps and sprints to company outcomes, and keeping a disciplined change-management channel.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

Signup for Weekly Digest Emails

Categories

Archieve