Lenny's Podcast
Lenny's Podcast

Mastering product strategy and growing as a PM | Maggie Crowley (Toast, Drift, Tripadvisor)

Maggie Crowley is VP of product at Toast and previously vice president and head of product at Charlie Health, senior director of product management at Drift, and a PM at TripAdvisor. She’s also the host of Build, a podcast dedicated to product and product management. In today’s conversation, Maggie

Featured Speakers

Lenny Rachitsky HostMaggie Crowley Guest

Topics Discussed

Episode Summary

Executive Summary: Maggie Crowley argues that great product management is less about flashy strategy and more about simplification, follow-through, and ownership. She emphasizes shipping, learning from results, carrying cross-functional work, and writing clear strategy docs that connect mission to execution. She also warns against overreliance on data or product-content clichés, and encourages authentic content creation as a career accelerant.

Main Topics: What separates great PMs (Priority: 5/5): Maggie identifies three recurring traits in the best PMs: they simplify complexity, follow up on outcomes, and do whatever work is needed to ship and drive results. Product strategy as a written logic chain (Priority: 5/5): She outlines a practical strategy template: start from mission, map landscape and current state, identify opportunities and constraints, then propose a focused plan that anyone can trace back to the business goals. Simplification and prioritization as core PM skills (Priority: 4/5): She stresses that PMs must reduce complexity, keep docs concise, use clear conclusions up front, and choose one thing to execute rather than spreading effort across many priorities. The value of follow-up and measurable outcomes (Priority: 4/5): Great PMs do not just launch work; they circle back on metrics, share results with stakeholders, and use those learnings to build credibility and improve future decisions. Career growth through depth and repetitions (Priority: 4/5): She argues that PM expertise takes years of shipping and staying close enough to products to see consequences, and that staying longer at a company can accelerate real learning. Contrarian views on data-driven culture and product content (Priority: 3/5): Maggie sees overemphasis on being 'data-driven' as a warning sign if it crowds out user understanding, and she warns that online product advice can oversimplify reality and create false templates. Writing and public content as career leverage (Priority: 3/5): Creating content helped her network, recruit, and learn faster, but only because it came from genuine work and real questions rather than chasing clout.

Key Arguments: The best PMs can identify the single most important thing, stay with it long enough to finish, and avoid getting trapped by complexity. Following up on launches and experiments is unusually high-value because it helps both the manager and the PM learn what actually happened. PMs are often the emotional center of the team, so they must carry extra responsibility for morale, optimism, and cross-functional glue work. Strategy should be a written artifact that traces from company mission to team priorities; without that logic chain, disagreement becomes opinion-based instead of evidence-based. A good strategy doc can be long internally, but should open with a concise summary and make the reasoning transparent enough for teammates to challenge specific assumptions. Being 'data-driven' can be a red flag when it replaces judgment, user research, and understanding of why behavior is happening. There is no reliable shortcut into PM; getting a PM title, often via business school, lateral transfer, or startup experience, materially changes hiring odds. Real PM competence takes years of shipping; frequent job-hopping can help, but deep exposure to a product cycle teaches more than shallow repetitions. Product content is useful as a toolkit, but dangerous when people treat frameworks as universal truth rather than context-dependent tools. Authentic writing and content creation can improve career access, recruiting, and learning when grounded in real work rather than performative branding.

Data Points: Years to feel competent as PM: ~5 years - Maggie said she did not really feel like she knew what she was doing until about five years into her PM career. Years at Drift: almost 4 years - She said staying at Drift allowed her to see multiple product cycles and learn deeply. Rewrite project duration: 2.5 years - A product rewrite she described was estimated at six months but dragged on for about two and a half years. Initial rewrite estimate: 6 months - The engineer on the rewrite estimated a six-month timeline. Product strategy doc length: up to 20 pages - She said a strategy doc can become long when covering market dynamics, competitors, technical change, and screenshots. Slack workspace size: 3 people - She described a small feedback group with two other women product leaders and herself. PM onboarding with new hire: 4 months - At her last startup, she spent four months working closely with an MBA recruit to help her ramp into PM. Podcast/community example: 2,500 traders - Mentioned as part of the sponsor read for Composer, not central to the discussion. Trading volume platform sponsor mention: $1 billion - Sponsor read for Composer highlighted its total trading volume. Trades executed sponsor mention: over 1 million - Sponsor read for Composer stated the platform had executed over one million trades.

Pivotal Quotes: "If you ever find yourself saying something like, that's not my job, that's probably a thing you should do." — Maggie Crowley: Her explanation of why PMs must take ownership of unglamorous, cross-functional work. "The really, really good PMs, remember to follow up." — Maggie Crowley: On why checking results after launch is a distinguishing trait among top PMs. "If you're a PM, you don't have that thing, right? It's not like, oh, my job is just to write the one pager. That's not true. Your job isn't just to pick the problem. Your job is to deliver a business result." — Maggie Crowley: Her definition of the PM role as outcomes-oriented rather than document-oriented.

Implications: Listeners should focus less on PM theater and more on ownership, clarity, and learning loops. For teams, the message is to reward judgment, user understanding, and execution discipline over jargon, dashboards, or generic frameworks.

🔓 Sign Up for Unlimited Episode Search

About Lenny's Podcast

Lenny Rachitsky interviews world-class product leaders and growth experts about building products and growing careers.

View all episodes from Lenny's Podcast