What it takes to become a top 1% PM | Ian McAllister (Uber, Amazon, Airbnb)
Executive Summary
Ian McAllister discusses core PM skills, trust, problem-first working backwards, operating reviews and teaching the reason behind decisions. Selected third-party transcript coverage excludes detailed company history, personnel evaluations and closing recommendations. Company examples are his accounts, unverified here. The top-1% framing is the show's wording, not a measured ranking. Untimed editorial topics are not video chapters.
Key Takeaways
Build the core PM skills repeatedly
McAllister identifies communication, prioritization and execution as important at every level. Growing seniority does not eliminate the need for them. His long skill list is a direction for improvement, not a requirement that one person be perfect at everything.
Use forecasting and measurement to learn
He connects making a forecast, executing and comparing the result with developing better instincts. A PM should not stop at giving advice or making a prediction. Record what you expected and what actually happened so the next decision benefits from experience.
Earn trust by setting and meeting expectations
McAllister treats trust as a product leader's currency. He points to clear commitments, truthfulness and owning mistakes as practices that build it. Results matter, but people also need to understand what you said you would do and whether you followed through.
Start working backwards from the problem
He warns that using a press-release template does not mean a team is genuinely working backwards. A preferred solution can be dressed up with a problem afterward. Begin with the customer and the obstacle, then consider the solution that best addresses it.
Separate the principle from the document format
Working backwards is a way of thinking; the internal press release and FAQ are mechanisms for practicing it. McAllister says other formats can support the same principle once a team learns it. Choose a suitable format without losing the problem-first discipline.
Know how the existing product is running
His account of business reviews emphasizes understanding trends, variances and what the team will do about them. Product leadership includes operating what already exists, not only building new things. A regular review can reveal where to improve or prevent a problem.
Teach the reason behind a decision
McAllister values explaining the pattern or mental model behind a choice rather than only giving the answer. That helps someone apply the lesson in future situations. A short explanation can have more lasting value than a prescriptive instruction alone.
The Conversation Breakdown
Build the core PM skills repeatedly
⏱ Untimed topicMcAllister identifies communication, prioritization and execution as important at every level. Growing seniority does not eliminate the need for them. His long skill list is a direction for improvement, not a requirement that one person be perfect at everything.
Use forecasting and measurement to learn
⏱ Untimed topicHe connects making a forecast, executing and comparing the result with developing better instincts. A PM should not stop at giving advice or making a prediction. Record what you expected and what actually happened so the next decision benefits from experience.
Earn trust by setting and meeting expectations
⏱ Untimed topicMcAllister treats trust as a product leader's currency. He points to clear commitments, truthfulness and owning mistakes as practices that build it. Results matter, but people also need to understand what you said you would do and whether you followed through.
Start working backwards from the problem
⏱ Untimed topicHe warns that using a press-release template does not mean a team is genuinely working backwards. A preferred solution can be dressed up with a problem afterward. Begin with the customer and the obstacle, then consider the solution that best addresses it.
Separate the principle from the document format
⏱ Untimed topicWorking backwards is a way of thinking; the internal press release and FAQ are mechanisms for practicing it. McAllister says other formats can support the same principle once a team learns it. Choose a suitable format without losing the problem-first discipline.
Know how the existing product is running
⏱ Untimed topicHis account of business reviews emphasizes understanding trends, variances and what the team will do about them. Product leadership includes operating what already exists, not only building new things. A regular review can reveal where to improve or prevent a problem.
Teach the reason behind a decision
⏱ Untimed topicMcAllister values explaining the pattern or mental model behind a choice rather than only giving the answer. That helps someone apply the lesson in future situations. A short explanation can have more lasting value than a prescriptive instruction alone.
Core Frameworks & Ideas
Problem-first working backwards
Define the customer and problem before choosing a solution; use a press release and FAQ or another suitable mechanism.
Trust through expectations
Set clear expectations, meet them, tell the truth and own mistakes.
Forecast-execute-measure
Compare expected and actual results so experience improves future judgment.
Actionable Next Steps
- ✓Write the customer problem before describing a proposed solution.
- ✓Record one forecast and compare it with the result after execution.
- ✓Review whether your recent commitments were clear and met.
- ✓Explain the reasoning behind a decision so a teammate can apply the lesson later.
Notable Quotes
“Probably communicate, prioritize, and execute.”
“Trust is just built by repeatedly setting and meeting expectations.”
“Well, working backwards is all about the problem and starting there and obsessing about the problem and being guided by it to then go into the solution.”
The One Thing to Remember
Start with the customer problem and build trust by making clear commitments and following through.