Strategy & Positioning 20 guests | 56 insights

Defining Product Strategy

Transform vision into a concrete plan of action by making hard choices that drive customer behavior.

Includes our free 8-email course on making your product team AI-native. Unsubscribe anytime.

The Guide

5 key steps synthesized from 20 experts.

1

Identify the crux through diagnosis

Begin by asking what is truly holding the organization back. Move beyond simple statements of value like 'not growing fast enough' to formulate a hypothesis about how market dynamics, technical limitations, or user behavior are creating a barrier.

Featured guest perspectives
"So I was hired to do a foundry for a company and they said, 'Well, our diagnosis is not growing fast enough.' Okay, let's get into that because that's not a diagnosis, that's a statement. It's a statement of value, you would like to grow faster than you are."
— Richard Rumelt
2

Apply the strategy choice cascade

Answer five integrated questions to form a coherent plan: define your winning aspiration, specify where you will play, determine how you will win, identify required capabilities, and establish management systems. Ensure these choices reinforce each other rather than being a list of disconnected projects.

Featured guest perspectives
"You have to have answers to five questions. What's your winning aspiration? Where to play? How can you win? What capabilities do you have to have that your competitors don't? And then, what enabling management systems do you have to put in place?"
— Roger Martin
"I'm a big believer that people down organization have to make really important strategic choices or bad things are going to happen, if they make really great ones, good things are going to happen, and they get trained to be a CEO someday."
— Roger Martin
"Strategy is really just an integrated set of choices that outline how you're going to win in whatever marketplace you choose. And so, a good product strategy is going to answer questions like what's your winning aspiration? But maybe more importantly, where are you going to play?"
— Annie Pearl
3

Visualize the future state

Spend time with designers crafting detailed prototypes and Loom walkthroughs of the future product. High-fidelity visualization anchors the team in a shared reality and prevents the misalignment that often occurs with abstract strategic pillars.

Featured guest perspectives
"There are three parts to a strategy: (1) vision, (2) strategic framework, and (3) roadmap. You can get started with whichever one calls to you:"
— Lenny Rachitsky
4

Codify the strategy into a simple narrative

Distill the strategy into a clear document featuring three core components: strategic pillars, non-focus areas, and the rationale for each choice. Use the rule of three and simple 'fill-in-the-blanks' sentences to ensure the plan is memorable and influences daily decision-making.

Featured guest perspectives
"The first is a handful of areas to focus on and I call these strategic pillars and then a whole bunch of areas that are explicitly not the focus. And the third component is why. So why are the focus areas, A, B and C? Why are these whole bunch of areas not the focus?"
— Chandra Janakiraman
"Even the most genius of strategies will fail if communicated badly. To influence day-to-day activities, strategies need to be simple enough for leaders at every level of the organization to understand, communicate, and remember — a strategy that gathers dust on a shelf is nothing more than an expensive bookend."
— Lenny Rachitsky
"The Founding Hypothesis is a handy Mad Libs–style sentence that we can fill in to understand and test a team’s strategy. Yes, the Founding Hypothesis is simple, but that’s exactly what makes it so powerful."
— Lenny Rachitsky
5

Execute a structured strategy sprint

Dedicate a focused period, such as a two-day workshop, to transform user problems into high-impact strategic pillars. Use a rigorous scoring system to filter a large list of problem statements down to the handful of initiatives that will actually move the needle.

Featured guest perspectives
"The Foundation Sprint is a two-day workshop for a team at the beginning of a big project. On the morning of day one, you’ll define the basics of your project; then, in the afternoon, you’ll craft differentiation to help you stand out from the competition. On day two, you’ll evaluate multiple options and choose an approach to your project."
— Lenny Rachitsky
"Day 2 of the strategy sprint is the single most important day of the whole 8-to-12-week strategy process. This is where the actual strategic pillars are selected."
— Lenny Rachitsky

Get this guide as an AI skill for Claude Code

Includes our free 8-email course on making your product team AI-native. Unsubscribe anytime.

Install This Skill

Add this skill to Claude Code, Cursor, or any AI coding assistant that supports Agent Skills.

Quick Install (Recommended)

Install this skill directly using npx:

npx skills add RefoundAI/lenny-skills --skill defining-product-strategy

Or install all 76 skills:

npx skills add RefoundAI/lenny-skills
View on GitHub →
Manual Installation
1

Download the skill

Download Skill (.zip)
2

Add to your project

Create a folder in your project root and add the skill file:

.claude/skills/defining-product-strategy/SKILL.md
3

Start using it

Claude will automatically detect and use the skill when relevant. You can also invoke it directly:

Help me with defining product strategy

Guest Perspectives

Deep dive into what 19 podcast guests shared about defining product strategy.

Anneka Gupta 1 quote
Listen to episode →
"When people say, 'I want someone that's strategic,' what they're really saying is, 'I want someone that can come up with and articulate a compelling and simple why behind the decisions and the direction of the company and product.' So that's number one. And the second piece is, 'I want someone that's going to champion and be a change agent to do things that may be hard but actually best for the long-term interest of the product or company, even though those things are not going to be easy to execute on.'"
Tactical:
  • Distill complex company or product decisions into a single, compelling narrative that provides a simple 'why' for the team.
  • Act as a change agent by pushing for hard decisions that serve the company’s long-term health over short-term convenience.
  • Use your deep understanding of business details to ensure your strategic narrative is rooted in financial and operational reality.
View all skills from Anneka Gupta →
Annie Pearl 1 quote
Listen to episode →
"Strategy is really just an integrated set of choices that outline how you're going to win in whatever marketplace you choose. And so, a good product strategy is going to answer questions like what's your winning aspiration? But maybe more importantly, where are you going to play?"
Tactical:
  • Define your winning aspiration to outline the ultimate goal for your product in the marketplace.
  • Identify the specific markets, segments, and personas where you will focus your efforts.
  • Determine how you will win against competitors within your chosen target audience.
View all skills from Annie Pearl →
Asha Sharma 1 quote
Listen to episode →
"And so you really need to bet on a platform or some app server type layer that allows you to swap things in and out and not really be beholden to anything, any one technology or any one tool because the reality is the whole thing is going to change."
Tactical:
  • Invest in an app-server layer that enables modular swapping of underlying models and specialized tools.
  • Prioritize foundational infrastructure like measurement, observability, and evals as the core platform value.
  • Build for extensibility to allow for the rapid integration of thousands of emerging specialized AI tools.
View all skills from Asha Sharma →
Chandra Janakiraman 1 quote
Listen to episode →
"The first is a handful of areas to focus on and I call these strategic pillars and then a whole bunch of areas that are explicitly not the focus. And the third component is why. So why are the focus areas, A, B and C? Why are these whole bunch of areas not the focus?"
Tactical:
  • Structure the document around three core components: strategic pillars, non-focus areas, and the rationale behind each choice.
  • Allocate one to two weeks of the development cycle specifically for synthesizing findings into a concise written narrative.
  • Explicitly name non-focus areas to ensure the organization understands what the team is choosing to ignore.
View all skills from Chandra Janakiraman →
Dharmesh Shah 1 quote
Listen to episode →
"Some of the best startup advice I've heard is startups should focus on one thing and be really, really exceptionally world-class at that one thing. And one of our early zigs is we are going to do exactly the opposite of that."
Tactical:
  • Evaluate standard industry advice and determine if doing the opposite provides a strategic advantage.
  • Choose a product scope that aligns with your specific vision, even if it contradicts the 'focus on one thing' mantra.
  • Commit to 'zigging' where others 'zag' when you have high conviction in a non-consensus approach.
View all skills from Dharmesh Shah →
Hamilton Helmer 1 quote
Listen to episode →
"You're on a treadmill and if you stop running on that treadmill, you get creamed, but it's not power. The things that drive operational excellence can be mimicked."
Tactical:
  • Avoid relying on 'moving fast' or 'the best team' as a durable source of power in investment decks.
  • Identify the specific 'economic castle' structure that will protect your margins once you stop sprinting on the execution treadmill.
  • Look for cost or price advantages that remain durable even if your competitors' operational efficiency catches up to your own.
View all skills from Hamilton Helmer →
Jag Duggal 1 quote
Listen to episode →
"We may not be right, but at least we are clear. Even if your strategy isn't right, you have a very clear idea of what was supposed to be happening."
Tactical:
  • Prioritize clarity over certainty in strategic documentation to ensure everyone knows the intended path.
  • Ensure every new project has a clear thesis on why a customer should care.
  • Apply specific strengths against a core problem rather than just setting ambitious but vague goals.
View all skills from Jag Duggal →
Jeetu Patel 1 quote
"You have to know the difference between a megatrend and a hype cycle. When there's a megatrend, don't fight it. AI is a megatrend, one of the most foundational movements that we have seen in human history."
Tactical:
  • Prioritize markets characterized by a 'capabilities overhang' where the available science exceeds current user implementation.
  • Evaluate opportunities based on their ability to solve systemic global shifts, such as declining birth rates and demographic changes.
  • Avoid markets where the use case is a obvious hype cycle without long-term foundational utility.
View all skills from Jeetu Patel →
Jiaona Zhang 1 quote
Listen to episode →
"What, as a company is your strategic strength and what's in your wheelhouse? So for example, Airbnb, we weren't that strong in operations. Again, we're this platform with this marketplace."
Tactical:
  • Evaluate if a new product direction aligns with your existing organizational strengths.
  • Identify low-cost signals, like user reviews, that play to your platform's inherent strengths.
  • Avoid using 'blunt instruments' to solve problems that require more tailored, strategic approaches.
View all skills from Jiaona Zhang →
Kevin Aluwi 1 quote
Listen to episode →
"I think the insight that we got here was that there kind of needs to be a unifying concept across all of your services within the app for your users to be able to think about your product in a sensible way. And for us, the way that our customers thought about us was that they thought about the driver."
Tactical:
  • Identify a unifying concept (like "the driver") that bridges different service offerings intuitively.
  • Conduct UX research to verify if customers are even aware that secondary services exist within your app grid.
  • Avoid launching services that clash with the user's core mental model of what your platform provides.
View all skills from Kevin Aluwi →
Mayur Kamat 1 quote
Listen to episode →
"Strategy is a little bit overrated for product. For most product managers, your strategy should be, "How fast can I go from hypothesis to data?""
Tactical:
  • Minimize time spent on 'big picture' strategy that lacks data-driven support.
  • Build an experimentation engine to turn product development into a scientific process.
  • Optimize your team's velocity for the path from hypothesis to data acquisition.
View all skills from Mayur Kamat →
Richard Rumelt 5 quotes
Listen to episode →
"Well, a strategy is a design for overcoming a high-stakes challenge. It's a mixture of policy and action designed to deal with a challenge."
Tactical:
  • Define the high-stakes challenge your organization currently faces.
  • Establish a guiding policy that outlines how you will deal with that challenge.
  • Develop a set of coherent actions to implement your policy.
"Bad strategy, the standard bad strategy for a corporation is a set of profit goals or performance goals. A set of goals. Goals are the engineering of how companies work to some extent. But abstract, high-level goals, they're not strategy, they're something else."
Tactical:
  • Audit your strategy to ensure it isn't just a list of ambitions or performance targets.
  • Remove 'fluff' and word salad that uses fancy language to mask a lack of substance.
  • Check if your 'priorities' are actually a laundry list of wishes rather than a focused choice.
"Don't call it strategy, call it an action agenda. It's huge numbers of people out there willing to sell you advice on mission and your vision and your values, all these things that have to be in place before you can have strategy. That's not true. Begin to try to identify the one or two key challenges that can actually be addressed and what are we going to do about it?"
Tactical:
  • Identify the one or two key challenges that your team can actually solve right now.
  • Skip the focus on vision and values if they are delaying actual strategic thinking.
  • Specify exactly what actions you will take to address your diagnosed problems.
"If you're making Almond Joy candy bars or something, you don't really change your strategy constantly. If you're in the tech business, of course you have a shorter time horizon. And then the coherence and action is critical."
Tactical:
  • Adopt a shorter strategic time horizon if you are operating in a high-innovation industry.
  • Maintain a dual mindset of conviction in your current bet and a willingness to adapt as reality changes.
  • Prioritize coherent implementation over high-level conceptual frameworks.
"So I was hired to do a foundry for a company and they said, 'Well, our diagnosis is not growing fast enough.' Okay, let's get into that because that's not a diagnosis, that's a statement. It's a statement of value, you would like to grow faster than you are."
Tactical:
  • Structure offsites as 'foundries' focused on identifying the single most difficult challenge (the crux).
  • Reject surface-level goals as a diagnosis and push the group to identify what is actually holding them back.
  • End the session with a concrete 'action agenda' rather than a list of ambitions.
View all skills from Richard Rumelt →
Robby Stein 1 quote
Listen to episode →
"AI is expansionary, and so there's actually just more and more questions being asked and curiosity that can be fulfilled now with AI. And so that's where you get the growth. All the core Google search isn't really changing, in my opinion."
Tactical:
  • Identify 'expansionary' opportunities where new technology can answer questions that were previously impossible to ask.
  • Layer new modalities like visual search onto mature products to tap into massive, unmet scales of user intent.
  • Ensure that new features complement rather than disrupt the foundational needs that users already rely on your product for.
View all skills from Robby Stein →
Roger Martin 5 quotes
Listen to episode →
"You have to have answers to five questions. What's your winning aspiration? Where to play? How can you win? What capabilities do you have to have that your competitors don't? And then, what enabling management systems do you have to put in place?"
Tactical:
  • Define a winning aspiration that focuses on customer success.
  • Specify both where you will compete and the unique way you will win in that space.
  • Align your internal capabilities and management systems to support your specific choices.
"I'm a big believer that people down organization have to make really important strategic choices or bad things are going to happen, if they make really great ones, good things are going to happen, and they get trained to be a CEO someday."
Tactical:
  • Identify the strategic choices within your specific domain that directly impact customer behavior.
  • Reject the 'execution vs. strategy' dichotomy by viewing your role as making lower-level strategic choices.
  • Use your current role to practice making integrated choices that prepare you for future leadership.
"Strategy is an integrated set of choices that compels desired customer action."
Tactical:
  • Define the exact customer action you want to compel through your strategic choices.
  • Measure success based on customer preference and choice relative to your competitors.
  • Iterate on your choices if customers are not responding in the way your strategy predicted.
"I have never met this mythical beast called a great natural strategist. Great strategists have all one thing in common, they just practice."
Tactical:
  • Commit to regular 'strategy reps' by applying the choice cascade to small, everyday decisions.
  • Study successful strategies to understand how the five questions were integrated.
  • Treat every strategic outcome as a learning opportunity to improve your future decision-making.
"Strategy is an integrated set of choices that compels desired customer action."
Tactical:
  • Start your strategy by identifying a specific, unmet customer need.
  • Verify that your 'how to win' choices provide a solution that customers actually value.
  • Reject market opportunities that do not align with your core capabilities and winning aspiration.
View all skills from Roger Martin →
Shreyas Doshi Live 1 quote
Listen to episode →
"And the interesting I found is that because I had a real product strategy, not one of those fake ones, a real product strategy that I had gotten alignment on with everybody, my planning for this major product for Stripe took me like three days."
Tactical:
  • Invest in creating a 'real' product strategy that provides clear direction for future trade-offs.
  • Ensure your strategy is robust enough to make future resource allocation decisions obvious.
  • Use strategic alignment as a filter to eliminate non-essential work and redundant meetings.
View all skills from Shreyas Doshi Live →
Shweta Shriva 1 quote
Listen to episode →
"Are you proactively trying to challenge your own assumptions is extremely important, right? As a big enough product manager as well as a seasoned product leader, if you're not doing enough of that, then I think you might not be listening. If there's no conflict, if there's no contention, then something is missing."
Tactical:
  • View internal contention or conflict as a healthy signal that your team is questioning established norms rather than stagnating.
  • Audit your product’s foundational assumptions regularly to ensure they still align with current market and technical realities.
  • Discard 'bad' historical data or legacy practices even when they were once part of a successful model.
View all skills from Shweta Shriva →
Teresa Torres 1 quote
"So it's a tree visual. So it's just like a decision tree. It starts with an outcome at the root of the tree, and then it branches into the opportunity space and then it branches into solutions, and maybe even assumption tests from there."
Tactical:
  • Place a single product outcome at the root of the decision tree.
  • Branch into the opportunity space by mapping specific unmet needs, pain points, and desires.
  • Use the visual to create a shared understanding and get stakeholder buy-in on strategic decisions.
View all skills from Teresa Torres →
Varun Mohan 1 quote
Listen to episode →
"We should be cannibalizing the existing state of our product every six to 12 months. Every six to 12 months, it should make our existing product look silly. It should almost make the form factor of existing product look dumb."
Tactical:
  • Dedicate resources to secret, longer-term bets that target the next 6-12 months of development.
  • Cultivate an organization that is comfortable discarding its current success to find the next breakthrough.
View all skills from Varun Mohan →
Vijay 1 quote
Listen to episode →
"The issue for us at the time was that we took people away from the investment in our core product to go do those other things. We moved people, right? And so the trap there is that you leave yourself right for disruption in your core because someone else can out invests you in that core."
Tactical:
  • Continue to out-invest all competitors in your core product to maintain market leadership and prevent disruption.
  • Invest profits or venture capital into new products rather than reassigning people from the core team.
  • Avoid taking resources away from the core until functionality gaps are closed to prevent distraction and churn.
View all skills from Vijay →