The First 90 Days as a New Marketing Hire: A Diagnose, Build, Ship Playbook

In your first 90 days as a new marketing hire, the trap is that you'll feel pressure — from yourself, your manager, sometimes your skip-level — to ship a flagship campaign by week four. Don't. The marketers who actually get promoted within their first 18 months are the ones who spent weeks one through 30 listening, weeks 31 through 60 building one focused thing, and weeks 61 through 90 shipping one named result. Diagnose, build, ship. In that order, with hard time-boxes.

The reason this sequence works isn't culture or politeness. It's that the dashboard you walk into on day one is lying to you in some specific way that you can't yet see, and your week-four campaign — the one your boss seems to want — will land on top of that lie. Six months later, when the campaign metrics underperform, the post-mortem will pin it on you, not on the broken attribution you inherited.

So before you do anything, you diagnose.

Phase 1: Diagnose (days 1–30)

The diagnose phase has one goal: find out what's actually true. Not what the dashboard says, not what your manager's running narrative says — what's actually true.

Three concrete moves in the first 30 days:

• Read the last four quarters of marketing reports cover to cover. Not the slide decks shown to leadership — the working documents the team used internally. Look for the gap between what was projected, what was reported, and what the audited number turned out to be. That gap is where the broken assumptions live.

• Get a 30-minute meeting with one person on each adjacent team. Sales (or BD), product, customer success, finance, data. Ask each one the same two questions: "What does marketing get right that I should keep doing?" and "What does marketing get wrong that I should fix?" Take notes verbatim. Patterns will emerge by your fifth meeting.

• Pick one number on the team's main dashboard and audit it end-to-end. Pick a number you'd describe to a non-marketer in one sentence — like "MQLs last month" or "blended ROAS Q3." Then trace it back through the SQL or the platform export. The audit will surface whether your team is operating on real measurement or shared fiction. This single exercise is the most diagnostic thing you can do in your first month, and most new hires never do it.

You're not making decisions in the diagnose phase. You're collecting evidence. The deliverable at the end of day 30 is a one-page memo to your manager: here's what I learned, here's what I think the real problem is, here's what I want to spend the next 60 days on. The memo is also your protection — it documents the inheritance you walked into, separate from any results you produce later.

Phase 2: Build (days 31–60)

In days 31–60, you pick one thing — one campaign, one experiment, one fix — and own it end-to-end. Not three things. Not a portfolio. One.

The best one to pick has three properties:

• It's small enough that you can finish it inside this 30-day window without inheriting anyone else's roadmap.

• It produces a number that ties to a metric your CFO recognizes — pipeline, payback, gross margin, retention rate. Not "engagement," not "brand lift."

• It tests one of the broken assumptions you found in your diagnose memo. The whole point is to take a thing your team believes and put a real number against it.

For example: your diagnose memo concluded that the team has been over-investing in branded paid search because the "ROAS" was last-touch and never tested for incrementality. Your build phase is a two-week regional holdout where you turn off branded bidding in one geo and watch what happens to total branded sessions and bookings. That's it. One experiment, one number, one decision.

While you're building, write down the assumptions that made the experiment possible — the test design, the control geo, the holdout duration, the success threshold — before the data comes in. This is how you protect yourself from the bad version of post-hoc analysis where the team either claims success or moves the goalposts after the result.

Phase 3: Ship (days 61–90)

In days 61–90, the one thing you built has to ship: a real decision, a real budget reallocation, a real change in process. The result of your experiment is the input. The output is one named, measurable change to the business.

Three concrete moves:

1. Write the one-page result memo, with the number front and center. Lead with the headline metric and the dollar implication, in that order. "Branded paid search holdout: -2% branded sessions, $480K of annualized media saved if rolled out company-wide." Bury the methodology footnotes at the end. The memo is the artifact your skip-level forwards to their boss. 2. Get one cross-functional sponsor before you announce. Walk the memo over to whichever adjacent leader benefits most — usually finance, sometimes sales, sometimes product. Their endorsement turns your result from "the new marketer's pet experiment" into "a finance-co-signed cost-out story." This step matters more than the result itself for whether anything actually changes. 3. Make the change reversible. Frame the rollout as a 90-day pilot with a tripwire — "we'll roll back if branded sessions drop more than 10%." A reversible decision is one your manager can bless quickly. An irreversible one stalls in committee for months.

By day 90, the deliverable is not a campaign. It's a memo, a decision, a sponsor, and a tripwire. That's the artifact set that gets you promoted, and it's the same artifact set that gets you a great reference if this role doesn't work out.

What to do this week

If you're already in your first 90 days, three things you can do this week:

• Pick the one number on your team's dashboard you'd most want to be able to defend, and start the audit. Most teams have at least one number nobody has reverse-engineered in 18 months.

• Schedule the five adjacent-team conversations. Not lunches, not all-hands, just 30-minute 1:1s with the same two-question script.

• Block out the next four Fridays for memo-writing. The number-one reason new hires don't ship a memo at day 30, day 60, and day 90 is that they didn't book the time. Book the time.

If you're not in your first 90 days yet — if you're interviewing or about to start — bring this framework to your final interview. Ask your hiring manager: "If I'm in the role on day 90, what's the one named result you'd want me to have shipped?" The answer tells you whether the company has actually thought about your role, or whether they're going to dump three roadmaps on you the day you start. Either answer is useful.