Lenny's PodcastWhat it takes to become a top 1% PM | Ian McAllister (Uber, Amazon, Airbnb)
CHAPTERS
- 0:00 – 4:42
Why Ian’s “Top 1% PM” post resonated—and what he expected from publishing it
Lenny sets up Ian’s influence in the PM world through his widely shared essay on top PM attributes. Ian explains he wrote it largely for fun and to structure his own thinking, not expecting broad reach.
- •Lenny’s personal story of the post’s impact on his early PM growth
- •Ian’s original intent: answering a well-scoped Quora question in the “Goldilocks zone”
- •The post’s unexpected longevity and continued referencing in the PM community
- 4:42 – 8:24
How writing changed Ian’s career: network effects, credibility, and opportunities
Ian describes how publishing online—especially his posts on Amazon’s processes—created relationships and industry connections that shaped his path (including to Airbnb). They discuss writing as a way to sharpen thinking and communication.
- •Writing about “working backwards” and PM/people management created inbound connections
- •Amazon’s relatively private culture made external writing especially distinctive
- •Writing as a forcing function: clear thinking → clear communication
- •Business writing skills as a durable career lever
- 8:24 – 10:56
Ian’s career journey: from marketing and coding to Microsoft, Amazon, Airbnb, and Uber
Ian walks through his unconventional background, including moving to Tokyo, bootstrapping into software, and evolving into product leadership roles. He highlights major chapters at Amazon, a stint at Airbnb, and his current work at Uber.
- •Transition from economics/finance → beer marketing → software development
- •Microsoft program manager role as an early PM-equivalent foundation
- •12 years at Amazon: retail/conversion, Amazon Smile, Alexa International, delivery ops
- •Airbnb: customer support technology platform
- •Uber: vehicles platform (fleets/rentals, electrification, AV platform path)
- 10:56 – 15:01
The core attributes of a top 1% PM: the full list and what Ian added later
Ian enumerates the original traits from his post and then shares the attributes he added in a recent refresh. The discussion frames these as a menu of strengths—few people excel at all of them, but the list defines the landscape.
- •Original attributes: think big, communicate, simplify, prioritize, forecast/measure, execute, technical trade-offs, design, copy
- •Added later: earn trust, dig for data, push back effectively, adapt to change, be driven by impact (not promotion)
- •Trust framed as “currency” for PMs and especially product leaders
- 15:01 – 21:14
For new PMs: the three skills that matter most—communicate, prioritize, execute
Ian narrows the list to three foundational skills for early-career PMs. He shares concrete examples of how communication breaks down, why prioritization multiplies impact, and how execution depends on shaping scope and enabling the team.
- •Communication as a career-long skill; “answer first, then explain”
- •Prioritization across many layers: themes, sequencing, scope cuts, and time management
- •Execution includes packaging solutions simply and improving team throughput
- •PMs as “motive power” behind shipping and outcomes
- 21:14 – 23:06
Tactical ways to level up communication (and why there’s no single prioritization hack)
Ian offers practical tactics to improve communication, pointing to his “Operator’s Manual” as a checklist of common pitfalls. He recommends self-grading after key interactions and using feedback loops to steadily improve.
- •Use a checklist mindset: avoid weasel words, stop rambling, “answer and then shut up”
- •Continuously self-assess after meetings, docs, and quick hallway/elevator questions
- •Actively ask managers for feedback on communication effectiveness
- •Working backwards as a broader practice that indirectly improves prioritization
- 23:06 – 29:58
For senior PMs: think bigger, earn trust, and stay driven by impact
For experienced PMs, Ian emphasizes expanding scope and ambition (“bigger elephants”), building trust through reliability and truth-telling, and letting impact—not promotion—guide daily decisions. He explains how expectations shift as PMs become more senior.
- •Think big: challenge whether an idea can be larger and more leveraged
- •Earn trust: set expectations, call shots, hit goals; truth and accountability matter
- •Impact focus: promotions often follow sustained business impact
- •Senior evaluation: less about shipping tasks, more about moving key outcomes
- 29:58 – 33:15
Broadening your “ownership box”: thinking like a GM and removing constraints beyond product
Ian describes “thinking big” as expanding what a PM considers in-scope—beyond roadmaps and engineering—to any constraint limiting customer or business success. This frames product leadership as cross-functional problem removal, even without direct authority.
- •Many PMs operate within a narrow definition of the role
- •Adopt a wide-angle view: anything affecting success is part of the job until owned elsewhere
- •Influence across functions (marketing, operations, support) without formal reporting lines
- •Find and remove barriers to outcomes, not just ship features
- 33:15 – 37:27
Trust in practice: what Ian wishes he’d done differently at Airbnb
Ian shares a reflective example from Airbnb, where he drove analytics-heavy platform work but later felt he could have invested more in partnership and alignment with customer support leadership. The lesson: the right strategy still fails without coalition-building.
- •Trust-building includes understanding others’ goals and forging real alignment
- •Avoid bullheaded execution; invest time to build alliances
- •Mitigate “landing risk”: strategy may not stick without stakeholder support
- •Continuous improvement mindset: treat missteps as learning opportunities
- 37:27 – 39:52
Why Amazon retains people: fit, learning velocity, and operational mechanisms
Ian explains that Amazon’s culture is demanding but clarifies fit quickly. He attributes long tenures to rapid learning, strong mechanisms (docs, reviews, WBRs), and a metrics-driven operating cadence that helps people build durable leadership muscles.
- •Amazon’s “crucible” environment creates a strong self-selection for fit
- •Metrics/fitness functions as a clear definition of success
- •Learning via high-quality written docs instead of thin slide decks
- •Weekly Business Reviews as a training ground for operating rigor
- 39:52 – 46:33
Lessons from Bezos and Wilke: innovation discipline, operating cadence, and teaching the ‘why’
Ian contrasts Bezos and Wilke as complementary leaders and highlights what he learned from each. He shares specific anecdotes about innovation exploration, the importance of a clear problem statement, and how leadership forums reinforce rigor and judgment.
- •Bezos: encouragement, innovation exploration, and discipline around defining the problem
- •Memorable lesson: “If you don’t have a problem paragraph, maybe there’s not really a problem”
- •Wilke: operator mindset, tough love, and WBR-driven organizational rigor
- •Great leaders teach mental models—not just decisions—to scale judgment
- 46:33 – 50:17
Working backwards, done right: start with the customer problem—not a pre-baked solution
Ian explains the most common failure mode: teams claim to work backwards but begin with a solution and retrofit a problem. He shares an early Amazon example (“ASIN-to-ASIN linking”) that had momentum but wasn’t truly grounded in a customer problem and ultimately failed.
- •Core principle: obsess over the problem first; solutions come after
- •Anti-pattern: “we could combine these ingredients/technologies” without a compelling customer pain
- •Retrofitting the customer/problem after choosing the solution undermines the process
- •Working backwards as a mental model Ian now uses to evaluate any initiative
- 50:17 – 59:23
Mechanism vs mindset: PR/FAQ as enforcement tools, plus the ‘legitimate plan to succeed’ test
Ian distinguishes the working-backwards mindset from Amazon’s specific mechanism (press release + FAQ + ‘the facts’). He explains how to adapt the approach in different company cultures and shares Bezos’s three-part investment filter: big idea, should we do it, and a credible plan.
- •Two layers: (1) start with problem; (2) use PR/FAQ as a forcing mechanism
- •Adaptation: use docs where possible, but fit the organization’s culture and leadership preferences
- •Working backwards reviews as gates for resourcing/approval and alignment
- •‘The facts’ section validates a legitimate plan (finances, hurdles, dependencies)
- •Bezos’s criteria: big idea, right fit for company, legitimate plan to succeed
- 59:23 – 1:04:58
Lightning round: books, podcasts, media picks, interview questions, and where to find Ian
Ian shares favorite recommendations and personal preferences, plus how listeners can connect with him. He closes with reflections on writing as a way to build relationships and community.
- •Books: Getting Real (epicenter design), Wool trilogy, Energy and Civilization
- •Podcasts: How I Built This; EV News Daily
- •Media: Yellowstone; Everything Everywhere All at Once
- •Interview question: self-awareness—what have you learned about yourself?
- •Find Ian: Twitter (@IanMcCall) and IanMcCallister.substack.com
