What actually matters in your first 90 days as a new VP?

The most common mistake in a first 90 days as a new VP is trying to demonstrate value by changing things quickly. The VPs who succeed in their first year usually spend the first 30-45 days doing something much less visible: building an accurate map of how the organization actually works, as opposed to how the org chart says it works.

Why the "quick wins" instinct backfires

Changing a process, a team structure, or a strategy before you understand why it exists in its current form often means undoing something that was a deliberate response to a problem you don't know about yet. The team usually knows this, even when they don't say so directly — and a fast, wrong change costs you credibility faster than a slow, careful one costs you time.

What to actually spend the first month on

One-on-ones with everyone on your team, and with the peers and stakeholders your role depends on, focused on one question: "what's working well that I should be careful not to break, and what's not working that you'd fix if you had the authority to." The pattern across these answers tells you more than any dashboard will in month one.

The trust-building move that actually works

Find one real, specific problem in your first month — ideally something your team has been frustrated by for a while — and fix it visibly and quickly, without a big announcement. This does more for your credibility than a strategic vision deck, because it demonstrates you listen before you act, which is the exact quality a new VP most needs to prove.

The mistake to actively avoid

Comparing your new team unfavorably to how things worked at your last company, out loud, in the first few months. Even when the comparison is accurate, it reads as disrespect for what people built before you arrived — and it's one of the fastest ways to lose a team's trust before you've earned the right to change anything.