The Talent Magnet: How One Executive Hire Attracts More
April 27, 2026
The CHRO Nobody Noticed: When Invisible Value Disappears
May 1, 2026
COO First 100 Days: Why Operators Fail Before They Start
The Operator's First Hundred Days: Why COOs Fail Before They Start
He arrived with a 90-day plan. By day thirty, he'd broken three relationships he didn't know he needed. He wasn't wrong. He was early.
The COO role fails fastest. Not because of capability. Because it's the only role with no defined edges. Every other executive inherits a domain. The COO inherits ambiguity.
The CFO owns finance. The CTO owns technology. The CMO owns marketing. The COO owns "operations," which usually means whatever the CEO hasn't defined and may not release to someone else once they start doing it.
The COO who starts executing before understanding which territory is genuinely theirs will collide with functional leaders who didn't know their autonomy was being reorganized. That collision happens in the first thirty days. The repair takes months.
The Three Failure Modes
Scope Assumption
The COO assumes the role is portable. It isn't. It's negotiated.
They arrive with a mental model of what COOs do, built from their previous role. They start managing functions, reviewing processes, and inserting themselves into decisions. The CEO hired them with a vision of what the COO would own, but that vision lives in the CEO's head, not in a document. The VP of Engineering assumed they'd continue reporting to the CEO. The Head of Customer Success assumed their function was autonomous. Nobody told the COO these assumptions because nobody asked. And the COO didn't ask because they assumed the scope was obvious.
Nobody defined the scope. So everyone defends their version of it.
That's the conflict. By week three, the COO is asking for reports that functional leaders don't think they should produce, and for attendance at meetings they weren't invited to. The functional leaders go to the CEO. The CEO mediates a conflict that shouldn't have existed.
The COO's first impression with the leadership team is "threat." That impression takes months to undo.
Authority Confusion
In most companies, authority is discovered by breaking it. Even when the scope is roughly defined, the authority within it remains ambiguous. Does the COO have the authority to reorganize a department, or do they need CEO approval? Can they hire and fire within their functions, or does every headcount change go through the CEO?
Every early decision becomes a test. Not of judgment, of boundaries.
The CEO who hired the COO to "take operations off their plate" often discovers in the first thirty days that they don't actually want operations off their plate. They want to stop dealing with operational minutiae but retain control over operational decisions. The COO, who was promised authority, discovers that authority is conditional, revocable, and defined retroactively.
This produces hesitation. The COO slows down, unsure which decisions are safe. The CEO watches the hesitation and wonders whether they hired someone decisive enough. The COO senses the dissatisfaction and either overcompensates with a burst of unilateral action or retreats further into caution. Both responses make the problem worse.
Political Miscalculation
The COO sits in the most political seat in the company. Not by intent. By design.
Every improvement the COO makes costs someone power.
The VP of Sales, who considers themselves the CEO's informal second-in-command, now has a COO between them and the CEO. The CTO, who's been operating autonomously for three years now, has someone asking about their engineering processes. The Head of Supply Chain, who reported directly to the CEO, now reports to the COO, which they experience as a demotion regardless of how the CEO frames it.
The COO who charges in without mapping who holds informal power, who has the CEO's ear, and whose autonomy is politically protected will create resistance that has nothing to do with their competence and everything to do with their sequence.
The Formation Lap
Skip the formation lap, and you're driving blind.
Most COOs don't crash immediately. They spend six months correcting the first corner.
The first sixty to ninety days should be a period of deliberate assessment that produces the information needed to act effectively. Not inaction. Diagnosis.
Weeks One Through Three: Decode
You're not evaluating. You're decoding.
Meet every functional leader individually, not to assess them, but to understand what they own, how they think about their function, and what they believe is broken. Meet the CEO multiple times, not about strategy, but about expectations. What does the CEO actually want the COO to do? Where are they willing to hand off? Where are they not willing to hand off, regardless of what they said during the interview?
Meet the team below the functional leaders. Director and manager-level people will tell you what VPs won't: where processes actually break, which systems are held together by specific individuals, and which relationships are fragile.
"At my last company" is a tell. It means you're not here yet.
Weeks Three Through Six: Map
Build a map of the organization with four dimensions that the org chart doesn't show.
Decision authority. Titles lie. Decisions don't. Who actually makes which decisions — not who is supposed to, but who does. The procurement manager making vendor decisions that technically require VP approval. The CEO overriding the marketing budget quarterly despite formally delegating it.
Informal power. This is the real org chart. It's just never written down. Who has the CEO's ear? Who can veto decisions informally? Who is politically protected? The COO who reorganizes a politically protected function without understanding its protected status will lose a fight they didn't know they were in.
Process reality vs. process documentation. Most companies run on undocumented truth. Changing the documented process without understanding the undocumented one will break something that works for reasons no one can see.
Relationship infrastructure. Friction is where performance is lost. Where do handoffs fail? Where does work fall between teams? This map shows the COO where intervention yields results and where it meets resistance.
Weeks Six Through Twelve: Negotiate the Charter
The charter defines survival.
Without it, every decision becomes a negotiation. And negotiation kills speed.
The charter answers four questions. What does the COO own, specific functions and decision domains, not "operations." What authority do they have within that scope: hiring, budget, process changes, and vendor authority? What does the COO not own, naming the exclusions matters as much as naming the inclusions. And how will the CEO and COO handle disagreements? If the CEO reserves the right to override any COO decision, the COO has responsibility without authority, which is the structural condition that ends COO tenures.
The charter evolves as the COO demonstrates judgment and the CEO builds trust. But starting without one means the boundaries are discovered through collision rather than conversation.
What the CEO Owes the COO
COO success is a CEO decision.
Define the scope before the hire. If you can't define it, don't hire it. The candidate who accepts an undefined scope has a starting point. The candidate who rejects it is telling you something important.
Take the hit publicly. When functional leaders resist the COO's authority, the CEO must visibly support the COO, not stay neutral while VPs undermine the new operator. Staying neutral is a choice. It just looks like inaction.
Give the formation lap time. Speed without context is damage. The COO who listens for sixty days and acts deliberately for the next sixty will outperform the COO who acts immediately and spends the next six months repairing the damage.
Actually, let go. The CEO who says "I want to step back from operations" but attends every operational meeting, reviews every operational decision, and calls the warehouse manager directly hasn't stepped back. They haven't let go. The COO can't own operations that the CEO hasn't released.
TLDR
The COO who moves first creates friction. The COO who understands first creates leverage.
The difference isn't speed. It's sequence.
Every early decision the fast-moving COO makes lands in a system they don't fully understand. Some of those decisions are right. Some damage relationships that would have been essential six months later. The cost of the wrong ones isn't just the decision; it's the trust that gets spent defending it.
Most COOs don't fail in execution. They fail in interpretation.
The COO role isn't hard because it's complex. It's hard because it's undefined.
Charlie Solórzano is a Managing Partner at Alder Koten, a boutique executive search firm specializing in C-suite and board placements across the U.S. and Mexico markets. He advises founders, investors, and boards on leadership transitions using The Race Conditions Model™, a proprietary diagnostic framework built on the thesis that leadership success is determined by conditions, not credentials.
Hiring a COO — or Just Brought One On?
The first hundred days are the highest-leverage period of the entire COO tenure. Getting the scope, authority, and charter right before execution starts is the difference between an operator who compounds advantage and one who spends a year repairing early damage. If you're making this hire or navigating this transition, let's talk.
Schedule a Confidential ConsultationFrequently Asked Questions
Why do COOs fail in the first 100 days?
The COO role has the highest failure density in the C-suite because it's the only role with no defined edges. Every other executive inherits a clear domain. The COO inherits ambiguity — whatever the CEO hasn't defined and may not actually release. The COO who starts executing before understanding which territory is genuinely theirs will collide with functional leaders who didn't know their autonomy was being reorganized. The damage from those early collisions takes months to undo.
What should a COO do in the first 30 days?
Decode, don't execute. Meet every functional leader individually to understand what they own and what they believe is broken. Meet the CEO multiple times — not about strategy, but about expectations. Where is the CEO willing to hand off? Where are they not? Meet the team below the functional leaders: director and manager-level people will tell you what VPs won't. None of these conversations should be about what you did at your last company. They should be about understanding this one.
What is a COO charter and why does it matter?
A COO charter is the document that should exist before the COO starts — defining what they own, what authority they hold within that scope, what they explicitly don't own, and how they and the CEO will handle disagreements. Without a charter, every decision becomes a negotiation, and negotiation kills speed. Most COO onboarding failures aren't about competence. They're about scope and authority never being defined, so boundaries are discovered through collision rather than conversation.
What does the CEO owe a new COO?
Four things. Define the scope before the hire — if you can't define it, don't make the hire. Take the hit publicly when functional leaders resist the COO's authority — staying neutral while VPs undermine the new operator is a choice that looks like inaction. Give the formation lap time — speed without context is damage. And actually let go: the CEO who says they want to step back from operations but reviews every operational decision and calls the warehouse manager directly hasn't stepped back. The COO can't own what the CEO hasn't released.
How does a COO map informal power in an organization?
By paying attention to decisions, not titles. Titles lie. Decisions don't. The informal power map reveals who has the CEO's ear, whose opinion carries disproportionate weight, who can veto decisions without formal authority, and whose functions are politically protected. This map is never written down, but it's the real org chart. The COO who reorganizes a politically protected function without understanding its protected status will lose a fight they didn't know they were in.
What's the difference between a COO who succeeds and one who fails early?
Sequence. The COO who moves first creates friction. The COO who understands first creates leverage. The difference isn't speed — it's interpretation. Most COOs who fail early weren't incompetent. They were accurate about the problems and wrong about the sequence for addressing them. They made real decisions in a system they didn't fully understand, spent trust defending those decisions, and found themselves operating from a deficit before they'd built the credibility to absorb it.
