Lenny's PodcastMastering product strategy and growing as a PM | Maggie Crowley (Toast, Drift, TripAdvisor)
CHAPTERS
- 0:00 – 0:55
“Carry the water”: the PM mindset of doing whatever it takes
Maggie opens with a core philosophy: if you find yourself saying “that’s not my job,” it’s probably exactly the gap you should step into. She frames the PM as the emotional center of the team—responsible not just for plans, but for momentum and outcomes.
- •“That’s not my job” is a warning sign for PM effectiveness
- •PMs often become the team’s emotional center and motivator
- •Taking on unglamorous tasks can accelerate shipping and impact
- •Optimism and follow-through are part of the job, not extras
- 0:55 – 4:12
Maggie’s background and what this conversation will cover
Lenny introduces Maggie’s career path (TripAdvisor → startups → Toast) and the themes for the episode. The scope includes PM excellence, strategy, hiring/breaking in, contrarian takes, and content creation.
- •Maggie’s roles across TripAdvisor, Drift, startups, and Toast
- •Episode topics: great PM traits, strategy writing, breaking in
- •Preview of contrarian opinions and career growth lessons
- 4:12 – 11:27
Three traits of the best PMs: simplify, follow up, and “carry the water”
Maggie shares the consistent threads she sees in standout PMs across company stages and product types. She argues these are what elevate PMs beyond baseline skills like communication and analytics.
- •Trait #1: simplify complexity into the one thing that matters
- •Trait #2: follow up on results after shipping—not just plan metrics
- •Trait #3: do the hard/boring cross-functional work to drive outcomes
- •Strategy is important but “a tiny slice” compared to shipping impact
- 11:27 – 19:37
Getting better at simplification: writing, editing, and ruthless focus
The discussion turns tactical: how to build the simplification muscle in docs, decisions, and prioritization. Maggie emphasizes that simplification is partly a skill, partly repetition—and always about clarity of intent.
- •Read your writing out loud to expose complexity and confusion
- •If you can explain it clearly in conversation, write it that way
- •Use repetition and reviews to improve simplifying over time
- •Simplification is prioritization + staying with the decision long enough to ship
- 19:37 – 21:38
Peer feedback loops: Maggie’s tiny Slack “support group” for better work
Maggie describes a small, trusted peer group where they edit each other’s work, troubleshoot leadership challenges, and share perspective. She highlights how feedback becomes harder to get the more senior you become—and why this matters.
- •A small, trusted peer circle can replace missing senior feedback
- •Slack/always-on channels reduce friction to asking for help
- •Use peers for document edits, venting safely, and decision calibration
- •Maintain relationships from past roles—future support networks emerge
- 21:38 – 24:19
Following up on results: the underrated habit that makes PMs stand out
Maggie explains why leaders rarely get proactive post-launch updates—and why it’s a huge differentiator when PMs provide them. The approach is simple: calendar reminders, dashboards, and consistent sharing.
- •Set calendar reminders: 2 weeks, 1 month, 6 months post-launch
- •Share outcomes proactively—don’t wait for managers to ask
- •Following up builds learning loops for better future decisions
- •Visibility matters: don’t rely on “quiet excellence” being noticed
- 24:19 – 27:25
PM time horizon: how long it takes to get good (and why staying can help)
They discuss the tension between job-hopping for title growth and staying long enough to see consequences. Maggie shares how depth and multiple product cycles helped her build real judgment faster later in her career.
- •It can take ~4–5 years to feel truly competent as a PM
- •Startups can expose gaps quickly when you’re the only PM
- •Staying longer lets you see second/third-order consequences of bets
- •Impact takes time; promotions often follow repeated shipping cycles
- 27:25 – 31:42
“When in doubt, it’s your job”: ownership, gaps, and the unglamorous PM reality
Maggie reframes PM work as outcome ownership rather than task completion. She details the day-to-day “bullshit work” that actually makes products succeed—QA, implementation, sales calls, project management, and closing gaps no one else owns.
- •PMs are accountable for business/user outcomes, not artifacts
- •Engineers/designers can “hand off”; PMs must ensure it all lands
- •QA, customer implementation, copy, and coordination aren’t ‘below’ PMs
- •Being the emotional center of the team is part of effective leadership
- 31:42 – 34:36
How to land a PM role: realistic paths, persistence, and getting the first “stamp”
Maggie outlines common entry routes into product and why the first PM title changes everything. She shares an example of hiring someone without prior PM experience—and how much mentorship it required.
- •Common paths: lateral internal move or joining a startup
- •Entry-level PM programs exist but are scarce and competitive
- •Once you have “PM” on your resume, future hiring screens get easier
- •Persistence and relationship-building can create the opening
- 34:36 – 47:00
Step-by-step: Maggie’s product strategy doc from mission to plan
Maggie shares a practical strategy-writing process designed to be explicit, traceable, and debate-friendly. The core move is documenting the full “logic chain” from mission through landscape, opportunities, constraints, and a concrete plan.
- •Start with mission and goals, then document the full landscape
- •Include competitors, SWOT, risks, market dynamics, product/business state
- •Add customer feedback + support signals + technical hurdles/tech debt
- •Derive 1–2 opportunities, outline challenges/assumptions, then propose a plan
- •Share broadly so disagreements anchor to specific points, not opinions
- 47:00 – 49:42
Strategy in practice: doc length, readership, and the roadmap mismatch
They explore why the doc can be long (even 20 pages) and why that’s okay: it’s primarily the PM’s “homework” and reference. Maggie also describes the common moment when strategy and roadmap don’t match—and how that reveals hidden resource allocation problems.
- •Write a top summary (Minto-style) so skimmers get the conclusion fast
- •Long docs can include screenshots, competitive research, and artifacts
- •Triad partners (engineering/design) often engage deepest with the content
- •Strategy often conflicts with an already-bloated roadmap—forcing hard tradeoffs
- •Not every feature needs a full strategy process; use judgment
- 49:42 – 54:02
The PM one-pager: centering on “why,” “why now,” and decision history
Maggie explains her one-pager philosophy as the PM’s core artifact for aligning a squad. The emphasis is on crisp context and motivation before solutions, plus maintaining a running log of decisions and links to supporting research.
- •Core headings: background/context, the problem, why it matters, why it matters now
- •Use the doc as “home base” for decisions, scope cuts, and tradeoffs
- •Bring it to the team early and invite critique—don’t be precious
- •“Why now” creates focus and preempts inevitable stakeholder questions
- 54:02 – 1:01:09
Contrarian corner: failures, rewrites, and why “data-driven” can be a red flag
Maggie argues that great PMs have shipped something bad—and can articulate what went wrong. She shares a painful rewrite story and explains why over-indexing on dashboards often replaces judgment and user understanding.
- •Interview question: “What’s the worst product you’ve ever shipped?”
- •Rewrite cautionary tale: ‘six months’ turned into ~2.5 years and sunk-cost traps
- •Skipping discovery and unclear requirements are common failure drivers
- •“Data-driven” language can signal overreliance on quant vs. qual insight
- •Sometimes the right move is simply the “obviously better” thing
- 1:01:09 – 1:14:28
Product content: why frameworks can mislead—and how creating content helps careers
Maggie critiques how product content can over-sanitize messy reality and cause people to optimize for framework compliance instead of impact. She then shares why content creation has been one of the best career investments she’s made—network, hiring leverage, and accelerated learning.
- •Frameworks lose nuance; readers may confuse artifacts with impact
- •Leaders must explain when/why they’re not “following the rules”
- •Creating content expands network and access to opportunities
- •A clear public POV helps recruiting—people self-select into your style
- •Writing forces reflection and accelerates learning from real work
- 1:14:28 – 1:22:33
Closing thoughts and lightning round: books, products, and the Olympic time horizon
Maggie closes with a reminder that product work is messy, failure is survivable, and fun matters. In the lightning round she shares favorite books, interview questions, products, and a perspective from Olympic speed skating: thinking in multi-year cycles and loving the process.
- •Have fun with the messiness—people are weird and products are for people
- •Recommended books: Presentation Secrets of Steve Jobs; Thinking in Bets; Scaling People
- •Favorite interview question reiterated: worst product shipped
- •Products she likes: LadderFit; PumpLog (focused execution)
- •Speed skating lesson: grind in 4–8 year horizons; mastery through repetition
