How to become a top 1% product manager, with Ian McAllister

Executive overview

Most PMs plateau because they spread effort across too many skills instead of mastering the few that compound. Ian McAllister — who spent 12 years at Amazon, then Airbnb and Uber — argues that a handful of capabilities separate top 1% PMs from everyone else, and the right ones change as you become more senior.

For new PMs: communicate, prioritize, execute. For senior PMs: think big, earn trust, drive impact above all else. Working backwards from customer problems — not from available technology — is the discipline that holds it together at every level.

The core insight: trust is the currency of product leadership — built by repeatedly setting expectations and meeting them, and lost the moment you don't.

The top skills for new PMs

• Communicate: answer first, then explain — never explain your way to an answer
• Prioritize: covers which themes, which projects, sequencing, scope, and your own time — not just roadmap order
• A PM with great prioritization generates 5x the impact of an equally skilled PM without it
• Execute: shape the work into the simplest, highest-impact package, then drive the team forward
• The PM is the motive power behind execution — if you stall, the project stalls
• Grade yourself after every communication: what could I have said better?
• Ask your manager for feedback on specific meetings or emails; treat it as continuous improvement

The top skills for senior PMs

• Think big: before committing to a direction, ask — could this be bigger and more impactful?
• Expand scope beyond the PM's traditional box; own everything affecting your product's success until someone else does
• Earn trust: set expectations, then meet them — repeatedly and visibly
• Trust-building behaviors: tell the truth without fail, launch what you said you'd launch, own mistakes
• Trust-destroying behaviors: being evasive, shipping something different, repeating the same mistake
• Drive impact, not promotion: focus on making the number go up and to the right; promotion follows
• Junior PMs are evaluated on shipping; senior PMs are evaluated on business impact

Working backwards: what most teams get wrong

• Working backwards means starting with a customer problem — not with technology or available ingredients
• The most common failure: teams have a solution in mind and retrofit the problem afterward
• Signal that you're not working backwards: the discussion starts with "we have these two things, we could combine them"
• The press release mechanism enforces the discipline — the problem paragraph comes first; if you skip it, you probably don't have a real problem
• The FAQ tests the third question: is there a legitimate plan to succeed?
• Bezos's three-part investment test: Is it a big idea? Should we be doing it? Is there a legitimate plan to succeed?
• The concept and the mechanism are separate — you can work backwards without writing a press release, but only once the muscle is built

How to implement working backwards outside Amazon

• With your own team: use written documents over slides — richer discussion, deeper product thinking
• Upward and across: match the format your leadership processes; push for doc-based reviews where you have leverage
• For new products: always use the full process (press release + FAQ)
• For smaller features below a certain threshold: carry the spirit, not necessarily the format
• The goal is to never start with "we could build X" — always start with the problem

Learning from Bezos and Wilkie

• Bezos ran the weekly business review for all of North American retail in one hour — forcing every leader to know their metrics and variances cold
• That cadence cascaded: leaders replicated it with their own teams, building an org-wide operational muscle
• Wilkie's model: operational rigor + teaching the why, not just the decision
• Teaching abstracts the lesson so the receiver can apply it to future situations and commit to it more genuinely
• Being a product leader means running what you've already built as rigorously as building new things

Attributes of great communication

• Answer the question asked — especially when the answer is a date, give the date
• Use numbers to answer questions wherever possible
• Avoid weasel words and evasive framing
• Writing clarifies thinking: you cannot communicate clearly without thinking clearly
• Build the habit early; the stakes rise with seniority but the skill compounds from day one

Earning trust in practice

• Understand what the other person's goals are before pushing your own agenda
• Spend time building alignment rather than charging forward with what you believe is right
• Even a correct strategy can fail if you haven't secured the support needed to execute it
• The risk: the right product, right direction, right strategy — all undermined by insufficient trust with the team that has to carry it out