The PM role

Your first 90 days as a new product manager

Lesson 40 of 45~11 min read
In this lesson7 sections

An unofficial lesson drawing on the methods in the Career Advancement chapter of Cracking the PM Interview by Gayle Laakmann McDowell and Jackie Bavaro (2014). PracHub is not affiliated with the authors or publisher. Buy the book

Your first 90 days as a product manager decide how much the team will trust your calls for a long time after. Interviewers test the same skill with questions like "How would you ramp up on a product you don't know?" and "How do you win over a team that doubts you?"

Dana has just joined a grocery-delivery app as the PM for substitutions. When an item is out of stock, the picker (the person shopping the order in the store) chooses a replacement, and the customer accepts or rejects it in the app. A rejected item is refunded. Customers reject 21% of replacements. Dana has never worked in retail.

Weeks 1 to 3: find out why things are the way they are

Dana's first idea arrived on day two: let customers set their wishes before checkout, such as "any brand is fine" or "refund it, don't replace it". It seemed obvious, which made her suspicious, so she asked the engineering lead why the app had never done it.

The answer was a test from two years earlier: a preferences step at checkout had cut completed orders and was removed within a month. She also learned how the team decides. Any change that adds taps to the picker app needs the operations lead's sign-off, because pickers are paid per batch and every extra tap costs them money. Neither fact was in any document she'd been handed.

"Before I suggest anything, could you walk me through the preferences test: what you tried, what you saw and who decided to pull it?"

Then she spent two half-days beside pickers. Their app suggests one replacement, by aisle and closest price, and pickers almost always take it to keep pace.

Before you change anything, learn what was tried and dropped, and how decisions get made today: who has to agree, who can block, what counts as evidence. Keep asking "why is it built this way?" until you reach a decision and its reason. A PM who acts first tends to repeat an old mistake in front of the people who lived through it.

To practice this step, try New PM in the First 90 Days: Discovering and Prioritizing the First Problems or Ramping Up on an Unfamiliar Product to Build Its Roadmap. Write only what you'd learn in week one and who you'd ask, then stop.

Hear from customers before you read the numbers

Not knowing the domain matters less than you'd fear. A PM who is keen to learn can get good in an unfamiliar field, and teammates often help. The operations lead offered Dana a walkthrough of how batches are built, because the last PM's specs kept asking pickers for things they couldn't do mid-aisle. Rosa, an engineer, spent an hour showing her how the app scores each candidate replacement.

Build your picture of the customer from several sources, starting closest to real use:

  • Use the product as a customer. Dana ordered her family's groceries through it twice a week.

  • Talk to customers, the unhappy ones first. She phoned eight who had rejected three or more replacements last month.

  • Sit with the people who operate it, as she did with pickers.

  • Read the support queue. She read 200 substitution tickets before opening a dashboard.

  • Only then, the numbers: rejection rate by category, by store, by hour.

The calls told her what no ticket had. Most callers shrugged off a wrong brand, but not a swap that broke a diet. One father whose daughter can't eat gluten now checks every label in every bag, and has stopped buying bread through the app. People who quietly stop buying don't write in. So the replacement ranking should put the household's diet ahead of price. That judgment is the PM's job, and it rests on knowing the customer better than anyone else on the team.

Check one habit: when a question reaches you, do you answer it or forward it? When the VP asked Dana why refunds had risen in one city, she replied that afternoon with the stores, her best guess at the cause and the analyst who could confirm it.

Interviewers check for a drive to learn, often by asking what you've learned outside work lately; have something specific ready, like a product you took apart or a small thing you built. Liking the users matters too, since you'll spend years inside their problems: weigh it when you compare offers, and answer "why this team?" with the people it serves and what you know about them.

To practice this step, try Getting Up to Speed Fast on an Unfamiliar Domain Under a Deadline (PM Behavioral) or Leading a Project in an Unfamiliar Domain as a Product Manager. Pick a real story of your own before you outline anything.

Why diet came before size

In her first one-to-ones, Dana asked each teammate what they'd been meaning to get to for months. The analyst had an answer. For two quarters she had wanted to sort rejected substitutions by reason, and the job kept losing to urgent requests. Dana took it in week three. She pulled 600 of last month's rejections with notes and comments, had a language model sort a first pass by reason, checked 100 by hand and shipped a one-page report.

Why the customer rejected the swapShare
Different size36%
A brand the customer avoids25%
Breaks a dietary need (regular for gluten-free)18%
Much higher price13%
Other8%

The analyst used it in the quarterly review a week later. The report did two jobs. It gave Dana the split she needed, and it answered two worries: most PM work happens out of sight, so a new PM can look idle to the builders, and many teams have watched one arrive and add meetings. Finished work the team already wanted answers both. If nobody names a task like that, look for the backlog item that keeps sliding down, and pick one that improves the product or the team's decisions: goodwill from busywork fades fast.

Size mismatches were the bigger slice, 36% against 18%, yet Dana started with diet. A wrong dietary swap can make someone ill, those tickets were the angriest in the queue, and the calls showed people dropping whole categories over them. The items already carry dietary labels, so the fix was small, and size could come next.

Answer the pushback with evidence and dates that hold

In week four, Dana shared her first written plan for the quarter. The engineering lead commented on nearly every line and redid her estimate of the orders each change would touch. This is normal. He is the one paged at night if a bad call ships, and he hasn't yet seen Dana make a single call.

Don't lean on your title to settle it. Answer with evidence and let time do some of the work, because standing comes mostly from results and calls that hold up. Dana replied to each comment with what she'd seen in stores and tickets, and linked the report she'd just shipped. Had she bristled, he'd have stopped bringing problems to her and taken them to his own manager.

Dates hold only if engineers aren't left waiting on you. In week five, Dana listed her recurring meetings: 23 of them, 17 hours a week. She dropped five: three status meetings that repeated a written update, a cross-team sync whose notes told her enough, and a weekly forum she'd joined only to be seen. She told each organizer why, so it read as a decision. Most of the rest was chat and documents waiting for comments, so she set rules. A question that blocks an engineer gets an answer the same half-day, even if the answer is "I'll decide by 3pm". Channels outside her team and incidents stay muted until her once-a-day read. Anything not on her one task list, checked at the start and end of each day, waits.

By week seven every date in her plan had held, and her next plan drew three comments.

Build standing with leaders of partner teams too, since they decide whether their people work with you. Dana met the operations lead every two weeks with picker-time numbers in hand.

To practice this step, try Winning credibility with senior teammates who doubt your leadership as a PM or Behavioral: Building Credibility With a Skeptical Team to Unblock a Shared Decision. Outline your answer, then check that it ends with a result someone else could confirm.

Write down what proof looks like before you build

Her bet: suggest replacements that keep the missing item's dietary label first, and show pickers the label so they stop choosing swaps that break it. Evidence said what to build, not whether it would work.

Dana's previous team wrote one page before every experiment: the decision it would inform, the main metric, the guardrails, the minimum run time and who makes the call. Here she found a test called a win after four days whose gain vanished at full launch. So she brought the page for the diet test only, minus its line about sign-off from a central data science group this team doesn't have. On it she wrote:

  • The main number: the rejection rate for replacements of items with a dietary label. It's 34% today, against 21% for all items. The target is 20% within the quarter.

  • Two guardrails: seconds per pick must not rise by more than 5, and the share of missing labeled items where the customer keeps nothing (no swap, or a rejected one) must not rise. No-swap refunds will climb by design when no safe item is on the shelf; this catches good swaps lost along with the bad.

A practice you've seen work is a quick way to add value, but timing matters. Pushed in week one, it sounds like "my old team did it better". Brought once you've found the problem it solves, it sounds like help.

A PM is judged on both halves: an experience that works for the person, and proof that it moved the number you named in advance. See our lesson on metrics and diagnosing a drop and the note on guardrails.

Report the launch, then ask how it landed

In design review, Rosa pointed out that pickers racing a batch clock tap straight past a warning, and proposed blocking swaps that break the label. The team built it her way, and in week eleven the dietary filter went live in 10% of stores. Each group needed something different, so Dana wrote the update three times.

For the engineers:

"The dietary filter is on in 10% of stores behind the flag. It's for people like the father I spoke to, who now checks every label in every bag. We're watching rejections on labeled items and seconds per pick; if pick time rises more than 5 seconds, we switch it off. Blocking instead of warning was Rosa's idea, and it was the right call."

For support:

"From Tuesday, in the stores listed below, pickers can't replace a gluten-free or dairy-free item with one that isn't. Customers there may get more refunds and fewer swaps on those items. Please tag those tickets dietary-swap so we can count them."

For the VP:

"We're testing a fix for the substitution complaint that does the most harm: swaps that break a diet. A third of replacements for dietary items get rejected today; the goal is 20% this quarter without slowing pickers or leaving more customers with nothing. First read in three weeks. Nothing needed from you yet."

The facts are the same in all three; what leads changes. Engineers get what changed and how to switch it off, support gets what customers will see and what to do, and the VP gets the result against the goal and any ask.

Notice the credit line in the engineering note: the idea was Rosa's, and Dana kept it hers in every meeting after. A team that owns the plan will defend it without you.

Peers rarely tell you how you're seen, but your manager hears it. At the end of the quarter, Dana asked hers:

"What are the engineering, operations and support leads saying about working with me? And what's one thing I should change?"

Mostly good: the report had landed and she kept her word. But the operations lead felt she brought finished plans for approval instead of problems to work out together, and her written updates ran long. That became her plan for the next quarter: take the next problem to the operations lead before writing a plan, and keep updates under 150 words.

That reputation travels. Informal reference calls are common in hiring, so a future employer may ring someone you worked with without asking you. They'll recall what they saw: for Dana, plan dates that held, the rejection report she delivered and Rosa's blocking idea kept as Rosa's.

To practice this step, try Bridging engineers and business stakeholders as a product manager and answer it aloud in two minutes, using your own work.

In the interview

"How would you ramp up on an unfamiliar product?" Give an order: what you'd learn first and from whom, what you'd leave alone, and the first useful thing you'd ship. Then tie it to something you've done:

"When I joined my last team, I spent three weeks using the product, calling unhappy customers, sitting with the people who run it and reading support tickets before I proposed anything. The first thing I shipped was a report our analyst had been putting off for two quarters."

"How do you build credibility with a skeptical team?" Skip the talk about rapport. Say what you did that the team could see, and what followed.

"The engineering lead challenged nearly every line of my first written plan. I answered with evidence from stores and tickets, took a long-postponed report off our analyst, and made sure an engineer's idea stayed hers. My next plan drew three comments."

A story with a date and a number beats a list of principles. Our lesson on building a PM behavioral story bank shows how to keep a few ready.

To finish, try Behavioral: Earning Buy-In from a Resistant Engineering Partner as a Product Manager and tell your answer aloud in under two minutes.

All communication and stakeholder questions