Lenny's PodcastHow to create a winning product strategy | Melissa Perri
CHAPTERS
- 0:00 – 3:04
Why product orgs struggle: goal-setting and strategy, not just training
Melissa opens with a core diagnosis she’s seen across organizations: most “training problems” are actually strategy and goal-deployment problems. Without clear context and direction, even well-trained teams can’t make meaningful progress. She frames product transformations as holistic change that requires decisive leadership and follow-through.
- •Training rarely fixes outcomes if goals and strategy aren’t clear
- •Teams need context for what to work toward, not just skills
- •Product transformations require holistic org change (not isolated fixes)
- •External help only works if leadership is ready to act
- 3:04 – 6:43
Melissa’s scale of experience and what she focuses on now
Lenny sets context on Melissa’s unusually broad exposure to product teams and companies. Melissa shares that her current energy is centered on education—teaching at Harvard, running Product Institute, and helping product leaders reach the C-suite. She also previews her next book and why she stepped back from deep consulting.
- •Worked with ~4,000–5,000 PMs and dozens of companies deeply
- •Teaching at Harvard and running Product Institute since 2016
- •CPO Accelerator helps product leaders transition into executive roles
- •Writing a new book on Product Operations; stepped back from consulting
- 6:43 – 9:44
The most common product-team breakdown at SaaS scale-ups: strategy deployment
Melissa explains a recurring inflection point for SaaS businesses: moving from product-market fit to scaling, often from single-product to multi-product portfolio management. At this stage, prioritization becomes existential, and the organization must learn to create and communicate a comprehensive strategy. Many companies plateau later and face the same need to rethink and reprioritize.
- •Scaling forces a shift from execution-first to strategy-first leadership
- •Single-product → multi-product portfolio adds complexity rapidly
- •Prioritization becomes critical as requests and options explode
- •Strategy must be communicated and deployed across growing orgs
- 9:44 – 12:31
When it’s time to hire a CPO (and the signals you’re missing one)
Melissa outlines practical indicators that a company needs CPO-level leadership. A key signal is a communication gap: executives and the board can’t explain what product/tech is doing or how it ties to goals. She also describes how she diagnoses alignment by asking teams what they’re working on and why.
- •Board/executives feeling ‘product is a black box’ is a major red flag
- •Misalignment across teams’ ‘what’ and ‘why’ indicates poor strategy deployment
- •Great PMs feeling blocked by lack of direction suggests leadership gap
- •Hiring difficulty and overly junior PM org can signal need for senior product leadership
- 12:31 – 14:41
CPO timing benchmarks and scope: complexity beats headcount
Lenny asks for rules of thumb; Melissa shares that ARR and portfolio complexity often drive the need for a CPO more than a strict PM count. She cites common thresholds (e.g., above ~$10M ARR; complexity events like expansion, pivots, mergers). She also explains how CPO scope often spans product, design, ops, analytics, and sometimes engineering.
- •Typical trigger: growth stage + portfolio expansion; often ~20–30 employees at >$10M ARR
- •Events that force strategy resets (new markets, geo expansion, mergers) push CPO need
- •PM count guidance: often around 7–8 PMs, but varies by org design
- •CPO scope commonly includes design/product ops/analytics; sometimes engineering for alignment
- 14:41 – 16:28
Before a CPO: what a Head/VP of Product should own (and where gaps appear)
Melissa distinguishes Head/VP of Product as a strong functional leader focused on process, roadmaps, and developing PMs—especially effective for one or two products. The jump to CPO requires executive navigation, board communication, and deep financial fluency to connect roadmap to revenue. Complexity and multi-product strategies tend to demand that next level.
- •Head/VP focuses on product function, process, roadmap roll-up, PM coaching
- •CPO requires board-level communication and executive influence
- •Financial depth: translating roadmap and strategy into revenue projections
- •Multi-product/platform strategy and broad cross-functional scope drive need for CPO
- 16:28 – 21:51
When interim CPO/consulting helps—and the non-negotiable: willingness to act
Melissa explains when leaders bring in external help: uncertainty about what product leadership is needed, or how to fix issues quickly while hiring. She contrasts deep transformation work with a short interim model (e.g., 3 months) focused on stabilizing execution and preparing handoff to a permanent leader. She emphasizes that consultants can’t “do it for you” and outcomes depend on leadership action.
- •Common use case: CEO unsure what product leadership is needed or who to hire
- •Interim approach: stabilize, implement basics, and prepare for a permanent CPO handoff
- •Consultants fail when leadership won’t act or expects the consultant to ‘do the job’
- •Real change may require hard decisions: org changes, senior hiring, strategy resets
- 21:51 – 23:52
How to tell you don’t have a strategy: the ‘missing middle’ and stagnant metrics
Melissa lists observable symptoms of strategy absence: teams working intensely while key metrics don’t move, and execs can’t connect shipped work to business outcomes. She describes the “missing middle” between lofty goals/vision and team-level work, leading to scattered initiatives and thinly spread teams. She also notes strategy often exists implicitly but isn’t written or shared consistently.
- •High output, low impact: lots of shipping (or grinding) with no metric movement
- •Execs can’t see how work ladders to goals; product becomes a ‘black box’
- •Strategy often lives in heads; lack of documentation creates misalignment
- •The ‘missing middle’ disconnects strategic intents from team-level initiatives
- •Too many initiatives spreads teams too thin to move meaningful outcomes
- 23:52 – 27:48
Clarifying company vision and strategic intents: write the two-pager
Melissa explains how she elicits and sharpens vision and strategy—starting with interrogating leaders and teams to surface implicit goals. She shares an example of a vague vision statement (“backbone of healthcare”) and why it fails without concrete meaning. Her remedy is a simple written artifact: a two-page memo covering company context, threats, competition, choices, and prioritized strategic intents.
- •Test alignment by asking many people ‘what’s the vision’ and comparing answers
- •A tagline isn’t a vision; it must define meaning, direction, and trade-offs
- •Write a two-pager: history, current state, threats, competition, what to do/not do
- •Prioritize ‘strategic intents’ (e.g., upmarket, new geos, new markets) over multi-year horizon
- 27:48 – 30:50
What ‘having a strategy’ looks like in practice: shared story + calmer trade-offs
Lenny asks for a strategy checklist; Melissa offers an operational test: teams can articulate a consistent narrative linking their work to customer value and business outcomes. She also highlights an organizational indicator—less stakeholder infighting—because executives share goals and can make rational trade-offs. Good strategy deployment makes pushback easier because priorities are explicit.
- •Teams can explain what they’re building and why, tying it to business metrics
- •Consistent story across teams indicates strategy is understood and deployed
- •Aligned exec goals reduce emotional conflict and stakeholder thrash
- •Trade-offs become objective: choosing intent #1 means not doing intent #2
- •Clear priorities make it easier to say ‘no’ (and explain why)
- 30:50 – 36:07
Turning strategy into artifacts: concise memos at each level of the ‘strategy tree’
Melissa describes lightweight documentation that scales: two-page narratives that connect vision to market positioning, current state, priorities, and desired outcomes. She recommends writing at multiple levels—executive intents, product initiatives, and team solution options—then linking them so anyone can traverse the strategy tree. The emphasis is on clarity and context, not heavyweight PRDs.
- •Use short prose docs (1–2 pages) instead of large PRDs to capture ‘what/why’
- •Different levels: business strategic intents → product initiatives → team solutions/options
- •Product initiatives are problem-oriented, made of multiple epics/efforts
- •Link docs in a wiki/Google Docs so teams can trace work to strategy
- 36:07 – 38:49
How to craft a stronger vision: concrete, differentiated, and explicit about ‘not doing’
Melissa gives practical guidance on improving vision quality. A good vision is concrete enough to visualize, far enough away to require iteration, and clearly differentiated from competitors. She argues the most powerful visions also state what the company will not do, preventing reactive copycat behavior.
- •Visions must be concrete and imaginable—not fluffy slogans
- •Should be ambitious and not already achievable with a single project
- •Focus on differentiation: how you’ll win vs. competitors
- •Include what you won’t do to create clarity and prevent copycat strategies
- •Use writing and brainstorming to surface differentiation and customer value shifts
- 38:49 – 44:07
Getting better at strategy as a PM: practice, conversations, and data-informed decisions
Melissa advises PMs to build strategic skill through deliberate practice—mentally role-playing as the CPO, asking better questions, and seeking exposure to market and financial realities. She recommends learning from adjacent functions (sales, finance) and studying how other companies moved from point A to B. Strategy is framed as making the best informed choice possible, then revising quickly when evidence changes.
- •Practice strategy even without scope: ‘What would I do as CPO?’ for reps
- •Interview leaders about their process and inputs behind priorities
- •Talk to other functions (e.g., sales win/loss) to understand market dynamics
- •Strategy depends on internal data + customer research; invest in analytics support
- •Make the best informed decision, then correct course as new evidence arrives
- 44:07 – 49:21
Preview of Product Operations: scaling insights, research, and strategic cadence
Melissa explains why product ops emerges as companies scale: inconsistent roadmaps, meeting overload, scattered insights, and repeated customer outreach. She breaks product ops into three pillars: internal data/insights, customer & market research enablement, and standardizing cross-functional processes and strategy check-ins. The goal is to enable teams—not centralize or micromanage them—while creating consistent inputs/outputs that leadership can use.
- •Product ops solves scaling failures: inconsistent artifacts, poor data access, chaotic cadences
- •Pillar 1: internal data/insights to track OKRs and monitor strategy health
- •Pillar 2: customer + market research enablement (avoid over-contacting same customers; make interviews searchable)
- •Pillar 3: standardize cross-functional processes (roadmap formats, planning rituals, stakeholder updates)
- •Standardize interfaces that affect the org; don’t standardize team-internal rituals like standups
- 49:21 – 53:41
Avoiding learning burnout: focus on execution, diagnose gaps, and build a toolbox
The conversation closes with advice on managing the overwhelming amount of PM content. Melissa recommends learning primarily through doing the job, then reflecting on what’s not working and deep-diving only into the specific skill gaps that matter. She also encourages adapting frameworks (including Agile) to serve the team rather than following dogma.
- •Execution is the best teacher; start by doing the job and reflecting
- •Identify what’s not working and deep-dive on targeted gaps (research, analytics, etc.)
- •Don’t try to absorb all advice—pick what helps and discard what doesn’t
- •Iterate on processes; if Scrum/Agile rituals don’t serve you, change them
- •Create a personal toolbox of practices that work in your context
