Jul 28, 2022 · 53m · lennys-podcast
How to create a winning product strategy | Melissa Perri
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
Product leadership expert Melissa Perri joins Lenny Rachitsky to unpack why organizational failures stem from flawed strategy deployment rather than skill deficiencies, offering practical guidance on crafting product vision, scaling CPO leadership, establishing product operations, and avoiding dogmatic frameworks.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Lenny holds 18% of the talking time here. How this is scored →
Lenny as informed peer 3.3 Guest teaching 5.8 Guest disagreement 1.4 Lenny pushing back 0.0
speaking balance: gold is Lenny, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 50:50 Rejection of dogmatic agile frameworks
Melissa emphatically criticizes teams getting trapped in rigid scrum ceremonies and writing endless user stories, urging practitioners to discard dogma that fails to produce real value.
Hardest push from Lenny ▶ 43:00 Host framing on pragmatic learning vs credentialsLenny sharpens and directs Melissa's point by highlighting that strategic acumen comes from talking to people and examining data rather than reading textbooks or getting an MBA.
Biggest teaching moment ▶ 20:45 Root cause of organizational failureMelissa corrects a widespread misconception among executives by explaining that 99% of organizational problems stem from poor goal deployment and missing strategic context rather than inadequate employee skill.
Lenny holds their own ▶ 33:29 Host sharing PM management insight on visionLenny draws directly from his own product management leadership experience to discuss how difficult vision development is to teach and how leveraging design elevates strategic communication.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Lenny as informed peer | Guest teaching | Guest disagreement | Lenny pushing back | Why |
|---|---|---|---|---|---|---|
| Melissa Perri's Background, Teaching, and Current Initiatives | 2 | 2 | 1 | 0 | Lenny opens with a warm, conversational introduction asking about Melissa's background and current initiatives. Melissa outlines her teaching at Harvard, Product Institute, and CPO Accelerator without any tension. | |
| Scaling Hurdles and Transitioning to Multi-Product Portfolios | 3 | 5 | 1 | 0 | Lenny prompts Melissa to share common scaling problems modern tech companies face. Melissa delivers an in-depth breakdown of transitioning from single-product PMF to multi-product portfolio strategy. | |
| Key Indicators for Hiring a Chief Product Officer | 3 | 6 | 1 | 0 | Lenny asks for concrete signals that indicate it is time to hire a Chief Product Officer. Melissa explains diagnostic methods, including identifying board communication gaps and lack of alignment across team initiatives. | |
| Sizing Teams, ARR Milestones, and VP vs. CPO Distinctions | 3 | 7 | 1 | 0 | Lenny probes for specific metrics like ARR thresholds and PM headcounts. Melissa provides clear heuristics around $20M-$30M ARR and differentiates functional VP responsibilities from executive CPO financial forecasting. | |
| Interim CPO Roles and Driving Organizational Transformations | 3 | 6 | 2 | 0 | Melissa discusses her interim CPO engagements and cautions that consulting fails if leadership lacks the willingness to execute tough decisions. She notes that 99% of company issues stem from strategy deployment rather than employee skill gaps. | |
| Recognizing a Lack of Strategy and Bridging the Missing Middle | 4 | 7 | 2 | 0 | Lenny asks how to spot teams lacking product strategy. Melissa dismantles empty corporate vision statements and articulates the concept of the 'missing middle' between high-level ambition and frontline engineering tasks. | |
| Sponsor: MakeLog Product Changelog Tool | 2 | 5 | 1 | 0 | Following a sponsor break, Lenny asks for a tangible checklist to evaluate strategy presence. Melissa explains how consistent team-level narratives and reduced executive infighting indicate strategic health. | |
| Structuring Strategic Artifacts and Documenting Strategic Intents | 3 | 6 | 1 | 0 | Lenny asks about strategic artifact documentation. Melissa lays out a practical two-page memo structure spanning strategic intents, problem-oriented product initiatives, and execution options. | |
| Developing and Communicating an Effective Product Vision | 4 | 6 | 2 | 0 | Lenny shares his management experience regarding PM vision development and notes how design partnerships amplify clarity. Melissa highlights the importance of combining visual prototypes with written narratives that explicitly state what not to do. | |
| How Product Managers and Leaders Can Hone Strategic Thinking | 5 | 6 | 1 | 0 | Lenny synthesizes Melissa's practical recommendations, emphasizing that strategic skill develops through cross-functional data-gathering rather than academic degrees. Melissa stresses making decisive choices despite incomplete certainty. | |
| Understanding Product Operations and Scaling Research & Data | 3 | 7 | 1 | 0 | Lenny inquires about Melissa's upcoming book on product operations. Melissa breaks down the discipline into internal insights, scalable user research enablement, and governance cadences. | |
| Navigating Information Overload and Iterating on PM Frameworks | 4 | 6 | 3 | 0 | Lenny asks how PMs can manage advice overload. Melissa delivers an impassioned critique of dogmatic agile implementations and urges practitioners to discard frameworks that do not serve their workflow. |
Statements from this episode (13)
Perri: Moving from single to multi-product is SaaS's hardest hurdle
“One of the biggest issues I kind of see with them and product management is at this pivotal scale up phase where they go from, Hey, I found product market fit to I'm ready to scale. One it's hiring a great chief product officer that can help them figure out wh…”
Perri: Uninformed boards signal the need for a true CPO
“If your executives and your board are telling you that the person who's communicating those things to them are usually not chief product officer level, right? Like if you are, if your executives don't know what you're doing, that's a big problem. So that's usu…”
Perri: High-growth software companies typically hire CPOs at $20M-$30M ARR
“If you're going above ten million dollars in ARR, it's usually when you hit around 20 to 30, you start to bring on a CPO and a high growth company.”
Perri: CPOs differ from VPs by explicitly tying roadmaps to revenue
“Where the gaps come between that and becoming an executive is like interfacing with the board, understanding the financial super deeply so that you can Create revenue projections off of what your roadmaps and your products strategy is going to be.”
Perri: 99% of product issues stem from strategy deployment, not training
“I've met a lot of organizations that think most of their issues are in the training of their people. And 99% of the time I see that it's actually in the way that they're setting their goals and deploying their strategy. Because once you train those people. The…”
Perri: Constant shipping without moving metrics signals a missing product strategy
“Signs that there are no strategy. Teams are all working like dogs. Like they're working. 80 hours a week. I see this all the time. People are heads down, crunching, crunching, crunching, releasing, releasing, releasing, or sometimes not releasing, but they're …”
Perri: Product strategy belongs in two-page memos, not 20-page PRDs
“And it's not like a product requirements document that's 20 pages. It's like a two pager just explaining what we're doing and why. And that context we usually throw into Google docs or a wiki or something like that, link them all together so that you can go fr…”
Perri: Product visions must be concrete but unachievable in one release
“A vision should be concrete enough where people can picture what it will be in their head. It can't be a fluffy, like be the backbone of healthcare, right? Like, what does that mean? I don't get it. So people need to be able to look at a vision and say, I can …”
Perri: Good product visions explicitly define what a company will avoid
“Good visions also say what you don't want to do. I love reading a vision that's like, we're not going to be like that. And that to me is so powerful because you're like, oh, okay, we're not going to copy that. Right. We're not going to go after that. Cause you…”
Perri: Product operations should decentralize user research rather than siloing it
“It's not. Centralizing user research as a practice. It's helping to scale user research so that we can enable more people to do user research, especially when you get into some of these companies.”
Perri: Athenahealth had 350 PMs repeatedly interviewing the exact same clients
“Like when I first started doing this. It was at Athena Health and we had 350 product managers and we had to make sure they weren't bothering the people at the same hospital over and over and over again, because they were when we came in and we said, wow, okay,…”
Perri: Product ops should standardize cross-functional deliverables, not internal rituals
“What I say is it doesn't standardize stuff that only belongs to a team. Like I don't care how a team does their standups. Like you choose how to do that. I'm not going to standardize that, but I do care what format your roadmap comes in. I do care how we make …”
Perri: Product teams should abandon dogmatic Agile and Scrum when unhelpful
“Try to tell teams that, you know, started with scrum or started with some of these more dogmatic processes. It doesn't serve you. Move on, change it, right? Everything's meant to be iterated on. Everything's meant to be adapted. If it does not work for you do …”