Product Management 101 guests | 143 insights

Defining Product Vision

Product vision is the inspiring picture of what the world looks like when you succeed. It describes a future state for users that is agnostic of your specific solution—ambitious enough to be motivating, concrete enough that people can visualize it. A strong vision serves as the organizing principle for all decisions, from hiring to feature prioritization, and keeps teams building cathedrals instead of laying bricks.

The Guide

6 key steps synthesized from 101 experts.

1

Describe the future world, not your product

A powerful vision describes a future state for users that doesn't mention your company, product, or solution. Prefix vision statements with 'In the future...' to ensure long-term focus. The goal is to create an aspirational destination that pulls everyone forward, not a product description that constrains thinking.

Featured guest perspectives
"The vision is the nirvana state that you aim to enable for your users and customers in five to 10 years... It should be bound to your target market. So not too wide and not too narrow. And critically it should not mention your company, your product, or anything solution related at all."
— Ben Williams
"Imagine a world where someone can feel this way about their money.' And it's like, 'And then this thing will do that.' That's the product strategy. It's how you execute on it."
— Chris Hutchins
"Disneyland, still the best vision statement of all time, which is the happiest place on earth. So once you tell an employee this is supposed to be the happiest place on earth, then you're signaling all sorts of things about how they need to pick up the trash and how they need to show up on time."
— Bob Baxley
2

Make the vision concrete and visual

Abstract strategy documents don't create alignment. Use prototypes, mockups, and wireframes to make the vision tangible. When people can see the end state, they make better daily decisions. A strategy document isn't complete without visuals that show what the product will look like when the vision is realized.

Featured guest perspectives
"At Canva, we're all about visual communications... visions in the very visual sense. We need to be able to see it. We need mock-ups. We need prototypes. You need to get that idea out of your head and present it to someone in a visual form."
— Cam Adams
"One of the things that we said with stake that we put in the ground was the strategy doc wouldn't be complete without wireframes... when you actually can show people wireframes of what the product will look like when that strategy is implemented, it creates much more alignment."
— Ravi Mehta
"I actually took a screenshot of the Google Play Store... and then I created rounded rectangles, just blank rectangles, four panels. And then I printed that out and I gave everyone a sheet and I said, 'If we solve these problems... what would be the screenshots?'"
— Ebi Atawodi
3

Use emotional metaphors to guide decentralized decisions

When teams share an emotional understanding of what the product should feel like, they naturally make consistent choices without top-down control. Define the 'feeling' using relatable real-world analogies. This shared mental model guides everything from iconography to communication patterns.

Featured guest perspectives
"If we all agree that the feeling of something should be, I'm sitting in Dolores Park with my friends on a sunny Saturday, then people will just naturally build something that feels more consistent. You know what the iconography, the designers know what iconography should look like."
— Ami Vora
"Ultimately, we came up with the idea that we were in the belong anywhere business. Airbnb was not in home sharing, we were in belonging anywhere."
— Chip Conley
4

Think 10X, not incremental

Ambitious visions force teams to abandon incrementalism and find first-principles solutions. When you push for 10X improvement, people think about the problem differently. Start with the unconstrained '15 out of 10' experience, then work backwards to what's feasible. This prevents teams from settling into local maxima.

Featured guest perspectives
"The exercise isn't necessarily to say if people say they want to hit a goal, I say, okay, I added a zero, you have to hit that goal. It's more the exercise of what would it take to be 10X bigger or do something 10 times better? Because what you find is when you push people, they will sometimes think about the problem differently."
— Brian Chesky
"What Brian taught us was think unconstrained first. Think about a 15 out of 10 experience, design the ideal end state first. In most companies, the designers and PM start by saying, 'Okay, 10 is perfect. We can probably do seven. Let's start at seven.' It's a very constrained minded thinking."
— Sanchan Saxena
"The job is to delight customers. Like Peter Thiel, his book, From Zero to One. The job of an entrepreneur at the beginning is just to find out something that's 10X better."
— Gibson Biddle
5

Use backcasting to work from the future backward

Instead of forecasting from present constraints, start by imagining a radically different future and work backwards. This 'backcasting' approach helps you discover non-obvious paths and avoid the comparison trap of just being 'better' than competitors. Great founders propose futures that deny the premise of current rules.

Featured guest perspectives
"Great founders, pattern breakers back cast, they say, it's a given that the future has to be radically different for me to be a big winner, and so, I'm going to look for radically different futures and work backwards from those radically different futures."
— Mike Maples Jr
"I talk about look in the future and then think backwards a lot, right? It's like what would we want to have done 20 years ago on this?"
— Tobi Lutke
"I really like to start by just imagining what is the future that you actually want. Right now I have a wall in my house in my office, which is my vision for what I'd like the world to look like in 2050."
— Melanie Perkins
6

Repeat the vision relentlessly

Vision isn't a one-time announcement. It requires constant, repetitive storytelling to stick. Share it at every all-hands meeting. Ensure every team member can articulate why the product exists and what future you're building toward. You're communicating enough when you feel like you're repeating yourself endlessly.

Featured guest perspectives
"You have to state your vision and your mission and why you're here, every all-hands. It seems so crazy because it's core to you why we would build this... you need everyone to be able to... have a very cohesive narrative in their head."
— Chris Hutchins
"It was also just storytelling and just repetitive storytelling around this is the vision, these are the bets we're making. Here's why. And you can't just tell that story once."
— Kayvon Beykpour
"The core insight here is that you want your teams to feel like they're building a cathedral and not laying bricks... take the time to help the team take a broader frame, open the aperture a little bit and have a view of what the cathedral is."
— Lane Shackleton

Common Mistakes

  • Writing a vision that's actually a product description or marketing tagline
  • Creating vision documents without wireframes or visuals
  • Letting current technical constraints limit your imagination
  • Announcing the vision once and assuming everyone absorbed it
  • Building by committee instead of championing a singular, opinionated direction

Signs You're Doing It Well

  • Anyone on the team can explain what the world looks like when you succeed
  • Teams make consistent decisions autonomously because they understand the vision
  • New ideas are evaluated against the vision, not just ROI
  • Your vision inspires people to join the company
  • The vision hasn't changed fundamentally in years, even as tactics evolve

All Guest Perspectives

Deep dive into what all 101 guests shared about defining product vision.

Alex Hardimen 3 quotes
Listen to episode →
"At the most basic level, I would say that our product is our journalism, which we then marry with a really compelling and useful user experience, in a way that helps people really act on our journalism so that they can understand and engage with the world around them."
Tactical:
  • Marry core content with compelling UX
  • Focus on helping users 'act' on the information provided
"We have the solar system metaphor where for us news is the sun in the sense that it's why we exist. It is what gives us our brand heritage and reputation. It's what instills trust. It's also where we just have the largest audience when you think about a funnel for our portfolio, and it's also where we just have the most amount of high quality coverage. But then that sun helps you give birth to other satellite planets or products that have a lot of the same DNA."
Tactical:
  • Identify the 'sun' product that drives brand heritage and trust
  • Build satellite products that share the core DNA of the primary product
  • Use the primary product as the top-of-funnel for the rest of the portfolio
"One thing that's really interesting is that our impact and our business goals are in service of our mission, which is to seek the truth and help people understand the world, not the other way around. What it means is that the way that we think about impact is growing a giant subscription business. That business exists to strengthen an informed democracy."
Tactical:
  • Define business metrics as being 'in service' of the mission
  • Measure impact not just by revenue, but by mission-driven outcomes like policy changes
View all skills from Alex Hardimen →
Alisa Cohn 1 quote
Listen to episode →
"Vision of the company. So when this company is successful, what does that look like?... What that might look like is a big venture outcome that we all read about. And if you are both assuming that you both think the same thing but aren't talking about it explicitly... then what often happens if you have differences is they come home to roost."
Tactical:
  • Ask: 'What is the vision for the company when it reaches its full potential?'
  • Discuss the trade-offs inherent in different visions (e.g., lifestyle business vs. venture scale)
View all skills from Alisa Cohn →
Alex Komoroske 1 quote
Listen to episode →
"You need coherence about where you're going and the way you get that is by creating a North Star for yourself. It should be in three to five years in the future, it should be very low resolution. It should describe a thing that every single person who reads it who has any kind of knowledge that might be useful or relevant agrees that it is plausible."
Tactical:
  • Set a 3-5 year vision that is 'low resolution' to allow for adaptation.
  • Ensure the vision is plausible enough that experts across functions (legal, eng, etc.) can see how it could work.
View all skills from Alex Komoroske →
Ami Vora 2 quotes
Listen to episode →
"If we all agree that the feeling of something should be, I'm sitting in Dolores Park with my friends on a sunny Saturday, then people will just naturally build something that feels more consistent. You know what the iconography, the designers know what iconography should look like. You know what the communication and join pattern should look like."
Tactical:
  • Define the 'feeling' of the product using a relatable real-world analogy (e.g., 'sitting in a park' or 'face-to-face communication').
  • Use these metaphors to ensure consistency across different teams without micromanaging every detail.
"For strategy to be useful, it actually has to change our behavior as a team to create better customer outcomes... What's the change, or coming out with a strategy that'll align people because we have the story, we have the narrative, we have the sequence."
Tactical:
  • Evaluate strategy by asking: 'What will we do differently tomorrow because of this?'
  • Use narrative and sequence to align the team on the long-term path.
View all skills from Ami Vora →
Andy Raskin 1 quote
Listen to episode →
"The one thing I say is it's this one story that the CEO uses to drive success in marketing, sales, but also product. That it becomes like a north star, strategic north star for product roadmap, for fundraising, for recruiting, really everything."
Tactical:
  • Ensure the product vision is embedded within a larger narrative about market change.
View all skills from Andy Raskin →
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? What are the markets you're going to go after? What are the segments of those markets? What are the personas in the segments of those markets? And then, how are you going to win with a target audience?"
Tactical:
  • Define the 'winning aspiration' first.
  • Identify specific markets, segments, and personas to target.
  • Articulate exactly how you will win with that target audience.
View all skills from Annie Pearl →
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.""
Tactical:
  • Focus on articulating a simple and compelling 'why' behind every major product decision.
  • Act as a change agent for initiatives that are best for the long-term interest of the company, even if they are hard to execute.
View all skills from Anneka Gupta →
April Dunford 1 quote
Listen to episode →
"The easiest way to take over a great big market is to define a segment of the market that is underserved by the market leader... knocking over that pin enables us to get to the three pins right beside it. And so now I'm established here as a beachhead and I can go get the next three pins."
Tactical:
  • Identify a 'lead pin' segment that is underserved by the current market leader.
  • Focus all resources on dominating that specific niche beachhead.
  • Sequence expansion into adjacent segments once the initial niche is secured.
View all skills from April Dunford →
Aparna Chennapragada 1 quote
Listen to episode →
"You do want to look for at least two out of these three factors, inflection points here if you want to make a really good product. Number one is there a... Shift is a step function in the tech... The second factor that we should look for is, what is the consumer behavior shift?... And I'd say the third inflection point, particularly I would say in enterprise but also in consumer, is the business model shift."
Tactical:
  • Identify step-functions in technology (like LLMs or mobile) that enable new solutions
  • Look for changes in how consumers use existing tools (like using a camera as a keyboard)
  • Evaluate if a new business model (like outcome-based monetization) is possible
View all skills from Aparna Chennapragada →
Ayo Omojola 1 quote
Listen to episode →
"Cash App, as a team we really cared about what we could do that was different and better than what else existed in-market. Being different is not enough... Being better is not enough... It has to be better than what exists today in a way that matters to the end user"
Tactical:
  • Identify what exists in the market and intentionally build something else.
  • Ensure the improvement is meaningful to the end user's experience.
  • Avoid just making a 'better' version that costs more without unique value.
View all skills from Ayo Omojola →
Archie Abrams 1 quote
Listen to episode →
"The technical architecture determines strategy in a technology company even more than the what and who we're building for. If you build the right technical how and set yourself up to have a platform that can be adaptable, flexible, that is incredibly valuable over the long term."
Tactical:
  • Evaluate product roadmaps based on whether the technical foundation allows for future adaptability.
  • Involve senior leadership in deep technical reviews to ensure architecture aligns with a 100-year vision.
View all skills from Archie Abrams →
Ben Williams 1 quote
Listen to episode →
"The vision is the nirvana state that you aim to enable for your users and customers in five to 10 years... It should be bound to your target market. So not too wide and not too narrow. And critically it should not mention your company, your product, or anything solution related at all."
Tactical:
  • Prefix vision statements with 'In the future...' to ensure a long-term focus
  • Ensure the vision does not mention the product or company name
View all skills from Ben Williams →
Benjamin Mann 1 quote
Listen to episode →
"The second one is Good Strategy Bad Strategy by Richard Rumelt. Just thinking about in a very clear way, how do you build product? It's one of the best strategy books I've read and strategy is a hard word to even think about in many ways."
Tactical:
  • Differentiate between 'good strategy' (diagnosis and action) and 'bad strategy' (fluff and goals)
  • Study the 'Alignment Problem' to understand the long-term stakes of the product's impact on society
View all skills from Benjamin Mann →
Ben Horowitz 1 quote
Listen to episode →
"You're just the keeper of the vision... somebody who's got to consolidate, get all the good ideas, prioritize them, decide which good ideas we're going to do"
Tactical:
  • Work backwards from the goal of a product that 'works' and customers love
  • Maintain the vision as a filter for which 'good ideas' to actually execute
View all skills from Ben Horowitz →
Bob Baxley 1 quote
Listen to episode →
"Disneyland, still the best vision statement of all time, which is the happiest place on earth. So once you tell an employee this is supposed to be the happiest place on earth, then you're signaling all sorts of things about how they need to pick up the trash and how they need to show up on time and how they need to wear their uniform."
Tactical:
  • Create a vision that is 'always over the horizon' to provide a permanent organizing principle for growth and acquisitions.
View all skills from Bob Baxley →
Benjamin Lauzier 1 quote
Listen to episode →
"Lyft's vision was always anchored around transportation, people of transportation... Uber had... this notion of being a logistics platform for assets in the world, for transporting people, for transporting things... I think Uber was able to rebound much more quickly because of how diversified the business was."
Tactical:
  • Evaluate if your vision is anchored to a specific use case or a broader capability (e.g., 'moving people' vs. 'logistics').
  • Consider how a more diversified vision allows for pivoting into adjacent categories (like food delivery) during crises.
View all skills from Benjamin Lauzier →
Brandon Chu 1 quote
Listen to episode →
"put forward a vision for what that team's going to accomplish that year, whether that is a directional change or even specific outcomes in some cases. And we spend time aligning with both Tobi, the rest of the C level exec team, even sometimes the board on what that is"
Tactical:
  • Align the executive team and board on broad directional changes annually
  • Set a 'North Star' that allows for chaotic iteration underneath it
View all skills from Brandon Chu →
Cam Adams 1 quote
Listen to episode →
"At Canva, we're all about visual communications... one of the things that's very particular about Canva is really setting visions. And I'm in visions, not just in the sense of looking forward two, three years, but also visions in the very visual sense. We need to be able to see it. We need mock-ups. We need prototypes. You need to get that idea out of your head and present it to someone in a visual form that helps you talk about and communicate about it."
Tactical:
  • Use visual artifacts like pitch decks and prototypes to align the team on future direction
  • Ensure the vision is tangible enough that stakeholders can 'see' the end state
View all skills from Cam Adams →
Brian Chesky 1 quote
Listen to episode →
"The exercise isn't necessarily to say if people say they want to hit a goal, I say, okay, I added a zero, you have to hit that goal. It's more the exercise of what would it take to be 10X bigger or do something 10 times better? Because what you find is when you push people, they will sometimes think about the problem differently."
Tactical:
  • Ask 'What would it take to 10X this?' to break current processes
  • Use ambitious scale as a tool for first-principles thinking
View all skills from Brian Chesky →
Bret Taylor 1 quote
Listen to episode →
"What if we inverted the hierarchy here and made the map the canvas?"
Tactical:
  • Experiment with 'inverting the hierarchy' of your product's UI to find a more compelling canvas
View all skills from Bret Taylor →
Casey Winters 1 quote
Listen to episode →
"The challenge you practically deal with as a product leader is you end up recruiting, and managing, and growing a lot of executional people who can get stuff done, but if they want to get to the director level or if they want to get to my level, they need to get more strategic."
Tactical:
  • Practice writing comprehensive strategy documents without heavy guidance from leadership
  • Study industry changes and competitor features to build a 'strategic' muscle
View all skills from Casey Winters →
Chandra Janakiraman 3 quotes
Listen to episode →
"Product strategy sits between the mission and vision and the plan... It forces choice to deploy scarce resources to generate maximum impact."
Tactical:
  • Position strategy between the mission/vision and the roadmap
  • Focus on achieving 'resonance' between the product and the market
"What does the product look like in five to 10 years? Why is the world better in 10 years? And what is the most exciting version of that view?"
Tactical:
  • Ask leaders to describe a 'day in the life' of a user 5-10 years in the future
  • Cluster long-term ideas into three distinct, cohesive versions of the future
  • Create 'concept cars' or prototypes to inspire the team without the intent of immediate commercialization
"I want you to imagine the progress on all these strategic pillars and what the headline of that newspaper article looks like. It's called a newspaper headline approach."
Tactical:
  • Have every team member write a mock newspaper headline for the product 2 years out
  • Use a 'blender' approach to combine common themes from these headlines into a single winning aspiration
View all skills from Chandra Janakiraman →
Christina Wodtke 2 quotes
Listen to episode →
"if you think about strategy as a strongly held hypothesis about a way to win in the market and fulfill our vision, then you can say, "Well, our mission is this, or vision..." ... Strategy answers those questions. They say, "We're going to have a game. It's going to be an Apple Arcade. We have a hypothesis that's actually going to help us.""
Tactical:
  • Define strategy as the specific choices (platform, business model, target) made to fulfill the mission.
  • Ensure the quarterly objective is a direct step toward the strategic hypothesis.
"the product manager serves the business. That's their role... they need to understand business models, they need to understand how to do a target market, and what is a target market, why is that target market the right one to go after, and how is it going to grow"
Tactical:
  • Deeply study business models (subscriptions vs. one-off sales) to understand how the company survives.
  • Focus on target market selection and growth trends as core PM responsibilities.
View all skills from Christina Wodtke →
Chris Hutchins 2 quotes
Listen to episode →
"you have to state your vision and your mission and why you're here, every all-hands. It seems so crazy because it's core to you why we would build this, what it's purposes, why it's amazing... you need everyone to be able to... have a very cohesive narrative in their head."
Tactical:
  • Share the mission and vision at every all-hands meeting
  • Ensure every team member can succinctly explain why the product exists
"Imagine a world where someone can feel this way about their money.' And it's like, 'And then this thing will do that.' That's the product strategy. It's how you execute on it."
Tactical:
  • Focus on the 'feeling' or benefit you want the user to have
  • Distinguish between the aspirational vision and the tactical strategy
View all skills from Chris Hutchins →
Chip Conley 2 quotes
Listen to episode →
"Ultimately, we came up with the idea that we were in the belong anywhere business. Airbnb was not in home sharing, we were in belonging anywhere."
Tactical:
  • Identify the 'unrecognized need' at the top of the customer pyramid to define your vision
  • Use the vision as an organizing principle for marketing and host education
"The customer pyramid, briefly... is meeting expectations is the base, meeting desires is in the middle, and then meeting unrecognized needs."
Tactical:
  • Map product features against expectations, desires, and unrecognized needs
View all skills from Chip Conley →
Christopher Lochhead 2 quotes
Listen to episode →
"The category makes the product, the category makes the brand, the category makes the company."
Tactical:
  • Focus on designing the market space rather than just the product features.
"Legendary entrepreneurs don't just think they know the future is going to be different, because they're designing that different future. And the problem they're focused on matters to them so much that the fact that the problem continues to persist makes them batshit crazy."
Tactical:
  • Identify a problem that drives you 'insane' and design a future where it is solved.
View all skills from Christopher Lochhead →
Claire Hughes Johnson 1 quote
Listen to episode →
"The mission is one line... you need a little more meat behind that... Articulating that, because until I said that to you... you might not understand why we invested in certain things or why it meant so much to us in terms of our user experience and the mission."
Tactical:
  • Draft a one-line mission statement that is aspirational but intellectual
  • Define 3-5 long-term goals (3-5 year horizon) that explain why the company exists
  • Use these goals to explain the rationale behind specific product investments
View all skills from Claire Hughes Johnson →
David Placek 1 quote
Listen to episode →
"We really do have to help people think about, 'It's not about the past. You're actually creating the future.' And we really talk to people and emphasize the idea, 'This isn't a name you're creating. We're creating an experience for you.'"
Tactical:
  • Focus on the desired future behavior and experience when selecting a name
View all skills from David Placek →
Dalton Caldwell 1 quote
Listen to episode →
"It is only a tarpit if it seems like it's not. If it's just a regular idea that is hard, that is not a tarpit. The weird aspect of what we call a tarpit idea is an idea that a lot of people come up with and then it seems like an unsolved problem and you get lots of positive feedback for. Right? And you have a really good set of arguments that it's a really good startup idea. And that's different than a bad startup idea."
Tactical:
  • Be skeptical of ideas that receive easy, polite validation but have a history of failure (e.g., friend coordination apps)
  • Look for structural reasons why an 'obvious' problem remains unsolved before committing to it
View all skills from Dalton Caldwell →
Dylan Field 2 quotes
Listen to episode →
"I think for us we had a framing of, we're going to go trace a workflow. If you've got an idea, go express it through Slides or hop in FigJam and brainstorm with your team. Okay, what's next? Go design, hop in Figma Design. If you need to go to development after that, Dev Mode will help you take you there."
Tactical:
  • Identify gaps in the user's journey from idea to finished product
  • Create separate product surfaces for distinct stages of the workflow (e.g., brainstorming vs. high-fidelity design)
"You have to go from strength to strength, and you can't always just be obsessed with what's the next biggest TAM... we looked to the Bureau of Labor Statistics at the start of Figma, and it was like 250,000 designers in the world was what it said. Probably wrong at the time, but also it was a point in time and the industry is about to change."
Tactical:
  • Prioritize following the user workflow over descending TAM lists
  • Look for trends where value is moving 'up the stack' to predict market expansion
View all skills from Dylan Field →
Edwin Chen 1 quote
Listen to episode →
"I would say don't pivot. Don't put scale. Don't hire that Stanford grad who simply wants to add a hot company to your resume, just build the one thing only you can build, a thing that wouldn't exist without the insight and expertise that only you have."
Tactical:
  • Identify the unique problem that only your specific expertise can solve
  • Resist the urge to pivot frequently in search of easy growth
View all skills from Edwin Chen →
Eeke de Milliano 1 quote
Listen to episode →
"Crazy Ideas... David will send out a blank doc to the org and it's titled Crazy Ideas. The Prompt is, 'Crazy ideas are ideas that we shouldn't, obviously, do. There's a 90% chance that they make no sense. But in the 10% chance that they do, they will make a 10x to 100x difference.'"
Tactical:
  • Circulate a blank 'Crazy Ideas' document annually
  • Encourage ideas that have a high probability of failure but massive potential upside
View all skills from Eeke de Milliano →
Eoghan McCabe 1 quote
Listen to episode →
"Strategically we were all over the place and I said, 'We're doing service.' ... It was the type of decision that where I had to practice the professional CEO approach, which is, 'Hey folks, what do you all think? Let's take everyone's input. Let's put it all down on a spreadsheet.' ... I said, 'Sorry, this is what we're doing.'"
Tactical:
  • Identify the single most promising market opportunity (e.g., Customer Service).
  • Explicitly stop work on secondary products or segments to focus resources.
View all skills from Eoghan McCabe →
Eric Simons 1 quote
Listen to episode →
"WebContainer was the bet, that we made the company on. Just to be clear. StackBlitz was a browser-based, deep technology play on, 'Can we make a web assembly based operating system that can boot in a browser, in like a hundred milliseconds, and run full on development tool chains?'"
Tactical:
  • Identify emerging platform capabilities (like WebAssembly) that enable previously impossible architectures
  • Commit to a long-term technical bet even if the immediate problem-solution fit isn't clear
View all skills from Eric Simons →
Evan LaPointe 1 quote
Listen to episode →
"Your brain is going to sort those ideas into believed, believable, kind of conceivable and inconceivable... A lot of the vision thinking and dialogue that happens inside of businesses directly activates people's inconceivable response without any self-awareness that, that's a personal problem, not a objective problem."
Tactical:
  • Recognize your own 'unbelievable' threshold and when your brain is rejecting an idea based on personality rather than logic.
  • Translate visionary ideas into 'believable' language for stakeholders who are high in conscientiousness and low in openness.
View all skills from Evan LaPointe →
Ethan Evans 1 quote
Listen to episode →
"To invent systematically, first you do need to be somewhat of an expert in whatever area you want to invent... then the second thing people don't do is they don't spend dedicated time actually thinking. They feel like, 'Invention is just going to come to me.' When I want to invent, I get away from all my devices. I go in a room with the problem I have, and I force myself to actually concentrate on what do I know and how can I invent?"
Tactical:
  • Block off two hours of dedicated thinking time at least once a month
  • Remove all digital devices to ensure deep concentration on a specific problem
  • Try combining two existing, unrelated concepts to generate a new invention
View all skills from Ethan Evans →
Fareed Mosavat 1 quote
Listen to episode →
"The way I think about product work... first, feature work... second is growth work... third is what we call product market fit expansion... and then there's the fourth that is always forgotten by a lot of PMs which is scaling work."
Tactical:
  • Categorize your current roadmap items into these four buckets to ensure a balanced portfolio
  • Identify which type of work you are naturally an expert in and intentionally build knowledge in the other three
  • Recognize that 'scaling work' includes not just technical debt but also 'user scaling' problems like trust and safety
View all skills from Fareed Mosavat →
Gaurav Misra 1 quote
Listen to episode →
"A lot of it was done based on this type of pillar-based thinking of this is our mission, this is what we're trying to do, does it fit within or is it outside?"
Tactical:
  • Define core product pillars (e.g., private sharing, safety) to filter out features that don't align with the mission.
  • Reject features that conflict with the mission, even if they offer high engagement potential.
View all skills from Gaurav Misra →
Geoff Charles 1 quote
Listen to episode →
"Strategy is about how do we get to our goals? And it's not a roadmap and it's not a vision, it's something right in between that... Figure out why we're uniquely positioned as a company to get after that goal."
Tactical:
  • Identify components or expertise that can be reused to increase velocity.
  • Define the 'right to win' based on existing infrastructure, data, or customer access.
View all skills from Geoff Charles →
Gibson Biddle 2 quotes
Listen to episode →
"The job is to delight customers. Like Peter Thiel, his book, From Zero to One. The job of an entrepreneur at the beginning is just to find out something that's 10X better. Delight is trying to work in that magnitude."
Tactical:
  • Aim for 'delight' rather than just 'satisfaction'
  • Look for 10X improvements over existing solutions
"to delight customers in hard to copy margin enhancing ways. So, there's kind of these three parts, customers, hard to copy, margin enhancing."
Tactical:
  • Identify specific features that provide customer delight
  • Determine what makes the product 'hard to copy' (e.g., brand, network effects)
  • Ensure the strategy includes 'margin enhancement' (monetization)
View all skills from Gibson Biddle →
Gokul Rajaram 1 quote
Listen to episode →
"As a very young company, you don't have a separate product strategy from a company strategy. The product and company strategy are the same. As you start growing, you have a go-to market strategy, product strategy, et cetera, et cetera."
Tactical:
  • Write a dedicated product strategy doc once the company reaches 20-25 people to articulate implicit choices
  • Ensure the product strategy clearly defines which customer segments are being served
View all skills from Gokul Rajaram →
Hamilton Helmer 2 quotes
Listen to episode →
"Power requires a benefit and a barrier, so he's taking care of the benefit part by saying a castle, you have to have a pretty good understanding of why it's a castle and not a shack."
Tactical:
  • Evaluate your product strategy using the 'Benefit and Barrier' test to ensure long-term value.
"Strategy is a long time concept. You're looking far out in the future... if you focus on value that narrows what you think about and allows you to get rather concise and offer up advice to founders about what they need to pay attention to."
Tactical:
  • Narrow your strategic focus to the factors that drive long-term business value rather than short-term tactical wins.
View all skills from Hamilton Helmer →
Howie Liu 1 quote
Listen to episode →
"the best way to innovate on the product is not incrementally split over all these different little surface areas, but actually to have a bigger, more step function vision of how this product needs to make a leap"
Tactical:
  • CEO should play a CPO role to maintain product vision
  • Focus on 'global maxima' breakthroughs rather than local optimizations within fiefdoms
View all skills from Howie Liu →
Ian McAllister 2 quotes
Listen to episode →
"At our scale we got to hunt for bigger elephants. And so I think at any scale as a PM, whatever your idea is or whatever your solution or the problem you're solving, take a minute at the beginning to say, could this be bigger? Could this be a bigger thing and more impactful than the initial idea, even if the initial idea sounds big?"
Tactical:
  • Ask 'could this be bigger?' at the start of every project
  • Start with a large vision even if you begin execution with a small step
"Most people operate within a box... take that really wide view of what product is across disciplines... take that really wide view of what success for your product is and not have the blinders on its product or tech. It's anything. It's anything that influences the success and your customers' success."
Tactical:
  • Identify and knock down constraints regardless of which department owns them
  • Think like an owner of the entire business, not just the technical feature
View all skills from Ian McAllister →
Ivan Zhao 3 quotes
Listen to episode →
"Our realization is actually let's hide our vision, which is everybody can create their software in the form factor that people do care. So what kind of tool do people use every day? Productivity software. It took us two years to realize we need to build a productivity tool. We called it sugar-coated broccoli. People don't want to eat the broccoli but people like sugar, so it gave them the sugar then hide your broccoli inside of it."
Tactical:
  • Identify the 'sugar' (the immediate utility users want) to deliver the 'broccoli' (your deeper vision/technology).
  • Avoid building purely for your own values if it results in a product that the mass market doesn't care about.
"Building for something you want the world to have is building for your value. You have some taste. You have some aesthetic. There are different energy. You need to create a balance. Too much of yourself. Then there's no users. Then you're just doing our project. And too much for business, you're building a commodity."
Tactical:
  • Audit your product to see if it leans too heavily toward personal aesthetic or pure business optimization.
  • Use personal values as a durable energy source during difficult building periods.
"We ship non-Lego pieces into our product. We're still there. We're still cleaning up part of it. That's a realization. It's like going back to the value part, it's like if you create this thing called a product or business, you attract people are value aligned to it. Then if you're trying to optimize too much on this competition revenue side of things, forced to introducing something anti-your-value, then the system, it's like there's organ rejection with your employees, with your customers."
Tactical:
  • Ensure new features align with the product's fundamental 'abstraction' (e.g., building blocks vs. hard-coded features).
  • Be willing to spend more time building a modular solution rather than a quick, hard-coded fix.
View all skills from Ivan Zhao →
Jackie Bavaro 3 quotes
Listen to episode →
"I basically realized that there's three key components to strategy... Vision: This is your inspiring picture of what the future looks like... Strategic framework: This is where you're saying, 'Here is the market we're going after. Here's what success looks like. And here are our big bets on what we think it takes to win that market.'... And then the third part is the roadmap."
Tactical:
  • Define 'big bets' that explain how you will win your target market
  • Ensure the vision is an 'inspiring picture' that motivates the team
"I think a good strategy is all about connecting the dots. Connecting the dots from this high level business goal of, 'We want to increase revenue by this much' to, 'This is the feature we're going to do.' And it might have many, many dots in between to help get people from one to the other."
Tactical:
  • Map every feature back to a specific business goal (e.g., revenue targets)
  • Identify the 'missing dots' or assumptions in the logic between a goal and a feature
"One of the great ways to learn strategy is to cross apply strategy from other places... consistency versus comprehensiveness. They said 'Is our product the kind of product where it's better to have consistent results all the time... or is it better to have comprehensiveness where even though the experience will be different each time we give you a result every time?'"
Tactical:
  • Look for 'eigenquestions' (like consistency vs. comprehensiveness) used by other successful products
  • Study how leaders in different industries frame their trade-offs
View all skills from Jackie Bavaro →
Jake Knapp + John Zeratsky 1 quote
Listen to episode →
"If we solve this problem for this customer with this approach, we think they're going to choose it over the competitors because of differentiator one and differentiator two."
Tactical:
  • Draft a 'founding hypothesis' sentence that includes: customer, problem, approach, competitors, and differentiators.
View all skills from Jake Knapp + John Zeratsky →
Janna Bastow 1 quote
Listen to episode →
"The product vision template, you might actually recognize it from the Geoffrey Moore's Crossing the Chasm book. It's the elevator pitch template... It asks things like, for your target customer, who the statement of need or the opportunity. The product name is a product category. What's the reason to buy? And then say, unlike this alternative our product, and then say what this statement of differentiation is."
Tactical:
  • Use the Geoffrey Moore elevator pitch template to define product vision: [Target Customer] who [Statement of Need], the [Product Name] is a [Product Category] that [Reason to Buy], unlike [Alternative], our product [Statement of Differentiation]
View all skills from Janna Bastow →
Jason Droege 1 quote
Listen to episode →
"From an entrepreneurship standpoint, it truly is about what insight do I have? Why am I so lucky to have this insight? Why in a world of a million entrepreneurs who are thinking, who are smart, who are trying everything, why am I in the position where I likely have an insight that others do not?"
Tactical:
  • Question why you specifically are positioned to have a unique market insight
  • Avoid 'consensus' thinking to find alpha in the market
View all skills from Jason Droege →
Jiaona Zhang 1 quote
Listen to episode →
"understand why people love you, double down on that and then whatever else you build around it... go back to, again, what's the core of our advantage and how can that be something we leverage in delivering a really great product experience for our users in X adjacent area or x add-on?"
Tactical:
  • Identify the 'alpha' or core strength of the product (e.g., Dropbox's simplicity or Airbnb's unique homes)
  • Avoid chasing competitors into areas that don't leverage your core advantage
  • Ensure multi-product expansions still tie back to the original value proposition
View all skills from Jiaona Zhang →
John Cutler 1 quote
Listen to episode →
"The Jeff Bezos thing, that the success of today was set in motion three years ago, that product is a layer cake and that you are layering on decisions, the success you're having now is a layer cake of decisions from the last bunch of years that you're doing it."
View all skills from John Cutler →
John Mark Nickels 2 quotes
Listen to episode →
"I try to just close my eyes and imagine the future as far out as I can. It's like five years from now, 10 years from now, whatever. And it's develop a really salient picture of what that looks like. It's like, we could do this right now, it's okay. 10 years from now, what could San Francisco look like? Or some city? What happens to the parking spaces? Are there still parking garages? Are those parks now?"
Tactical:
  • Carve out distraction-free time to visualize the industry 5-10 years out
  • Identify specific physical or societal changes that will likely occur (e.g., repurposed parking spaces)
"One example might be, why do we need a 4,000 pound vehicle to move a human three miles? Okay, well... Or even a couple of humans. We do an Uber Pool or a Share, and you move two humans or three humans, even then that's pretty inefficient. If you think about just the physics there, the energy expenditure."
Tactical:
  • Question the basic physics or economics of current solutions
  • Look for massive inefficiencies (like vehicle weight vs. passenger weight) to find product opportunities
View all skills from John Mark Nickels →
Jules Walter 1 quote
Listen to episode →
"What I do specifically is I try to identify what's the best practice for something. For example, let's say strategy... Can you help me understand what are people at this company... where you think have done a great job at strategy or what are examples of artifacts? Then I get these artifacts and I reverse engineering them."
Tactical:
  • Request examples of high-quality strategy artifacts from respected peers or leaders.
  • Analyze successful documents to identify the core questions, data points, and frameworks used.
  • Observe the iteration process of a strategy document rather than just the final version to understand the trade-offs made.
View all skills from Jules Walter →
Julie Zhuo 1 quote
Listen to episode →
"Purpose is like, 'What are we here to do? What's our North Star?' And I think it's very hard to actually convey that if you don't have conviction yourself... you have to really check in with yourself on like, 'Wait, I know we're told to do this and this is what we have to do, but how do we really feel about it?'"
Tactical:
  • Check your own belief in the strategy before attempting to lead others.
  • Engage in dialogue with leadership to find alignment if you lack conviction.
View all skills from Julie Zhuo →
Katie Dill 1 quote
Listen to episode →
"Reach for the stars and land on the moon. And what I mean by that is that vision work is really important... vision work that absolutely does look at the entirety of the experience, a comprehensive approach, a journey approach, and thinks about how these various things may come together to be better, and sketch out the ideal version... show what that ideal version is, because if you don't know what that is, what are the chances that you're going to increment yourself to the right outcome in the end?"
Tactical:
  • Sketch out the 'ideal version' of the product 2 years out
  • Work backwards from the ideal vision to determine what to ship first
View all skills from Katie Dill →
Kayvon Beykpour 1 quote
Listen to episode →
"It was also just storytelling and just repetitive storytelling around this is the vision, these are the bets we're making. Here's why. And you can't just tell that story once."
Tactical:
  • Communicate the product vision and the 'why' behind bets repeatedly to both internal and external stakeholders.
View all skills from Kayvon Beykpour →
Ken Norton 1 quote
Listen to episode →
"What would it be like, in my case, to lead with purpose and be decisive and lead with vision and to have other people felt like they're being brought along and listened to and participated and create safe spaces for other people?"
Tactical:
  • Shift from a reactive mindset (solving problems) to a creative mindset (leading with vision)
  • Ensure the vision-setting process makes the team feel heard and safe
View all skills from Ken Norton →
Keith Coleman & Jay Baxter 1 quote
"Probably the craziest one is just that this thing is going to be the voice of the people. It's going to represent the voice of people. It's not going to represent the company's voice. So it is not a tech company deciding what shows."
Tactical:
  • Establish core principles (like decentralization or transparency) that the company cannot override
  • Design systems where the company has no 'button' to manually change outcomes, forcing reliance on the algorithm
View all skills from Keith Coleman & Jay Baxter →
Karri Saarinen 1 quote
Listen to episode →
"I personally have this belief that productivity software should be, and especially company software should be opinionated... Being opinionated, I think the value it provides people is you don't have to think too much or spend more time on the tool than you do on your actual work."
Tactical:
  • Design for a specific target user rather than trying to build a generalized solution for everyone.
  • Provide strong default workflows so users can focus on their work instead of the tool.
View all skills from Karri Saarinen →
Kevin Aluwi 1 quote
Listen to episode →
"Don't just copy, because Gojek was not an Uber clone, even though that was kind of how some investors or analysts talk about us, we were focused on a solution that was uniquely an Indonesian phenomenon, the motorcycle taxi driver. And this led to both product and branding innovation."
Tactical:
  • Identify unique local phenomena or problems to solve rather than defaulting to global clones
  • Adapt product strategy to the specific behaviors of the local population
View all skills from Kevin Aluwi →
Kunal Shah 1 quote
Listen to episode →
"Every time you see that the product efficiency delta is greater than or equal to four, three things happen. It is irreversible. Second is that you have a very high tolerance for it to fail. If Uber fails a little bit, will you say, “Oh my God, I'm going to really stop using it?” No. And the third thing is what I call the UBP, ‘Unique Brag-worthy Proposition.’ Every time humans unlock a Delta 4 product or service, they cannot stop talking or sharing about it."
Tactical:
  • Score the current solution's efficiency from 1 to 10.
  • Score your proposed product's efficiency from 1 to 10.
  • Ensure the delta is at least 4 to guarantee high user tolerance and low CAC.
  • Identify the 'Unique Brag-worthy Proposition' (UBP) that triggers word-of-mouth.
View all skills from Kunal Shah →
Lane Shackleton 1 quote
Listen to episode →
"The core insight here is that you want your teams to feel like they're building a cathedral and not laying bricks. And I think it's really, really easy to do when PMs are really busy on a day-to-day to just be one task after the other, really execution oriented and maybe not take the time to help the team take a broader frame, open the aperture a little bit and have a view of what the cathedral is."
Tactical:
  • Show different facets of the vision: write-ups, metrics, directional mocks, and 'billboard' examples.
  • Take the mystery out of constraints by visualizing the long-term destination.
View all skills from Lane Shackleton →
Marc Benioff 1 quote
Listen to episode →
"I want to get to the future first and welcome our customers there."
Tactical:
  • Look for emerging technologies (like agents or robotics) years before they become mainstream
  • Build the 'future' state and then guide customers toward it
View all skills from Marc Benioff →
Marily Nika 1 quote
Listen to episode →
"Even when I'm at work and I am trying to come up with a nice mission statement, when we're PMs will come up with mission statements, it's just crucial part and it's where the core begins. You want to get people excited, you want to get people inspired. There is nothing I can write that's going to be as good as what ChatGPT looks like."
Tactical:
  • Draft a mission statement and ask ChatGPT to rewrite it for clarity and inspiration.
  • Ensure mission statements are simple enough for a non-expert or even a child to understand.
View all skills from Marily Nika →
Manik Gupta 1 quote
Listen to episode →
"Generally you would say the CPO is responsible for driving the product vision for the company, and that product vision cannot be divorced from the company vision. Oftentimes this is actually what also creates conflict within the leadership team, where the product vision is... people are coming up with these grandiose plans... but then it's not really grounded in the reality of where the company is. Anyways, it's around product vision and making sure it's coherent with the company vision."
Tactical:
  • Ensure the product vision is coherent with the company's strategic goals to avoid leadership conflict.
  • Avoid 'grandiose' plans that aren't grounded in the company's actual capabilities or market position.
View all skills from Manik Gupta →
Maggie Crowley 1 quote
Listen to episode →
"You should be able to walk all the way from your company's mission down to the individual priority on your team and see the logic chain and why you got there."
Tactical:
  • Start with the company mission and current business goals
  • Document the landscape: market point of view, competitors, and SWOT analysis
  • Identify the specific opportunity and what must be true for it to work
  • Sequence the plan based on what you would do if no one else had an opinion
View all skills from Maggie Crowley →
Marty Cagan 1 quote
Listen to episode →
"Product teams don't do product strategy. Product leaders do product strategy. They need to do the product strategy... that is the job, is to make these strategic decisions, the focus decisions, the bets you're going to place."
Tactical:
  • Leaders should define the strategic bets and focus areas.
  • Teams should be given the latitude to figure out the best way to solve the problems within those strategic bets.
View all skills from Marty Cagan →
Matt Mullenweg 1 quote
Listen to episode →
"And I think your audience in particular, is great software ever created by committee or does it more often reflects a vision of a leader or something that can allow us to... and I think particularly WordPress not just remaining relevant but actually accelerating growth over huge technological shifts over the past two decades."
Tactical:
  • Avoid 'design by committee' for core product direction
  • Empower a visionary leader to make unpopular decisions that ensure long-term survival
View all skills from Matt Mullenweg →
Melissa Perri + Denise Tilles 1 quote
Listen to episode →
"As a chief product officer, ARR is interesting to me, but it's not as interesting to me as ARR by customer segment. It's not as interesting as ARR by product line. It's not as interesting if I take that and then look at it by retention or adoption by product or feature set... When we start to put those lenses on it, they now become a really powerful strategy insight."
Tactical:
  • Analyze ARR and retention by specific customer segments rather than just at the aggregate level
  • Monitor feature adoption by segment to validate if strategic shifts (e.g., moving upmarket) are working
View all skills from Melissa Perri + Denise Tilles →
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:
  • Focus on the speed of the hypothesis-to-data loop rather than long-term strategic documents.
  • Use data to override the 'loudest voice in the room' or executive intuition.
View all skills from Mayur Kamat →
Melanie Perkins 3 quotes
Listen to episode →
"I really like to start by just imagining what is the future that you actually want Right now? I have a wall in my house in my office, which is my vision for what I'd like the world to look like in 2050."
Tactical:
  • Create a physical or digital 'vision wall' for a long-term horizon (e.g., 2050)
  • Define 'wild success' and 'terrible failure' for a 10-year period to clarify the desired direction
"So we have this concept of chaos to clarity. Every idea starts in the chaos side, and then you have to work all the way to the other side, which is clarity. That very first step at the far end of chaos was quite an embarrassing step actually, because you don't have mastery at that point."
Tactical:
  • Start by simply writing an idea down to move it out of your head
  • Use pitch decks to refine and communicate thinking before building
  • Accept that the first step of a vision will feel 'embarrassing' due to a lack of mastery
"So our mission, empower world design, empower everyone to design anything with every ingredient in every language on every device, and just take those things very literally."
Tactical:
  • Define mission pillars (e.g., 'every language', 'every device') and systematically check them off over years
View all skills from Melanie Perkins →
Melissa Perri 4 quotes
Listen to episode →
"I once asked all the executive team at a healthcare company, what's the vision for this company? And they said, to be the backbone of healthcare. And I said, what does that mean? And they couldn't elaborate. Nobody could elaborate on that. And I said, cool, that's a tagline, but it's not a vision."
Tactical:
  • Ask leaders to elaborate on vague vision statements to see if they have a shared understanding of the future state.
  • Define who the future customers will be and how the value provided will differ from today.
"A vision should be concrete enough where people can picture what it will be in their head. It can't be a fluffy... be the backbone of healthcare. What does that mean? I don't get it. So people need to be able to look at a vision and say, I can understand that we're going to get there one day."
Tactical:
  • Ensure the vision is far enough away that it cannot be achieved by building just one thing.
  • Avoid making the vision a description of the current state of the product.
"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. We're not going to go after that."
Tactical:
  • Explicitly list competitors or market behaviors the company intends to avoid copying.
"SAFe is not good at describing how you do discovery work."
Tactical:
  • Build vision before sprints
  • Feed discovery continuously
View all skills from Melissa Perri →
Michael Truell 2 quotes
Listen to episode →
"Our goal with Cursor is to invent sort of a new type of programming, a very different way to build software, that's kind of just distilled down into you describing the intent to the computer for what you want in the most concise way possible, and really distilled down to just defining how you think the software should work, and how you think it should look."
Tactical:
  • Focus on the 'what' (logic and intent) rather than the 'how' (under-the-hood implementation).
  • Aim for a representation of logic that is human-readable and human-editable, moving toward pseudocode.
"I think that more and more, being an engineer will start to feel like being a logic designer, and really, it will be about specifying your intent for how exactly you want everything to work. It'd be more about the whats, and a little bit less about how exactly you're going to do things under the hood."
Tactical:
  • Develop 'taste' for how software should work and look as a primary competitive advantage.
View all skills from Michael Truell →
Mihika Kapoor 2 quotes
Listen to episode →
"My take is that vision is everything. It is really important to create a vision that you believe in, that your team believes in and that your company believes in. Because the reality of the product development cycle is that it's so messy, it's so chaotic... it's so important to be anchored on that singular vision because then any step along the way feels like forward progress."
Tactical:
  • Ensure vision is inseparable from user research and team input rather than created in a vacuum
  • Root the vision in engineering feasibility from the beginning
  • Use a 'pain point, solution, proof point' structure for vision pitches
"I think that when you're actually presenting a vision, one of the most important things is that there is a single artifact that the team is creating together... you want for everyone to feel incredible ownership and incredible passion about this combined deliverable, so that it's a unified team who believes a singular set of insights."
Tactical:
  • Avoid siloed deliverables like separate research readouts and design crits
  • Lean into high-fidelity prototypes and mocks to make the vision 'felt' emotionally
View all skills from Mihika Kapoor →
Mike Maples Jr 2 quotes
Listen to episode →
"Great founders, pattern breakers back cast, they say, it's a given that the future has to be radically different for me to be a big winner, and so, I'm going to look for radically different futures and work backwards from those radically different futures."
Tactical:
  • Identify a future that is radically different from today
  • Work backwards from that future to determine what needs to be built now
  • Avoid the 'comparison trap' by proposing a future that denies the premise of current rules
"The way startups win is because it proposes a radically different future. Disorients the incumbent and chaotically moves people to that different future."
Tactical:
  • Focus on being radically different rather than just 'better'
  • Look for ways to change the subject of the market entirely
View all skills from Mike Maples Jr →
Nancy Duarte 1 quote
Listen to episode →
"Movements have a five act structure... dream, leap, fight, climb, arrive. So, the torch bearer, the reason we called that is the leaders know where they're headed, but they might not ever see it super, super clearly."
Tactical:
  • Communicate the 'Dream' to get initial buy-in
  • Use stories and ceremonies to provide 'emotional fuel' during the 'Fight' and 'Climb' phases
  • Acknowledge that you don't need to see the whole future, just enough to lead the next step
View all skills from Nancy Duarte →
Naomi Ionita 1 quote
Listen to episode →
"I always used to say you can't retrofit collaboration. You have to be collaboration-first. And a lot of companies now really take that for granted. But back in mid-2000s, this was kind of a new way of building product. And so we missed that bridge."
Tactical:
  • Design for multiplayer/team workflows from the start to avoid the 'single-player' growth cap
View all skills from Naomi Ionita →
Nick Turley 2 quotes
Listen to episode →
"What we envision is this entity that can help you with any task, whether or not that's at home, or at work, or at school, really any context, and it's an entity that knows what you're trying to achieve. So, unlike ChatGPT today, you don't have to describe your problem in menu to detail because it already stands your overarching goals and has context on your life"
Tactical:
  • Build toward a 'relationship' model where the AI remembers user goals over time
  • Expand the 'action space' of the AI so it can execute tasks, not just provide information
"ChatGPT feels a little bit like MS-DOS. We haven't built Windows yet, and it will be obvious once we do. ... I think natural language is here to stay, but this idea that it has to be a turn-by-turn chat interaction I think is really limiting."
Tactical:
  • Look beyond the chat box for ways to communicate affordances to users
  • Explore AI that can render its own UI dynamically based on the task
View all skills from Nick Turley →
Nilan Peiris 1 quote
Listen to episode →
"But to get to recommendation, you're going to blow your user socks off. You have to give them an experience they didn't know was previously possible. And when you are in that place of doing something that no one has ever done before, that's when you get it. So the bar is all the way up there. And to put that in context, that means figuring out how to move money instantly. That means figuring out how to drop the price all the way from six all the way down to 0.35."
Tactical:
  • Set the product bar at 'blowing the user's socks off' rather than just functional utility
  • Identify the 'theoretical minimum' cost or 'theoretical maximum' speed and aim for that as the long-term goal
  • Avoid shortcuts that rely on existing infrastructure if they prevent you from fundamentally changing the user experience
View all skills from Nilan Peiris →
Oji Udezue 1 quote
Listen to episode →
"Forest time is the idea that you make time within your week, within your month to see the forest for the trees... to elevate, to get some bird's eye view, to see the entire landscape and see the alternative paths through the current problems that you're escaping."
Tactical:
  • Schedule one full day per month specifically for strategic reflection away from daily operations.
  • Use a structured worksheet to survey the 'forest' and identify alternative paths that aren't visible during daily execution.
View all skills from Oji Udezue →
Noam Lovinsky 1 quote
Listen to episode →
"At Thumbtack, we had principles about which sides of the marketplace we wanted to serve in which order and when we serve Thumbtack. So it was customers first, pros second, and then Thumbtack last. ... Saying Thumbtack last is the easy thing to say. Actually doing it in action I think is a very different thing."
Tactical:
  • Create a stack-ranked list of stakeholders to guide trade-off decisions
  • Ensure 'business needs' are prioritized after customer and provider value to ensure long-term health
View all skills from Noam Lovinsky →
Richard Rumelt 3 quotes
Listen to episode →
"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 strategy as a mixture of policy and action to address a specific challenge.
"The kernel... if anyone in three is missing, something's wrong. It's not really a strategy, it's something else. There has to be an understanding of the situation. There has to be a guiding policy, how are we going to deal with it? And then the coherence and action is critical."
Tactical:
  • Ensure your strategy document includes a clear diagnosis of the situation.
  • Develop a guiding policy that outlines the approach to the diagnosis.
  • List coherent actions that implement the policy without contradicting each other.
"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... 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:
  • Rename your strategy to an 'action agenda' to focus on execution.
  • Identify one or two key challenges that are actually addressable today.
View all skills from Richard Rumelt →
Ramesh Johari 2 quotes
Listen to episode →
"Uber and Airbnb are selling you the taking away of something, which is a weird thing to think about. What they're taking away is the friction of finding a place to stay. They're taking away the friction of finding a driver. In economics, we call those things transaction costs."
Tactical:
  • Identify the specific market failure or friction (e.g., trust, discovery, payment) that your platform is uniquely positioned to solve.
"Maybe we shouldn't talk about the concept of a marketplace founder. Really there's founders. And I think every entrepreneur... it means literally any founder is a marketplace founder. It'll be a choice they make after they grow as to whether they want to build a platform."
Tactical:
  • Focus on solving a core problem for one side of the market before worrying about building a scaled marketplace infrastructure.
View all skills from Ramesh Johari →
Ravi Mehta 2 quotes
Listen to episode →
"The product strategy stack is a system that helps people understand what framework they're using in order to make decisions and what's going to drive value for the business. The top of the stack is the company mission... The second thing is strategy... The next level of the strategy stack is the product strategy. And the product strategy is the connective tissue between what is the company trying to accomplish and what are the day-to-day things that the product team is doing."
Tactical:
  • Define the mission as the qualitative, aspirational change you want to bring to the world.
  • Ensure the strategy is 'rigorously logical' rather than just aspirational.
  • Use the stack to debug issues: if goals aren't being met, check if the roadmap or strategy is misaligned.
"One of the things that we said with stake that we put in the ground was the strategy doc wouldn't be complete without wireframes... the reason is that oftentimes when you talk about strategy in words alone, everyone takes away a different interpretation of that strategy, whereas when you actually can show people wireframes of what the product will look like when that strategy is implemented, it creates much more alignment."
Tactical:
  • Include conceptual wireframes in strategy documents to force concrete decisions about trade-offs.
  • Use the 'nav bar test': if your strategy doesn't dictate what the 4-5 items on a mobile nav bar are, it isn't specific enough.
View all skills from Ravi Mehta →
Roger Martin 2 quotes
Listen to episode →
"Strategy is an integrated set of choices that compels desired customer action."
Tactical:
  • Focus on the things you control to influence the one thing you don't: customer action.
  • Ensure all strategic choices reinforce one another rather than acting in isolation.
"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' to contextualize your choices.
  • Identify the specific 'where to play' (playing field) and 'how to win' (value proposition).
  • Determine the 'must-have capabilities' and 'management systems' needed to sustain the advantage.
View all skills from Roger Martin →
Ryan Hoover 1 quote
Listen to episode →
"One- one regret is we should not have tried to expand horizontally. We should've just focused entirely vertically and- and served the tech community, you know, better and- and with more things, which is effectively what we're doing now."
Tactical:
  • Be cautious of expanding into new categories before fully serving the core community's needs.
  • Recognize that different product categories (e.g., games vs. podcasts) require fundamentally different discovery experiences.
View all skills from Ryan Hoover →
Seth Godin 2 quotes
Listen to episode →
"Choose your customers, choose your future. Choose your competition and choose your future. Choose the source of validation and you choose your future. Choose your distribution, and you're also choosing your future."
Tactical:
  • Explicitly select a 'smallest viable audience' rather than trying to appeal to everyone.
  • Align the product's distribution strategy with the specific needs and behaviors of the chosen customer base.
"Tension is at the heart of every art form and every innovation. What we do when we launch a new product, we say, we have this thing that can do X, and now the person is imagining what their life might be like if that were true. If they fall in love with that possibility, now there's tension."
Tactical:
  • Articulate a 'remarkable promise' that creates emotional tension for the potential user.
  • Ensure the product actually delivers on the promise to resolve that tension positively.
View all skills from Seth Godin →
Shreyas Doshi 3 quotes
Listen to episode →
"Google taught me the... power of thinking really big. And I know it sounds like a platitude, but really big. And I only actually realized that when I left Google and I started working with the other teams and these were all capable teams and I was struck by how many teams just limited the potential of what they could achieve."
Tactical:
  • Ask 'What does it take to make it bigger?' for every $1M or $10M opportunity.
  • Be willing to let go of smaller opportunities to focus on billion-dollar potential.
"Most execution problems that I encounter in a high performing environment where everybody has the right intentions are actually not execution problems, they are either strategy problems or interpersonal problems or cultural problems."
Tactical:
  • If a 'band-aid' solution like a new review process fails, investigate if the teams are pursuing different or undefined strategies.
"Twitter's biggest problem is a product strategy problem. The reason they're struggling is they don't have a real product strategy. Now, of course, attempts were made to create a product strategy, but it wasn't a real compelling, cohesive product strategy."
Tactical:
  • Distinguish between 'fake' strategy and a 'real compelling, cohesive' strategy.
  • Recognize that execution alone cannot fix a fundamental lack of strategic direction.
View all skills from Shreyas Doshi →
Stewart Butterfield 1 quote
Listen to episode →
"If you can't see almost limitless opportunities to improve, then you shouldn't be designing the product. ... I feel like what we have right now is just a giant piece of shit. It's just terrible and we should be humiliated that we offer this to the public."
Tactical:
  • Maintain a high bar for quality that views current versions as 'humiliating' compared to the potential
  • Cultivate a perpetual desire for improvement across the design team
View all skills from Stewart Butterfield →
Shweta Shriva 1 quote
Listen to episode →
"In terms of the product, whether you're working for a big company or a startup, the core product management tenant is still the same, which is, you have to work backwards from the customer problem or the user problem. Building a technology for the sake of it doesn't really go that far, so you really have to focus on the, what are you building, who are you building it for and what problem are you solving?"
Tactical:
  • Focus on the 'who' and the 'what problem' before the 'how' of the technology.
View all skills from Shweta Shriva →
Tomer Cohen 1 quote
Listen to episode →
"To really set the new purpose for it, which was this is not a springboard for other products, this is not a traffic jumpstart for, it's not an app self feed, it's really about people that matter talking about things that I care about professionally. It's about knowledge exchange."
Tactical:
  • Shift product DNA from 'activity tracking' to 'value exchange' or 'knowledge sharing'.
  • Define the vision by asking: 'If you're successful, what change would happen in the world?'
View all skills from Tomer Cohen →
Vikrama Dhiman 1 quote
Listen to episode →
"Product strategy for me is where you are able to define that while somebody defines that this is the mountain that you're going to climb, but okay, how are you going to climb that mountain is basically the product strategy piece."
Tactical:
  • Focus on defining the 'how' of climbing the mountain once the 'what' (goal) is set
  • Identify specific user segments and their needs to inform the strategy
  • Determine the specific order of operations for product development
View all skills from Vikrama Dhiman →
Vijay 2 quotes
Listen to episode →
"If you are the leader in some core product, our takeaway here is you should continue to out invests everyone else in that core and then invest the profits that come out of that core into the next venture. Invest profits and not people"
Tactical:
  • Avoid moving core team members to experimental secondary products
  • Fund new ventures with profits or venture capital, not by thinning out the core engineering team
"This design driven initiative was really about how can we think about the system architecture of our product? What are the key building blocks of Mixpanel? Where do they need to fit? How few of them can we have, which is a really important step?"
Tactical:
  • Identify the core building blocks of the product (e.g., pages and blocks in Notion)
  • Optimize for the fewest number of building blocks possible to increase feature reach and consistency
View all skills from Vijay →
Ebi Atawodi 4 quotes
Listen to episode →
"four things. So it has to be lofty, it has to be realistic, it has to be devoid of any tech or limitations of today, and it has to be grounded in a very clear and potent problem. User problem."
Tactical:
  • Ensure the vision is lofty enough to be exciting but realistic enough to feel reachable
  • Remove technical limitations of today when imagining the future state
  • Ground the vision in a potent user problem
"Once upon a time, write the problem and then write something and then write something, and then one day something happened. And as a result, the state of the world where we're trying to be. It's very simplistic, but in its simplicity of the magic because you are like, 'I'm a PM, I'm trying to solve problems.'"
Tactical:
  • Use the 'Once upon a time' framework: Once upon a time [problem], then one day [event/launch], and because of that [change], and finally [new state of the world]
"I write an article. I'll write in the headline because if the vision has come to pass, right? And it's gone well, someone's going to be writing hopefully some sexy headline about the thing that you've built. So I go to the future and I write the headline I would see. And I write the subtitle, just that, and I'll actually use the... I'll [inaudible 00:18:01] it into the page of TechCrunch or [inaudible 00:18:04] or something just so it looks realistic."
Tactical:
  • Write a future TechCrunch or New York Times headline and subtitle for your product
  • Mock the headline into a realistic-looking news page to provoke a response and build conviction
"I actually took a screenshot of the Google Play Store... and then I created rounded rectangles, just blank rectangles, four panels. And then I printed that out and I gave everyone a sheet and I said, 'If we solve these problems... what would be the screenshots?'"
Tactical:
  • Print out blank App Store screenshot templates and have the team draw the 'hero mocks' and captions for the future product
View all skills from Ebi Atawodi →
Josh Miller 1 quote
Listen to episode →
"we want to be to the web browser, what the iPhone was to the cell phone. Yes. The iPhone replaced your cell phone, but it really was something much more. And so, we want Arc to be the iPhone for the internet, and that yes, it replaces your default browser... it really is that interface, this new type of computer."
Tactical:
  • Use a well-known historical analogy (like the iPhone) to explain a complex future vision
  • Frame the product as an interface to a macro trend (like the shift to cloud computing)
View all skills from Josh Miller →
Nickey Skarstad 2 quotes
Listen to episode →
"I really like the vision mission strategy pyramid... At the top is vision. Below it is mission and strategy, and then objectives. And this is a very simple framework... where do you need to go long term? In 10 years, if you could zoom up and look at what an ideal path for you would be, what is that? Write it down."
Tactical:
  • Define a 10-year vision as the top level of abstraction
  • Ensure each level of the pyramid (Mission, Strategy, Objectives) ladders up to the Vision
"I would pre-fill out the Miro beforehand... create them as headers in the Miro document... give everyone the space and the freedom to think existential and to frame it that way, 'we are going to be thinking in a five to 10 year timeline. Do not worry about what's happening today.'"
Tactical:
  • Pre-fill whiteboarding tools (Miro/FigJam) with headers and prompts before the meeting
  • Use timers and music to facilitate focused, creative brainstorming
  • Synthesize ideas into buckets after the meeting rather than forcing a final vision in the room
View all skills from Nickey Skarstad →
Peter Deng 1 quote
Listen to episode →
"You have to plan your chess moves out in advance. You have to really think before you act and build systems that were going to let you go sustainably faster."
Tactical:
  • Build scalable architectural systems (like Uber's 'Venues') to enable future speed
  • Avoid 'spaghetti' solutions during hyperscale by pausing to re-architect core components
View all skills from Peter Deng →
Sanchan Saxena 2 quotes
Listen to episode →
"The thing that I learned from him was intentionality... You got to have intentionality. Where do you want to go? What is the world you want to create for your customers? And then create out A/B testing to get you the fastest route to that end state world."
Tactical:
  • Define the 'intentionality' of the product before setting up tests
  • Use A/B testing as a GPS to find the fastest route to a pre-defined destination, not to choose the destination
"What Brian taught us was think unconstrained first. Think about a 15 out of 10 experience, design the ideal end state first. In most companies, the designers and PM start by saying, 'Okay, 10 is perfect. We can probably do seven. Let's start at seven.' It's a very constrained minded thinking."
Tactical:
  • Design the perfect, unconstrained experience first, then work backwards to what is feasible
  • Do things that don't scale in one location to prove the 'lovable' product before scaling
View all skills from Sanchan Saxena →
Tamar Yehoshua 1 quote
Listen to episode →
"In 2014, he wrote a master plan for Slack, which was build a product people love, build a network. That's Slack Connect. Build a platform that makes all of your other SaaS products more valuable. That's Slack Platform. And then do some magic AI stuff... It literally was. There was a grid with four boxes in 2014 and it never changed."
View all skills from Tamar Yehoshua →
Tobi Lutke 2 quotes
Listen to episode →
"I talk about look in the future and then think backwards a lot, right? It's like what would we want to have done 20 years ago on this? We have very long-term plans. At 100 years you can't talk about this software project but you can talk about the mission itself, whatever things that will survive for 80 years that are left on this particular timeframe."
Tactical:
  • Look decades into the future and work backwards to current decisions
  • Focus the long-term vision on the mission (e.g., entrepreneurship) rather than the tool
  • Ask: 'What is the decision our future selves would want us to make?'
"The positional game is like, what is the territory on the map that you are taking? What role do you play? How much trust do you have of merchants? Do merchants want more from you or less? Are you the kind of thing they're trying to optimize out of their software spend, or the one that they ask to subsume all other software spend? ... If you do that well, the tactics are yours."
Tactical:
  • Prioritize the 'positional game' (trust, role, territory) over short-term 'tactics' (hacks, A/B tests)
  • Avoid 'tacticking' yourself out of a position by over-extracting value from customers
  • Focus on being the partner customers want to rely on more deeply over time
View all skills from Tobi Lutke →
Jag Duggal 1 quote
Listen to episode →
"We're not trying to be incrementally better, we are trying to be fundamentally different."
Tactical:
  • Define vision around being different
  • Use Amazon mock press release
View all skills from Jag Duggal →

Install This Skill

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

1

Download the skill

Download SKILL.md
2

Add to your project

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

.claude/skills/defining-product-vision/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 vision