The First 90 Days as a New CMO or VP Marketing

Your first instinct in a new marketing leadership role is to prove you were the right hire. That instinct, acted on too fast, is exactly what gets new leaders fired within a year.

Quick Summary

• The most common and costly mistake new marketing leaders make is jumping into execution mode too quickly, before understanding what is actually broken versus what merely looks broken.
• "What's broken on the surface is rarely the root issue," meaning the campaign that looks weak is often a symptom of a stack, process, or team gap underneath it.
• A frequent trust-killer: new leaders quietly evaluate a team member's replacement before genuinely trying to learn what that person actually does and why.
• Average CMO tenure sits around 4.1 years industry-wide, which makes the first 90 days disproportionately important, a bad start rarely gets fully recovered from.
• The framework that separates leaders who last from leaders who don't is simple to state and hard to follow: listen first, diagnose the system, then act, in that order.

The Listening-Tour vs. Quick-Wins Tradeoff

Every new leader feels pressure to show a win fast. The mistake is picking a visible, easy win before you understand whether it is the right one.

Spend the first three to four weeks doing structured listening: 1:1s with every direct report, a handful of skip-levels, and conversations with sales, product, and finance about how they experience marketing's output. Write down patterns, not opinions, three different people independently flagging the same bottleneck is a real signal.

By week six, you should be able to state the top three problems in one sentence each, in language your CEO would recognize. If you cannot, you are still listening, not diagnosing, and that is fine, just do not skip ahead.

Auditing Team, Stack, and Pipeline Before Changing Anything

Three audits happen in parallel during the listening phase, not sequentially, because they inform each other.

Team audit: who owns what, who is actually strong versus who is just loud, and where real skill gaps sit versus where the org chart just looks wrong on paper. Resist reorganizing the team before this audit is done, a premature reorg signals you did not bother to learn who people are first.

Stack audit: what tools are licensed but unused, what data actually flows between systems versus what the diagram claims flows, and where manual workarounds have quietly become "how we do things." Overlapping martech licenses are one of the most common, and most politically easy, first fixes once mapped.

Pipeline audit: where deals or conversions actually stall, using real data rather than the story people tell about the funnel. This audit alone often reveals whether marketing's real problem is lead volume, lead quality, or a downstream sales capacity issue nobody wants to say out loud.

Only after all three audits converge should you propose structural changes. Moving fast here without the data is how a new leader inherits blame for problems they did not cause and could have avoided by waiting three more weeks.

Classic Mistakes That Burn Trust Fast

Replacing people before understanding their role. New leaders sometimes start quietly evaluating a team member's replacement in week two, before genuinely learning what that person does day to day, and the team can tell.

Mistaking visibility for value. Rebranding the newsletter or refreshing the deck template feels like progress and photographs well, but it does not move the metric the board is watching, and everyone eventually notices the gap.

Announcing a strategy before the audit is done. A confident 90-day plan delivered in week three, before the team and stack audits are finished, reads as arrogance even when the instincts turn out right.

• Do not criticize the previous leader's work publicly, even when it deserves it, your team likely built it and still feels ownership.
• Do not skip the finance and sales relationship, marketing's credibility with the CFO is set in the first quarter and is expensive to rebuild later.
• Do not over-promise a timeline for results you cannot yet control, given the audits are still running.

Key Takeaways

• Spend the first three to four weeks listening structurally, one small low-risk win is fine, save strategic bets for after diagnosis.
• Run team, stack, and pipeline audits in parallel, they inform each other and prevent premature restructuring.
• Ask for raw dashboard access immediately rather than trusting a curated handoff deck.
• Never quietly evaluate replacing a team member before genuinely understanding their role.
• Resist announcing a full strategy before the audit is complete, even a well-reasoned plan lands badly if it looks premature.