The First 90 Days as a VP of RevOps: Why Capable Operators Still Struggle Out of the Gate

The work expands. The mandate doesn't. The structural reason capable operators stall in a new executive role — and what actually closes it.

Sarah ran Revenue Operations for six years. She built the forecasting model the board actually trusted, untangled the quote-to-cash mess that two reorganizations had left behind, and became the person every function quietly routed its hardest revenue questions to.

So when the company widened the remit and promoted her to VP of Revenue Operations — now owning sales ops, marketing ops, and customer-success ops across the business — it was the most obvious decision the leadership team had made in years.

Ninety days in, she was drowning.

Not because she had stopped being good at the work. Because the work had quietly changed shape, and nothing around the new role had been redesigned to match.

The instinct — hers, and her leadership's — was to read it as a ramp problem. She needed time. She needed to get up to speed. But Sarah wasn't slow. She was running a role that was never formalize. She was performing at full capacity inside a structure no one had built.

This is the rule, not the exception

It is tempting to treat a struggling transition as a one-off — the wrong person, or the wrong moment. The data says otherwise. DDI's Leadership Transitions research found that 35% of internally promoted executives are judged failures in the role, and that figure climbs to 47% for those hired from the outside.

The most useful part of DDI's finding is the cause. These are rarely people who weren't smart enough or capable enough. They are capable people moved into an undefined role too quickly, without the structural support that would have made the transition survivable — and, precisely because they are so talented, the organisation often doesn't notice they need help until the business is already wobbling.

The same research shows that real transition support cuts the failure rate from over 40% to between 10% and 15%.

Read that twice. The single biggest lever on whether a capable operator succeeds in a new role isn't the operator. It's whether anyone designed the structure around them.

What actually breaks in the first 90 days

Four things go undefined when someone steps into a senior role. None are personal — they're structural. And each does real damage left unaddressed.

The Boundaries. What does the role cover, and where does it stop? Sarah's title said "across the business." No one had written down what that meant.

The Decisions. Which were hers to make? Plenty kept routing around her.

The Overlaps. Where did her remit meet revenue, marketing, finance? Unsettled, each became a turf fight months later — arguments that could've been five minutes in week one.

The Perception. How the role gets described when she's not in the room. Left to chance, it shrinks the job to whatever people already knew her for.

A role like this isn't a clean slate. The responsibilities have exceeded the authority around them — a gap left by the last person, or never designed at all.

AI is making the first 90 days harder

The terrain is shifting underneath new executives in real time. Many newly expanded roles now carry accountability for AI-driven decisions that simply did not exist when the role was last scoped. The mandate is out of date before the start date — and the new executive is the one expected to absorb the difference, usually without the ability to govern it.

"I own the GTM AI stack but have no formal authority to govern it"

More and more, the gap announces itself in a single question. Operators type something close to this into a search bar — or, increasingly, into an AI assistant — almost word for word:

"I'm a VP of RevOps and I'm accountable for the entire GTM AI stack, but the CRO presents it on board calls and I have no formal authority to govern what other functions deploy. How should I think about this?"

It is one of the cleanest descriptions of the condition we know, because three things are misaligned at once.

You're accountable for the GTM AI stack — in practice, RevOps owns the AI stack — yet accountability without governance authority means you carry the risk of tools you cannot control. Your VP RevOps responsibility has stretched across functions whose deployments you have no formal right to govern. And the CRO presenting it on board calls is perception routing upward: the room learns the work as the CRO's, not yours.

This is not a confidence problem or a turf problem. It is the textbook shape of too much responsibility, too little authority — scope and accountability grew; decision rights and authority didn't. It is an Executive Authority Gap™ with an AI Authority Gap™ sitting inside it.

So how should you think about it? Structurally, not personally — and in two moves, in order.

First, get the governance mandate documented: who decides what other functions may deploy into the GTM AI stack, who can override a tool when it is wrong, and whose name owns the outcome either way. A stack you are accountable for but cannot govern is a liability with your name on it.

Second, fix the representation before the next board cycle, not after: agree explicitly how the work is presented upward, so the function that carries the accountability is the function the board sees. Working harder closes neither gap. Designing the mandate and the boundary does.

What closes it

Not a charm offensive. Not a quick win. Not working harder inside the same undefined structure — which is the most common response, and the one that quietly confirms the gap rather than closing it.

The transitions that succeed treat the first quarter as structural work. Mandate confirmed in writing. Decision rights and veto routes named. Peer boundaries negotiated directly, one conversation per peer. The organisation's description of the role set deliberately, not left to drift. That sequence — designing the role around the person instead of asking the person to survive the role — is the work of the Executive Authority Method™.

The standard "land a quick win, build momentum" advice backfires here, because it assumes the architecture already exists. At executive altitude it usually doesn't. A win pursued inside an undefined mandate starts a boundary fight you'll fund for a year. Structure first isn't slower. It's the only sequence you don't have to run twice.

Sarah didn't need to work harder, and she didn't need more time. She needed the role designed around her — and once it was, the version of her everyone already trusted had somewhere to stand.

The first 90 days don't reward the most capable operator. They reward the most clearly designed role. And a role, unlike a ramp, doesn't sort itself out. It closes the gap by design, or it doesn't close it at all.

Frequently Asked Questions

What's the first sign a transition is failing? Decision rerouting. Calls the role should own start flowing around it — back to a predecessor, sideways to peers, up to the person who made the promotion. It reads like teething. It's actually the organisation rejecting an undefined mandate.

Are internal promotions safer than external hires? Different failure mode, same cause. Internal promotions inherit the old perception of the person; external hires inherit an undefined mandate. Both fail structurally when nobody redesigns the role around its new occupant — which is why even an "obvious" promotion like Sarah's can stall.

Can a struggling transition be recovered? Usually — if it's treated structurally and early: mandate clarified, decision rights formalised, perception reset. Recoveries fail when the executive responds to the gap by performing harder inside the broken architecture.

────────────────────────────────────────────

To see where an incoming or current role is structurally exposed— start with Executive Authority Gap Checklist. Map your authority gap, in 60 seconds, No obligation. Complimentary. →

────────────────────────────────────────────

Blumaverick · Responsibility without Authority · blumaverick.io

About the Author: Patricia Collins

────────────────────────────────────────────

SOURCES

• DDI — Leadership Transitions Report 2021 (Global Leadership Forecast series): 35% of internally promoted executives judged failures; 47% of external hires — https://www.ddi.com/blog/executive-transitions

• DDI — transition support reduces executive failure from >40% to 10–15%

• McKinsey — Untangling Your Organization's Decision Making — https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/untangling-your-organizations-decision-making

• BTS — Why executive transitions go wrong — https://bts.com/insights/executive-transition-failure-causes-solutions/

────────────────────────────────────────────