New COO With Imposter Syndrome? The Fear of Commanding Your Own Peers

There is a specific disorientation reserved for the newly-minted COO, and it is unlike the doubt any other chief feels. You were promoted for excellence in running something — a function, a region, a business unit — where you had a team, a budget and a clear line of authority, and where competence reliably converted into results because you could direct the resources yourself. The COO seat removes almost all of that. You are now accountable for how the entire enterprise executes, but the people who actually execute — the CTO, the CRO, the CFO — are your peers, not your reports. The self-doubt a new COO feels is the vertigo of discovering that the instrument you mastered, direct authority, is precisely the instrument the new job takes away.

This makes COO imposter syndrome distinctively about power rather than knowledge. A new CFO doubts a skill; a new COO doubts a mechanism. You know how to run things — that is not in question. What is in question is whether you can make things happen when you cannot mandate them, when the levers are influence, alignment and trust rather than reporting lines and budgets. And because the enterprise judges a COO by whether the machine runs, the fear is uniquely exposing: a functional leader can fail quietly, but a COO who cannot orchestrate fails in full view of every chief they were supposed to align. The seat is designed to run on a power you have never had to develop, and the gap feels, at first, like a verdict.

The essential work is to separate two things the new COO experiences as one: the ordinary nerves of any step-up, and the one genuine capability the role actually demands that the old job never did. Much of what you feel is pure transition — the loss of familiar mastery-signals, the discomfort of a wider remit, the exposure of a bigger seat. That fades with repetition and should not be mistaken for inadequacy. But underneath it sits a real, specific gap, and honesty about it is what makes the difference: the ability to produce enterprise-wide execution through lateral influence rather than vertical authority. That is a genuinely different skill from the one that got you here, and no amount of self-belief substitutes for building it.

The distinction matters because the two demand opposite responses. Transition nerves need patience and perspective — you treat them as weather, not verdict, and let competence accrue. The orchestration gap needs deliberate skill-building — the mechanics of aligning peers, of turning shared goals into shared commitment, of resolving cross-functional conflict without the authority to impose a ruling. Conflate them and you get the worst of both: you either dismiss the real gap as ‘just nerves’ and never build the skill, or you inflate the nerves into proof that you cannot do the job at all. The new COO who thrives is the one who says, precisely, ‘this part is transition and will pass, and this part is a muscle I have never built and must’.

The trap that catches most new COOs is a hidden assumption: that authority is the strong form of leadership and influence is the weak substitute you are stuck with. It is exactly backwards. Command is the crude instrument — it works only within your own lines, only when people must comply, and it stops dead at the boundary of your org chart. Orchestration is the more powerful instrument precisely because it crosses those boundaries: it moves people who have every right to say no, which is the only kind of movement that actually runs an enterprise. The COO who mourns their lost authority is mourning the loss of a short lever and failing to pick up the long one.

Consider what the great conductors of organisations actually do. They do not order the CRO and the CTO to align; they make alignment the obviously rational course for both, they surface the shared goal that makes cooperation self-interested, and they build the personal credit that lets them broker what neither peer would concede to the other alone. None of that is available to someone who leads only by mandate. The COO seat is not a demotion in power dressed up as a promotion; it is an upgrade to a form of power that works where authority cannot reach. Reframing orchestration as the senior skill rather than the consolation prize is what turns the fear of not being able to command your peers into the ambition to conduct them.

Standing as a COO is built through a handful of deliberate early moves that establish you as the enterprise’s indispensable integrator rather than a functional leader with a grand title. The first is to become the person who makes other chiefs more successful — to arrive in cross-functional problems not as the referee imposing a verdict but as the one who finds the solution that lets both peers win. A COO who reliably makes the CRO and the CTO look good to the board earns a form of trust that no reporting line could grant, and that trust is the true currency of the seat. You are not trying to command your peers; you are trying to become the person they cannot execute without.

The second move is to own the seams. Every enterprise loses more value in the gaps between functions than inside any one of them — the handoffs that drop, the goals that conflict, the programmes that stall where no single chief is accountable. Those seams belong to no one, which means they can belong to you, and owning them is how a COO demonstrates enterprise-level command without needing enterprise-level authority. When you become the leader who makes the whole run better than the sum of its parts, the question of whether you can command your peers quietly dissolves — because you are no longer trying to move them by force, you are the one they rely on to move together. That is orchestration, and it is the job.

COO imposter syndrome feeds on itself if left alone. The new COO who secretly believes they cannot move peers without authority tends to overreach for control — pulling decisions to themselves, leaning on the CEO to impose what they cannot broker, treating every disagreement as a threat to their standing — and each of those moves confirms to the other chiefs that the COO is insecure rather than trusted, which erodes the very influence the role depends on. Or they retreat into the operational detail where their old authority still feels real, and abdicate the integrating work that is the actual point of the seat. Either way, the fear becomes the outcome.

This engagement is built to break that pattern deliberately. Across two partner conversations, a diagnosis and a written roadmap, we separate your transition nerves from the genuine orchestration gap, reframe lateral influence as the senior skill it actually is, and design the specific early moves that establish you as the enterprise’s indispensable integrator rather than a functional leader out of their depth. The aim is not to restore the authority you lost — that authority was never coming back, and you do not need it. It is to make you fluent in the more powerful form of leadership the COO seat was always meant to run on, so that conducting peers stops feeling like a threat and starts feeling like the work you were promoted to do.