Your First 30/60/90 Days as a New PMM

You walked in expecting to find a positioning doc. What you actually got: a Notion page last edited 14 months ago, a sales deck the AEs already ignore, and three Slack DMs from PMs asking when the launch brief for the Q3 release will be ready. Deals are closing despite the messaging, not because of it. Welcome to product marketing.

The first 90 days of a new PMM role aren't about brilliance. They're about not blowing up your political capital before you have anything to spend it on. By day 90 you want three things: shipped artifacts the company can point to, a real win-loss data set nobody else in the building has, and an H2 roadmap with named buy-in. Get those, and you've earned the right to say no later. Skip them, and six months in you're "the launch coordinator," which is a polite title for a career dead-end.

Here's how to actually do it.

Why 30/60/90 matters more for PMM than for any other role

Engineers have story points. Sales has quota. CS has retention. PMM has... vibes. There's no built-in scoreboard, which means if you don't define your own milestones, someone else will define them for you, and they'll define them as "did you write the deck for next Tuesday's launch."

The 30/60/90 isn't a corporate ritual. It's the only mechanism that protects you from becoming a launch concierge. You're committing publicly to a sequence: listen, then ship something small, then own something real. Each phase earns the right to the next one. Skip listening and your positioning will be ignored. Skip the small ship and nobody trusts you with the big one. Skip the launch and you're still "the new PMM" at month six.

Write your 30/60/90 down in week one. Send it to your manager. Reference it in every 1:1.

Days 1–30: Listen, don't ship

The biggest mistake new PMMs make is showing up in week two with a positioning rewrite. Nobody asked. Nobody trusts your opinion yet. And you don't actually know enough to be right.

Spend the first 30 days listening, hard. Three concrete deliverables, in this order.

Run 10 win-loss interviews

Five wins, five losses. Not the easy "champion loved us" calls. The messy ones. The deal that closed because the buyer's hand was forced by a contract renewal elsewhere. The loss where the AE swears it was price but the prospect actually hated the implementation timeline.

A workable interview guide is twelve questions, 30 minutes, recorded with permission:

1. Walk me through the moment you decided you needed to solve this.
2. What did you try first, before evaluating tools?
3. Who else was in the room when you made the call?
4. What were the two or three vendors that made the shortlist?
5. What did you Google on the way to the shortlist?
6. What was the one thing on our website that made you take us seriously? (Or skip us?)
7. Walk me through the demo. What worked, what didn't?
8. What objection almost killed the deal internally?
9. If we had been $20K cheaper, would you have picked us? (Or: if you'd been $20K richer?)
10. What's the first thing you wish we'd told you that we didn't?
11. Six months in, what do you wish was different?
12. If a peer asked you about us tomorrow, what would you say?

Block 90 minutes per call: 30 to interview, 30 to write up, 30 buffer because every fifth call goes long. Schedule them in week two so they're done by day 28. Yes, sales will resist handing over their lost deals. Tell them you'll share the synthesis. Then actually share it.

Audit existing positioning and messaging

Pull every customer-facing artifact you can find. Website hero, pricing page, top three blog posts, sales deck, one-pager, demo script, ABM email sequence, the LinkedIn ad currently running, the CEO's last podcast appearance.

Score each one on two axes: clarity (would a stranger understand what we sell in 30 seconds?) and consistency (does it match what the other artifacts say?). Use a 1–5 scale. Make a spreadsheet. The number on the page is the point.

You're going to find that the website says "AI-powered platform," the deck says "operating system for revenue," the CEO says "we automate the boring stuff," and sales says "honestly, we're like HubSpot but cheaper." This is normal. Don't fix it yet. Document it.

Sit on five live demos

Camera off, mic muted, in the background. No notes to the AE afterward. You're not there to coach. You're there to listen for the moments where the rep goes off-script and why.

Track three things per demo: the question that made the rep pause, the slide they skipped, and the moment the prospect leaned in. Patterns across five demos will tell you more about your real positioning than any internal doc.

One-pager: "What I heard in 30 days"

Day 30 (or 32, nobody dies if it slips). One page. Not the whole company. Share with your manager, the PM lead, and the sales lead. Three sections:

• What we say vs. what buyers hear (with two or three direct quotes from interviews).
• The biggest gap I'm seeing (one paragraph, not a manifesto).
• What I'd like to test next 30 days (one specific thing).

Resist the urge to recommend a positioning rewrite in this doc. You haven't earned the credibility yet. The doc's job is to prove you listened.

Days 31–60: Ship something small, prove the loop

Now you ship. The point of this phase isn't to ship the right thing. It's to prove you can ship anything. Three small artifacts, all internal-facing, all reversible.

Rewrite positioning v1 as an internal draft

Not a launch. Not a website rewrite. An internal Google doc, maybe four pages, that fills out a positioning canvas: the problem, the audience (be specific; "VPs of RevOps at 100–500 person SaaS companies" beats "B2B leaders"), the alternatives buyers consider, your unique value, and the proof points that back it up.

Send it to three people: your manager, the head of sales, and the head of product. Ask for written comments by a specific date. You'll get conflicting feedback. That's the data you wanted. Now you know who disagrees about what.

Don't try to reconcile all of it in v1. Pick one of the three perspectives to anchor on (usually sales, since they're closest to the buyer) and note where you're choosing not to address the others yet. Camellia's rule: positioning v1 is a hypothesis, not a treaty.

Refresh one enablement deck

Pick the one sales actually opens. Ask the AEs which deck they pulled up most last quarter. It's almost never the deck the previous PMM was most proud of.

Refresh, don't rebuild. Keep the structure the AEs already know. Replace stale customer logos. Update the competitive slide. Cut three slides nobody uses. Add one slide that addresses the top objection from your win-loss work. Run it past two reps before shipping.

If the deck has 47 slides and nobody opens it, the answer isn't to make a better 47-slide deck. It's to ship a 12-slide version and let the long version die quietly.

Run one launch retro on a recent release

Pick a release from the last 90 days, even if you weren't there for it. Talk to the PM, the AE who got the most demo requests, and one customer who actually adopted the feature. Twenty minutes each.

Surface the gap between what shipped and what the market heard. Almost every retro turns up the same pattern: the engineering scope was real, the launch was a blog post and a Slack message, and three months later half the sales team can't describe the feature. That gap is your job. The retro doc is how you make it visible.

This artifact does double duty: it gives you a credible reason to be in launch planning meetings going forward.

Days 61–90: Own a launch, present positioning v2, propose the roadmap

Days 61–90 are when you go from "the new PMM" to "the PMM." Three things, in this order.

Lead one tier-2 launch end-to-end

Not the flagship. Earn that later. A tier-2 launch — a meaningful feature, not a flagship product release — is the right scope. You own the brief, the messaging, the enablement, the customer comms, and the post-launch retro. You set the bar on what "launched" means and you defend it when engineering asks to skip enablement because the deadline slipped.

Two principles for the launch:

• Start the brief at spec stage, not GA stage. If the PM hands you a launch on Friday and asks you to "do the marketing," push back. The brief should be drafted while the spec is being written. Day-of marketing is not a thing.
• Define done before you start. "Done" is not "the blog post went live." Done is: AEs can describe the feature in one sentence, the demo flow is updated, the customer-facing release notes are out, and there's a retro scheduled for two weeks post-GA.

Present positioning v2 to leadership

Backed by win-loss quotes (you have ten, use them) and a competitive teardown (one slide per major competitor: how they position, where buyers see them as different, where buyers see them as the same as us). This is where positioning v1 stops being your hypothesis and starts being the company's hypothesis.

Get named buy-in before the meeting, not in it. Walk it past sales lead and product lead privately first. Adjust based on their feedback. The leadership presentation should be a confirmation, not a debate. Surprise positioning meetings are how positioning dies.

Propose the H2 PMM roadmap

One page, three priorities. For each priority: what you're going to ship, what you'll measure, and what success looks like at the end of H2.

Then the part that scares people: a section called "what I'm saying no to." List three things the company will ask you to do that you won't do. Maybe it's "writing the weekly sales newsletter" or "owning customer marketing email" or "running the partner co-marketing program." Whatever it is, name it now. Saying no in writing in your H2 plan is 100x easier than saying no in a Slack DM in week 14.

Add a final section on what you need to deliver: headcount (probably none yet), tools (probably one or two), budget (be specific). The CFO doesn't read aspirational roadmaps. They read numbers.

Three real-world traps that kill new PMMs

Trap 1: Positioning by committee

The CEO loves "platform." The head of sales wants "easy to deploy." The head of product is fixated on "AI-native." You write a v1 doc; each one of them rewrites it in a different direction. By v4 you're producing a Frankenstein paragraph that satisfies all three executives and resonates with zero buyers.

The fix isn't to have stronger opinions. The fix is to anchor on one source of truth that overrides internal preferences: the actual words real customers used in your win-loss interviews. When the CEO wants "platform" and three of your won-deal champions said "the thing that finally got marketing and sales onto the same data," the answer to the CEO is "here are the exact words our buyers used; can we test that first?"

You're not arguing with the CEO. You're handing them better data than they have.

Trap 2: "Sales says one thing, the website says another"

You'll notice this in week three and want to fix the website immediately. Don't.

Fixing the website first gives you a perfect home page that nobody on the sales team uses. The AEs keep saying their thing because their thing is what worked on their last 20 calls. Your shiny new hero copy isn't going to override 20 reps of muscle memory.

The right order is: positioning v1 (internal), enablement deck refresh (so AEs have a better thing to say), pilot the new language with two or three reps in live calls, gather feedback, then update the website. By the time the website changes, the sales team is already saying the new thing. The website becomes confirmation, not contradiction.

Trap 3: Getting pulled into every launch as "the PMM"

By week six you'll be invited to four launch planning meetings a week. Each one is a small ask ("just review the messaging"), but each one ends with you owning a deliverable. That's how you become the launch coordinator.

The fix is your H2 roadmap. Once you've defined three priorities and named what you're saying no to, you have an artifact to point at. "I'd love to support that, but it isn't in my H2 priorities; want to walk through how we'd reshuffle?" Almost nobody actually wants to reshuffle. They want a quick yes. The roadmap gives you a structured no.

Day 90: How you know it worked

You don't measure success by the number of decks shipped or interviews logged. You measure by whether the company changed its behavior.

Three signals to look for:

• AEs quote your messaging in calls without being prompted. Not the deck. The actual sentences. Sit on a demo in week 13 and listen for it.
• PMs bring you in at spec stage, not at launch stage. When the next product brief lands in your inbox eight weeks before GA instead of eight days, you've earned the seat.
• You've said no to at least one thing in writing, and the building accepted it. This is the real test. Saying no without consequences means the H2 roadmap stuck.

Plus the leading indicator: positioning v2 has named buy-in from sales lead and product lead, not just your manager. If those names are on the doc, the company has a positioning doc again. That's the deliverable.

Ninety days isn't enough time to fix the messaging. It's enough time to earn the right to fix it. Spend the time accordingly.

Learn More

• Product Marketing Manager Job Description
• How to Run Win-Loss Interviews That Sales Will Actually Use
• Positioning v1: From Notion Doc to Sales-Ready
• Sales Enablement: What PMM Actually Owns