The PM 30/60/90

Starting from zero is an advantage for about 90 days

Every new PM job starts the same way: you know nothing, nobody trusts you yet, and everyone is too busy to onboard you properly. The standard advice is to schedule coffee chats and absorb. That advice wastes the one advantage you will never have again: for about 90 days, you are the only person in the building who can see the product without the org's story wrapped around it. After that, you have a story too.

I have started over enough times, Microsoft to Adobe to Salesforce to four startups to Smartcat, to know the window closes fast. This chapter is the plan for spending it well. It is the sibling of The Builder PM 30/60/90, which covers transforming a role you already have. This one covers landing in a role you don't understand yet.

The short version

The PM 30/60/90 for a new job runs in three moves. Before day 1 and through days 1 to 30: set up your personal stack before you start, run decision archaeology on the last 90 days of your product area, build a signal map instead of a stakeholder map, and write a manager contract in week one. Days 31 to 60: ship one compounding artifact, a call synthesis, a live dashboard, an eval set, or a debate-ending prototype, and use it to earn your seat in decision rooms. Days 61 to 90: take ownership of one bet with a falsifiable success measure, kill or renegotiate one inherited commitment, and write a day-90 note to your manager that sets the scoreboard for the next year. Templates for the contract, the signal map, and the day-90 note are in the PM First-90 Kit(coming Jun 13).

Day zero: infrastructure before access

You do not need a company laptop to start. Three setups before day 1.

Stand up your second brain. A notes system with a daily capture habit, so the firehose of your first weeks gets stored somewhere queryable instead of evaporating. Mine is described in the PM second brain. The first month of a new job is the highest-value input stream of your tenure and most PMs let it run straight to the floor.

Start your prompt repo and agent scaffolding. The synthesis agents you will want in week three, call synthesis, doc digestion, meeting summaries, take an evening to set up and zero company data. Build them now on public material. The full setup is in the PM agent stack.

Use the product as a customer. Personal email, real task, hit the paywall, file a ticket. Write down everything that confused you. In six weeks you will be incapable of this read. It is the cheapest user research you will ever produce and it makes your first customer calls ten times sharper.

Days 1 to 30: archaeology, not coffee chats

You will be told to "meet everyone." Fine, meet them. But structure the month around evidence, not introductions.

Run decision archaeology. Reconstruct the last 90 days of your product area: merged PRs and what shipped, launch posts, the killed projects, the escalations, the pricing or packaging changes. For each significant decision, trace who raised it, where it got debated, who actually decided, and what evidence was in the room. Two effects. First, you learn how the org really works, which never matches the wiki. Second, within three weeks you are the best-informed person in most meetings about recent history, which is a strange and useful kind of credibility for someone with no tenure.

Build a signal map, not a stakeholder map. A stakeholder map tells you who has power. A signal map tells you where truth enters the building: which support queue, which sales call recordings, which dashboard, which customer Slack channel, which engineer who quietly knows everything. Your job long-term is to sit closer to the signal than anyone else. Find the sources in month one and subscribe to all of them. Route them into a daily digest the way Continuous Listening describes.

Write the manager contract in week one. One page, co-written with your manager: what you own, what good looks like at day 90, how decisions get made between you, what they are silently worried about. Ask that last one directly. Most PM onboarding failures I have witnessed were expectation mismatches that were never written down, discovered at month four, fatal by month six. The contract converts an ambient vibe into an editable artifact. Template in the PM First-90 Kit(coming Jun 13).

Sit in eight raw customer calls. Before reading anyone's synthesis, form your own. The interview guide gives you the structure. Feed the transcripts to your synthesis agent and compare its read with yours and with the team's official narrative. The three-way gap is your first real discovery.

What you do not do in month one: share conclusions, propose strategy, or critique the roadmap. Observations and questions only. The deep dive on this month is the PM first 30 days, mapped(coming Jun 12).

Days 31 to 60: ship one compounding artifact

Month two is where you convert evidence into standing.

The standard advice says find a quick win. Quick wins are usually stunts: small enough to be ignored, cosmetic enough to be resented, forgotten by the next sprint. Ship an artifact instead. An artifact keeps working after you ship it.

Four proven options, pick the one your team's weather calls for:

The synthesis. Twenty customer calls, synthesized into themes with verbatim quotes and one recommended action each, delivered to the team. Costs you two days with the agent stack you built at day zero. The call triage recipe is the exact pipeline.

The eval set. Take the next feature on the roadmap and write its eval set before anyone asks. Thirty to 150 labeled examples that define what good looks like. You just became the person who defines quality for that feature. The Eval Is the Spec is the method.

The live page. One URL with the signals the team currently assembles by hand every week: adoption, eval scores, cost, open customer themes. The staff meeting dashboard pattern(coming Jun 25) shows what this replaces.

The prototype. Find the debate that has been circling for weeks and end it with two working prototypes built in an afternoon. Prototype Before You Spec is the craft; 60 minutes is enough is the proof.

Ship it, then watch the reactions. Who used it, who ignored it, who got defensive. That reaction data feeds the same coalition logic a CPO runs at larger scale in The CPO 30/60/90. The month is broken down in days 31 to 60, first artifact(coming Jun 22).

Days 61 to 90: own a bet

Month three converts standing into ownership.

Take one bet and put your name on it. Not the whole roadmap. One outcome with a falsifiable success measure and a date: "activation for segment X moves from A to B by date Y, and here is the evidence this is the right lever." Write it as a one-pager. Socialize it through the signal map you built. This is the moment you stop being new.

Kill or renegotiate one inherited commitment. Every PM inherits at least one commitment that the evidence no longer supports: a promised feature, a standing report, a ceremony. Pick the safest one, lay out the evidence, and either kill it or renegotiate it openly. Doing this once, calmly, with receipts, teaches the org how you operate and makes every future no cheaper. The mechanics live in the anti-backlog.

Write the day-90 note. One page to your manager: what you found, what you shipped, the bet you own, what you killed, and what you want to be measured on for the next year. This closes the manager contract from week one and opens the next loop. It is also, quietly, the first draft of your next promotion case. Structure in the PM First-90 Kit(coming Jun 13), and the month deep dive in days 61 to 90, own a bet(coming Jun 29).

What you'll feel

Day 5: useless, because everyone references history you don't have. Archaeology fixes this faster than tenure does.

Day 25: pressure to have opinions. Hold. An opinion at day 25 is a guess wearing your reputation.

Day 50: the artifact lands and someone senior asks who made it. This is on schedule.

Day 80: the first real pushback on your bet. Welcome. Pushback at day 80 means you proposed something with actual content.

Pick one thing this week

If you have signed but not started: set up the second brain and the synthesis agent tonight. Two hours, no company access needed.

If you are inside the first 30 days: start decision archaeology this afternoon. Pull the last quarter's launch posts and killed projects and start the timeline.

If you are past day 90 and none of this happened: run the plan anyway, compressed. The window for the fresh read is gone, but the ledger, the map, the artifact, and the bet work at any tenure. The templates are in the PM First-90 Kit(coming Jun 13).

Sources: Michael Watkins, The First 90 Days for the classic frame, Teresa Torres, Continuous Discovery Habits for the interview cadence the signal map feeds, Julie Zhuo, The Making of a Manager on manager expectation-setting.