The PM role

How product managers grow and get promoted

Lesson 45 of 45~10 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

Product managers get promoted for measured results with customers, delivered again and again at a growing scope. Knowing that tells you what to spend your weeks on, and shapes your answers to "What's your highest-impact project?" and "What makes you want to leave?", where the interviewer checks whether you know what a PM's work is for.

Our example is Greta, a PM at a company that sells expense-report software to mid-sized businesses. She spent a year in customer implementation, then took the PM job for exports and admin settings, an area nobody else wanted. Two years later she owns expense submission and approval and wants senior PM. An outside offer would give her that title now.

Evidence a promotion case can use

Greta's first draft of her promotion case read "wrote 14 specs, ran 30 customer calls." She deleted it and started again from what had changed for customers. A promotion case is built on what happened after release: did customers use the thing and come back?

Long hours can't stand in for that. A PM answering messages at midnight about a feature nobody uses is behind one who leaves at six with a launch that moved its number.

To practise this step, try Behaviors That Separate Effective Product Managers From Ineffective Ones, and write your list before reading on.

Her second draft rests on three launches, each owned from first plan to a result read eight weeks after release:

LaunchTarget set before buildingResult after eight weeks
Receipt photos fill in the expense lineMedian time to file a report: 14 to 8 minutes9 minutes
Policy warnings before submittingReports sent back by approvers: 18% to 10%9%
Mileage claims from a map routeHalf of mileage claims in the new flow within a quarter62%

Three rows show a pattern where one would look like luck, and each lap through planning, building and the weeks after release makes the next one better. Early on, a team that finishes a cycle every six weeks gives you more laps in two years than one that ships yearly. With continuous deployment a launch is rarely one big day, so count a problem you owned from first plan to measured result. If you're three weeks from shipping when you start a job search, finish and read the first results before you interview: a panel's first follow-up on your last project is usually what happened after release.

To practise this step, try End-to-end product ownership story: goal, scoping cuts and your personal contribution. List every cycle you've completed first.

The policy warnings show the choices behind a target. Beside send-backs from 18% to 10%, Greta named what the launch must not damage: reports started but never submitted. Warnings that scared people off filing would have looked like success on send-backs. That's a guardrail, and it belongs beside your target whether your team writes quarterly OKRs (objectives and key results) or tracks a north-star metric.

Midway through, a designer proposed reworking the whole report screen. Greta asked whether it would cut send-backs. It wouldn't, so it waited.

Receipt photos missed, at 9 minutes instead of 8. Greta traced the gap to hotel bills with dozens of lines, and the fix went into next quarter's plan. A miss you can explain still shows judgment; a launch with no target proves nothing either way.

To practise this step, try Product manager behavioral: your highest-impact project and how you proved its results or PM Behavioral: Presenting Your Biggest Career Achievement and Explaining Why It Mattered. Write down the target you had, or should have had, first.

Work to take on, work to stop

Two other teams were about to build their own approval rules, the logic that decides who signs off an expense. That logic lived in Greta's area, which grew from a piece of approvals work she asked for after her CSV-export fix cut support tickets from about 120 a month to 35. Three copies would have meant customers setting up the same rules three times, so she turned the rules into one shared service. The invoices team launched supplier-bill approvals on it in five weeks, where building their own would have taken four months, and the card product will run on it too.

The question she asked is the one to ask of any area: do other teams depend on it? If they do, one improvement reaches every team built on it, and your case can claim each result.

To practise this step, try Behavioral: Owning Unglamorous but Essential Work as a Product Manager.

Owning an area also means deciding what to stop. Few customers used the custom report builder Greta inherited: 40 of 1,300 customer accounts had opened it in the last 90 days, yet it took half the time of two engineers to keep running. Her one-page case set those two numbers beside what the engineers could finish instead: the policy warnings, a quarter early. Her manager agreed to retire the builder. Stopping work means someone admits an old call was wrong, and usage, cost and a named alternative on one page make that easy to agree to.

For the stopping half, try Behavioral: Deciding to Sunset a Feature and Running the Shutdown. It also asks how you ran the shutdown.

Who has to see the work

Greta runs a monthly launch review where PMs from four teams bring their next launch and its target. When the approvals service needed two engineers from the card team, the PM there knew her from the review and answered within a week. Directors from two other groups have sat in, and both will be in the room that weighs her promotion. If they've seen her work, her manager isn't arguing alone.

Above mid-level, most of the people who weigh your promotion don't work with you day to day. Look for something several teams need and nobody runs: a shared guide to reading experiments, a rotation running post-launch retros across teams, or a customer advisory session several teams attend.

To practise this step, try Influence without authority: securing people or budget owned by another team. Our lesson on leading without authority covers persuasion.

The empty row in her table

Greta set her record against the company's career ladder, the written expectations for each level: every senior PM requirement, with her evidence beside it.

Senior PM requirementGreta's evidence
Ships measured results in an area, repeatedlyThree cycles with targets, two hit
Builds things other teams depend onThe approvals service
Influence beyond her teamThe monthly launch review
Sets a one-year direction for an areaNone. Her director writes the plan she executes

The first three rows are the work above. The fourth is the gap, and her current team won't fill it. The company is starting a corporate-card product with no customers yet, and the card team needs a PM to write its first-year plan. Greta asked for the role, though she'd never written such a plan.

To write it, she lined up mentors, each picked for one strength and given one specific ask. A principal PM known for strong strategy documents got this: "Would you read my draft first-year plan for the card product and mark where a VP would push back?" A narrow ask is easy to say yes to.

She also asked two senior PMs which of their year-old plans had held up, to learn from results rather than style, and asked a PM at a payroll company whose onboarding her customers praised what they had left out of the first version.

Not every gap needs a new team. Greta reads data well and has never priced anything, so she offered a few hours a week to run the invoices team's price test for a new add-on: one bounded piece of work on her weak side, which becomes evidence without a move.

The card team or the startup

Greta's offer is senior PM at a 120-person startup making purchasing-approval software. The manager decides it for her: her first plan is exactly where she needs someone who has grown PMs. She asked three PMs who had worked for the card team's director what happened when a PM's plan went wrong. Two said the director backs PMs then, and hands them work above their level. Had they said she takes over a plan once it slips, the card team would have lost its edge where Greta cares most. A contact who once reported to the startup's head of product told her that person had never managed PMs. A former report knows how a manager acts under pressure, which an interview loop rarely shows.

The other differences sit inside each job. At the startup she'd be the sole PM, setting direction, and a fast-growing company can move you up within months, but only while the growth is funded. Ask about runway: months of cash at current spending, and when they last raised. This one has about 18 months. On the card team she'd write one new product's first-year plan, at a company with no layoffs since she joined.

She scores the two with the scorecard from our lesson on how PM jobs differ plus two rows of her own, showing only rows that differ:

QuestionCard teamStartup offer
Manager4: vouched for by PMs she asked2: head of product has never managed PMs
Direction and ownership4: writes the first-year plan5: sole PM, sets direction
Stability and runway4: no layoffs since she joined2: about 18 months of cash
Total129

She'd take the card team even if the startup won on total, because of the first row. Ownership ranks second because she's two years in; in a first PM job, strong PMs nearby and a leader to learn from would beat a bigger startup title.

The title is the startup's real pull. Big jumps in level usually come from changing companies or joining a risky turnaround, since internal promotion goes one step at a time. A résumé of one-year stints works against you, though: employers hesitate to invest in someone likely to leave. Leaving now, after two years, would look fine; leaving that startup after one would start a pattern.

When you're the one looking

The offer reached Greta through a finance manager at a customer she onboarded in her implementation year, who has since joined the startup. People you treated well, on old teams or on the customer's side, are often the ones who bring you into the next role.

If you're searching, talk to many people, don't read silence or a no as a verdict, and send warm contacts a short update every few weeks. Take an opening that brings you closer to building products even when the title or team isn't what you planned, as Greta did with the area nobody wanted.

Her packet and her answers

Greta's packet leads with the approvals service, not receipt photos. Receipt photos sped up one flow in the expense product; the approvals service serves all three of the company's spend products, expenses, invoices and cards. That reach is what her table's second row asks for, so it goes first.

At many larger companies the case goes in as a promo packet, evidence against each next-level requirement, and a calibration meeting or committee compares it with other teams' candidates to keep the bar even. Ask your manager how yours works and when packets are due.

Her manager's read of the draft: strong, not yet. The strategy row in her table is still empty, and a calibration room reads an empty row as a no, however full the others are. Filling it once won't settle it: with one plan under a line, someone in the room will ask whether she can do it again. So her packet waits for the card product's first-year plan and a quarter of results against it.

Each piece of Greta's case becomes a STAR story: situation, task, action, result. Her highest-impact project:

"Two other teams were about to build their own approval rules, so customers would have set up the same rules three times. I owned expense submission and approval, so I proposed one shared service and borrowed two engineers from the card team for six weeks. Customers with both products now set approval rules once, and approval-setup tickets fell from about 90 a month to 50. The invoices team also shipped on it in five weeks instead of four months."

A time she changed what her team worked on:

"I inherited a report builder that 40 of our 1,300 accounts had opened in 90 days, taking half the time of two engineers. I put both numbers on one page beside what they could finish instead. We retired it, the policy warnings shipped a quarter early, and send-backs fell from 18% to 9%."

Asked later why she changed teams:

"I'd shipped three launches against targets, and the part of the job I hadn't done was setting direction. The card product needed someone to write its first-year plan, under a director known for backing PMs, so I asked for it."

The answer points at what she wanted to learn, not at what she was escaping. Our lesson on why you're leaving covers that question in full.

To practise this step, try Narrate your career history and job moves in a PM interview using your own record.

All self-awareness and growth questions