The definitive reference on the first 90 days as a newly promoted Vice President — what the window is actually for, the mistakes that derail new VPs, the four-move Stratos protocol for landing the role, how the focus shifts across the 30/60/90-day arc, and how to recover if you have already burned the early weeks. Published by Stratos Coaching as an open resource for newly promoted VPs and the organizations onboarding them.
The first 90 days as a new VP are not for declaring strategy, restructuring the org, or proving you deserved the promotion. They are for listening at scale, making the identity shift from operator to executive, mapping the political landscape, and shipping one tightly scoped early win. The window is decisive because the organization forms its lasting impression of your altitude during it — and McKinsey research consistently finds 40%+ of executive transitions fail within 18 months, with the earliest months disproportionately shaping the outcome.
The first 90 days in any new role compress an unusual amount of signal into a short window. For a newly promoted Vice President, that compression is acute. Peer VPs, the executive leadership team, direct reports, and the boss are all forming their lasting impression of the leader in real time — and most of that impression is locked in before the leader has had a chance to deliver anything material.
McKinsey research and the Center for Creative Leadership consistently report that 40% or more of executive transitions fail within 18 months. The same studies repeatedly identify the same root cause: not capability shortfalls, but early misreads — declaring strategy too soon, missing political dynamics, hiring or firing too fast, or simply continuing to operate at the prior altitude. Michael Watkins's The First 90 Days (2003, updated 2013) put a name on the window. The mechanics underneath it are remarkably consistent across industries and functions.
In practical terms, the organization is deciding three things about a new VP during the first 90 days:
This is why the 90-day window is decisive even though it produces relatively little actual output. The output is the impression itself — and impressions set the gravity field that every subsequent move plays out in. A strong first 90 days creates organizational tailwind for the next 18 months. A weak first 90 days creates organizational drag for the same period.
Across many engagements with newly promoted Vice Presidents, Stratos Coaching sees a small, predictable set of mistakes account for the majority of derailments in the first 90 days. None of them are exotic. Each is rooted in a leader carrying forward the habits that earned the promotion into a role where those same habits become liabilities.
The single most common failure. The leader keeps doing the Director-level work because it feels productive, because they are good at it, and because the new VP-level work is ambiguous and slower. The calendar fills up with operational meetings the leader does not need to be in. The team learns to escalate decisions upward because the leader keeps making them. By day 60 the leader is exhausted, the team is dependent, and peers have quietly concluded that the new VP has not made the altitude shift.
A different failure pattern, often from leaders who feel the pressure to look decisive. They show up in the first two weeks with a strategy slide. The team listens politely. Peer VPs raise eyebrows. The strategy is almost certainly wrong — the leader did not yet have the context to be right — and walking it back later costs more credibility than the original silence would have.
The leader treats “politics” as a dirty word and refuses to engage with it — which is itself a political move, just an unaware one. Initiatives get blocked by peers whose incentives the leader never thought to map. Resources go to functions whose VPs spent more time building executive alliances. By day 90 the leader cannot understand why their function is structurally underfunded relative to its strategic priority.
The leader picks an early initiative that is either too large to ship in 90 days, too small to matter to executive stakeholders, or unaligned with the priorities the executive leadership team is actually optimizing for. The work is competent. The result is invisible. The 90-day window closes without a visible win the organization can attach to the new leader.
The underlying error that connects the first four. The leader assumes the VP role is the Director role with more scope, more headcount, and more meetings. It is not. The VP altitude is a categorically different job — setting direction, building the function, navigating the executive leadership team, and producing outcomes that cannot be directly controlled. Treating it as more of the same is the surest path to derailment. For the broader pattern, see our reference on the leadership transition from Director to VP.
The Stratos first-90-days protocol is the proprietary framework Stratos Coaching uses with newly promoted Vice Presidents. It is not a calendar. It is a sequence of four moves, each with a clear purpose, a specific practice, a predictable failure mode, and a definition of what excellent looks like. The four moves are run roughly in parallel across the 90 days, with different weighting in different windows of the arc.
The protocol is designed to do four things at once: prevent the most common derailments, accelerate the altitude shift from Director to VP, build durable political capital, and produce one visible win by day 90 that anchors the organization's perception of the leader.
A deliberately structured sequence of 30 to 50 one-on-one conversations in the first 30 days of the role, spanning direct reports, peer VPs, key cross-functional stakeholders, the boss, and a small number of external customers, partners, or vendors who interact with the function. The same five questions are asked in every conversation. Responses are captured in a private working document the leader returns to throughout the 90 days.
The listening tour does three things simultaneously. It produces context the leader could not otherwise acquire fast enough on their own. It signals to the organization that the leader operates by asking before declaring — which is itself an executive signal at the right altitude. And it establishes the relational footing the leader will need to draw on for the next 12 to 18 months. Skipping it, or running it informally, sacrifices all three.
Use the same five questions in every conversation. Vary the wording, but not the substance. A practical version:
Capture observations in a structured document — not just answers, but patterns across answers. The signal is rarely in any single conversation. It is in the convergence and divergence across many.
Two failure modes are common. The first is treating the listening tour as casual coffee meetings — warm relational conversations that do not produce structured insight. The second is using the listening tour as a stage to telegraph the leader's own views, which converts the conversations into one-way broadcasts and signals to stakeholders that the listening was performative.
The leader finishes day 30 with a written synthesis of the function's state, the cross-functional dynamics, the stakeholders who matter most, the patterns across many voices, and three or four specific hypotheses about what the function needs over the next 12 months — held loosely, ready to be revised. Stakeholders walk away from the listening tour conversations with the impression that the new VP listened harder than they expected, and that something will come of it.
The deliberate identification of the operating behaviors that earned the promotion, and the equally deliberate decision to stop doing them — replacing each with a VP-altitude behavior that develops the function rather than doing its work. This is the move new VPs underestimate most consistently, because the operator behaviors feel productive and the executive behaviors feel passive at first.
A new VP who has not made the identity shift is doing two jobs — the Director job they did before and the VP job they were promoted into. The Director work is more familiar and gets done first. The VP work is more ambiguous and gets pushed. By day 90 the leader is exhausted, the team has not stepped up because the leader has not stepped back, and peers conclude that the new VP is still operating. The shift is also what makes Moves 3 and 4 possible — a leader who is still operating does not have the time or the room in their head for political mapping or strategic bet selection.
Three concrete behavioral cues to watch in the first 60 days:
For the wider pattern across all four senior leadership capabilities — strategic thinking, executive presence, political fluency, and strategic communication — see our reference on executive coaching and the altitude transition framework.
The most common failure is not refusing to make the shift. It is making it partially — delegating some of the operating work but keeping the parts the leader is best at and most identified with. That residue is enough to keep the team dependent and the leader stretched. The shift has to be made cleanly to land. A coach with prior VP operating experience is often what makes the cleaner version possible — see VP & SVP coaching.
By day 60, the team is making operating decisions without escalating. The leader is spending most of their time on cross-functional alliance work, function-level direction, and one or two high-leverage initiatives. Direct reports describe the new VP as “the person who asks the question I should have asked myself.” The leader has visible thinking time on their calendar and is not the bottleneck for the function's day-to-day output.
A written map of every executive whose support, neutrality, or opposition materially affects the new VP's function — usually 8 to 15 people. For each, the leader captures stated priorities, unstated incentives, current standing with the new VP, and the fault lines between this person and other senior stakeholders. The map is updated weekly through the 90 days and remains a working document well past them.
At VP altitude, the majority of consequential work happens through peers and stakeholders who do not report to the new leader. Resourcing, strategic priority, cross-functional execution, headcount, and the ability to ship an early bet all depend on alliances the leader either builds or doesn't. Leaders who treat “politics” as something they refuse to engage with are not being above the fray — they are simply playing the game badly. The map is the difference between political fluency and political blindness.
For each name on the map, capture four fields:
Invest the first 60 days in alliance-building and fault-line detection — not in advancing any agenda that requires the stakeholders' support. Trying to push the agenda before the map is built almost guarantees that one of the unmapped fault lines will block the work.
Two failure modes recur. The first is moral squeamishness about “politics” — treating the map as something dirty rather than as the basic geography any senior leader operates inside. The second is building the map only of the people the leader already likes, which misses precisely the stakeholders whose neutrality or opposition will determine outcomes. For a deeper treatment, see political fluency for senior leaders.
By day 60, the leader can describe each of the 10 to 15 executives on the map with specificity — their priorities, their unstated incentives, where they currently stand, and which fault lines run between them. The leader has had at least one substantive 1:1 with each, has identified two or three durable alliances, has named the one or two stakeholders most likely to oppose their early bet, and has decided how to route around or address that opposition before the bet is announced.
A single, tightly scoped, visible initiative that the new VP commits to delivering inside the 90-day window. Not three. Not five. One. The bet is selected after enough of the listening tour and political map have been built to make a sound choice — typically late in days 30 to 60. It is scoped, resourced, and shipped in the final 30 days.
The 90-day window has to close with something the organization can attach to the new leader. Without a visible win, the impression that solidifies is “competent, thoughtful, hard to point to anything specific yet.” That impression compounds. With a visible win — even a modest one — the impression becomes “new VP shipped something credible inside 90 days,” which buys runway for the larger initiatives the function actually needs over the next 12 to 18 months.
Four filters for selecting the early bet:
Scope it explicitly in writing before announcing it — the deliverable, the success measure, the stakeholders, the date. Resource it with the team's strongest people, not a side project staffed with whoever was available. Pre-socialize the bet with the two or three stakeholders most likely to influence its reception. Ship it before the end of the 90-day window, not on the boundary. Then use it — explicitly — as the anchor point in the leader's first ELT-level update.
The two recurring failures are picking too large a bet (work that cannot finish inside 90 days), and picking the wrong bet (work that does not map to any stakeholder's stated priority and therefore lands without resonance even when it ships). The political map from Move 3 is what makes the second failure avoidable.
By day 90, the bet has shipped, the executive leadership team has heard about it from sources other than the new VP, and at least one peer VP is using it as evidence that the new leader is “the real thing.” The bet is small enough to have shipped and visible enough to have mattered. The leader has a concrete artifact to anchor the next twelve months of larger work to.
The four moves do not happen in clean sequence. They run in parallel across the 90 days, but with different weighting in different windows. A practical view of where the focus should shift:
| Window | Primary focus | Secondary focus | What to avoid |
|---|---|---|---|
| Days 1–30 | Structured listening tour. 30 to 50 one-on-ones. Pattern capture across many voices. | Begin the identity shift. Notice operator instincts and redirect them. | Strategy declarations, restructures, hiring or firing decisions, public commitments. |
| Days 30–60 | Political map. Stakeholder mapping, alliance building, fault-line detection. | Begin scoping the early bet. Continue identity work. | Picking the bet too early, before the map is complete enough to choose well. |
| Days 60–90 | Ship the early bet. Scope, resource, pre-socialize, deliver. | Begin the longer-arc strategy work that will surface in months 4 to 9. | Adding a second bet. Scope creep on the first one. Skipping the pre-socialization. |
The cleanest way to fail this arc is to invert it — ship the bet first, build the political map second, do the listening tour third, and start the identity shift sometime around month 6. That sequence is unfortunately common.
Formal feedback at VP altitude is slow and lagging. A new VP cannot wait for the annual review to find out whether the role is landing. The most useful signals are informal and largely behavioral — they show up in how stakeholders treat the leader, not in what they say to the leader's face.
Leading signals that the first 90 days are landing:
Warning signals that something is off:
If multiple warning signals are present at week 6, treat it as a forcing function to run a reset (see below) rather than wait for the warning to become formal feedback. The cost of catching the drift at week 6 is small. The cost of catching it at month 6 is much larger.
An external VP hire and an internally promoted VP run essentially the same protocol, but the failure modes are different. External hires have to compress the listening tour faster because they lack the institutional context internal hires arrive with — they typically need to add 5 to 10 conversations in the first 30 days, including with the people who were finalists for the role. They also start with less political capital and have to build the map of stakeholders from a colder start.
Internal hires face a different problem: stakeholders already have a model of them at the previous altitude and tend to hold them to it. The identity shift is harder, because every peer remembers the leader as the Director who used to handle a specific kind of work. Internal hires have to work explicitly to claim the new altitude — declining to engage with the operating work they used to own, declining to be looped into the conversations they used to lead, and being visibly comfortable with the slower rhythms of executive work.
A new VP who is also new to the industry or the function has to acknowledge that lack of context in the listening tour itself rather than try to hide it. Stakeholders will respect a leader who says explicitly “I am asking more questions early because I want to be slow before I am fast.” They will not respect a leader who pretends they already know. The political map for a pivot VP often needs to extend further out — to industry peers, advisors, and former colleagues at adjacent companies — because the internal map alone will not produce the context the leader needs to make sound calls.
A founding VP role — first VP of Engineering, first VP of Product, first VP of Sales — bends the protocol in two ways. The political map collapses to a much smaller number of names (the founders, the existing leadership team, the lead investors), and the early bet is often less about shipping a discrete initiative and more about installing the foundational operating system the function will scale on (hiring, planning cadence, performance management). The listening tour and identity shift remain just as critical, though the listening tour weights more heavily toward investors and founders and the identity shift is from doer-builder to scaler-builder rather than Director to VP.
If a new VP reads this at week 6 or week 8 and recognizes that the early weeks have been spent operating, declaring, or running flat at the wrong altitude, the right move is not to grimly carry on. It is to run a structured reset — explicitly named, communicated, and executed.
The reset has three parts:
A clean reset at week 6 costs almost nothing. The same drift continuing to week 24 typically costs the role.
Run a structured listening tour, make the identity shift from operator to executive, map the political landscape, and ship one tightly scoped early bet by day 90. The window is not for declaring strategy or restructuring — it is for earning the right to do so. The first 30 days are listening; days 30 to 60 are political mapping and identity work; days 60 to 90 are scoping and shipping one visible win.
McKinsey and Center for Creative Leadership research consistently finds that more than 40% of executive transitions fail within 18 months, and that the early months disproportionately shape the outcome. The organization forms its lasting impression of a new VP during this window — whether they operate at executive altitude, whether they can be trusted with larger scope, and whether their early moves signal sound judgment.
Five recurring mistakes: continuing to operate at Director altitude, declaring strategy before listening, ignoring political dynamics, picking the wrong early bet, and treating the VP role as a bigger Director job. Each is rooted in the same underlying error — failing to recognize that the altitude shift is a change in the nature of the work, not a change in scope.
Almost never. The only major changes a new VP should make in the first 30 days are addressing genuine emergencies — active customer escalations, severe performance issues that predate the leader, regulatory or safety risks. Reorgs, strategy declarations, hiring or firing decisions, and process overhauls should wait until the listening tour and political map are complete.
External hires need to compress the listening tour faster because they lack institutional context, and they have to build political capital from a colder start. Internal hires face the opposite problem — being held to operating standards from their previous role and struggling to claim the new altitude. External hires get a clearer reset; internal hires must work harder to earn one.
Moving from operating the work to leading the leaders who operate the work. Directors are rewarded for execution depth, hands-on problem-solving, and personal output. VPs are rewarded for setting direction, developing the function, building cross-functional alliances, and producing enterprise outcomes that cannot be directly controlled. The most common failure is doing both jobs — keeping the Director work and adding the VP work on top.
Leading signals: unsolicited inclusion in strategic conversations; peer VPs proactively bringing problems to them; the boss consulting rather than directing; the team operating without escalation; stakeholders citing the VP's framing rather than their own. Lagging signals — formal 360s, performance reviews, headcount approvals — typically arrive too late to course correct.
Run a reset. Acknowledge the drift to your boss, run a compressed two-week listening tour, and redraw the 30/60/90 plan with the clock effectively reset. Bosses respond well to a leader who diagnoses their own error and proposes a credible correction. The reset is far less damaging than continuing on the wrong track for another 60 days.
Ninety days is the window in which the organization forms its first impression, not the window in which the role is fully landed. Full landing typically takes six to twelve months — long enough to ship two or three meaningful initiatives, complete an annual planning cycle, and accumulate enough cross-functional surface area for stakeholders to know the leader by reputation. The 90-day window is decisive because it sets the trajectory of the longer arc.
For most newly promoted VPs, yes — and the case is strongest in the first 90 to 180 days when stakes are highest and the cost of misreads is largest. A coach with prior VP or SVP operating experience accelerates the listening tour, sharpens the political map, and prevents the most common identity-shift failures. Coaching at this stage is the cheapest available form of risk mitigation against the 40%+ executive transition failure rate. See VP & SVP coaching for the dedicated engagement.
Stratos Coaching is a premier executive coaching firm working 1:1 with Vice Presidents, Senior Vice Presidents, and C-suite leaders. Our coaches have actually held the seats — 25+ years of enterprise leadership experience, including time in VP, SVP, and C-suite roles inside Fortune 500 companies. The first-90-days protocol is the spine of our VP & SVP coaching engagements. Every engagement begins with a free 30-minute strategy conversation.
Related reading: What is executive coaching? · Leadership transition coaching · Our engagement structures · First 90 days field notes · First 90 days — the operator’s view · First 90 days at altitude · Notes for first-time VPs
This reference is published by Stratos Coaching under Creative Commons Attribution 4.0 (CC BY 4.0). When citing, please attribute to “Stratos Coaching” with a link to stratoscoaching.com. The Stratos first-90-days protocol, the altitude transition framework, the four capabilities of senior leadership, and the four-behavior model of executive presence are proprietary frameworks of Stratos Coaching, published for open educational use.