Product Taste

Product Taste and Intuition

Develop a reliable internal compass to recognize and build world-class products.

Help the user with product taste and intuition using insights from 35 guests and posts across Lenny's Podcast and Newsletter.

How to Help

1. Deconstruct experiences - Guide the user through analyzing specific product details to identify why they evoke certain emotional responses.
2. Calibrate intuition - Help the user document and review their decision rationales against real-world outcomes to refine their judgment.
3. Challenge assumptions - Use first-principles thinking to question standard industry metrics and focus on core user utility.
4. Refine the feel - Assist in articulating the specific polish, speed, and usability elements that contribute to a high-quality product feel.

Core Principles

Learn Through Model Primitives

Howie Liu: "I think to really understand the solution space of what's possible, you have to be in the details. I mean, literally, you can't just look at screenshots or a pre-recorded video of a new product feature. AI is something you have to play with, and ideally you're playing with both the packaged up app or solution that you've built with it, but you're also playing around directly with the underlying primitives who are using the models either via API or via a chat interface."

True intuition is built by playing directly with the underlying technology and APIs rather than observing demos. Understanding the raw boundaries of your ingredients allows you to imagine new possibilities.

Articulate Emotional Responses

Jessica Hische: "Most people are better at understanding the feelings and sensations that typography and logos give us than they give themselves credit for, because what we are as people are endless absorbers of patterns, and information, and all this kind of stuff as we move throughout the world. We don't take time to sit and digest it, but it's still coming in and getting logged, and so even as a non-designer, I think you can look at examples of logos where something's not quite right and be like, 'Something's not right here, I just don't know how to name it.'"

Develop a professional eye by explicitly naming the feelings triggered by specific design elements. Practice identifying broken patterns to understand what makes a visual work.

Design for Human Emotion

Josh Miller: "What we do at The Browser Company is we talk about optimizing feelings. How do we want to make someone feel on the other end of our software? Do we want to make them feel joy? Do we want to make them feel fast?"

Focus development on evoking specific human feelings like joy or speed rather than just moving quantitative metrics. Treat metrics as secondary tools to measure the success of an emotional experience.

Actively Falsify Assumptions

Judd Antin: "One of my big mantras was, "We don't validate, we falsify. We are looking to be wrong." Many PMs, many designers are not in that place. They do not want to be wrong. They're looking to validate, and that's user-centered performance."

Use research to stress-test your internal beliefs and look for ways you might be wrong. Avoid research that merely validates existing decisions without the potential to change them.

Quality as a Growth Strategy

Katie Dill: "I know there's this saying of it's growth versus quality, but quality is growth. And if you think about how you can make your product easier to use and more understandable, that will of course drive people to use it, and use more of it, and have a better experience with it that they'll want to talk about with others."

Superior aesthetics and usability are not just for show; they drive user activation and word-of-mouth. High-quality details make a product feel more approachable and trustworthy.

Iterate via Internal Usage

Karri Saarinen: "We actually believe that when you start building the thing you actually start realizing more how it should work and how it should be better. A lot of times with the teams we tell them, "Just put it there in, I don't know, the first week almost. After you have some designs in place or some design ideas, just put it into the app and ship it to production." It's only visible to us so we internally can test it out."

Ship early to internal teams and co-create with select customers to find real usage patterns. High quality is reached through constant iteration before final polishing.

Templates & Frameworks

• Three Dimensions of Product Feel (What working at Figma taught me about customer obsession) - The three specific dimensions Figma focused on to get the 'feel' of their product right, applicable to any high-frequency software product
• Signs Your Product Sense Is Improving (How to develop product sense) - Six indicators that your product sense is developing over time, useful as a self-assessment rubric.
• Competitive Product Comparison Template (How to develop product sense) - A structured comparison framework for analyzing two competing products across multiple dimensions to uncover strategic differences and design choices.
• Shopify's Product Quality Benchmarking Questions (How Shopify builds product) - Questions to ask when evaluating whether your product meets a high quality bar
• Mona Lisa Principle (How Miro builds product) - A quality standard principle stating that everything shipped should be something the team would be proud to put their name on, like the Mona Lisa painting
• Adapt When Adopting Framework (How Duolingo reignited user growth) - A three-question framework for evaluating whether to borrow a feature from another product and how to adapt it to your own context
• Three Key Features Framework (Great ≠ Good) (Essential reading for product builders—part 1) - Paul Buchheit's product design principle: pick three key attributes or features for a new product, get those very right, and forget everything else. If a produc
• Onion-Peeling Product Philosophy (How Notion builds product) - A metaphor for building products that serve both casual users and power users by letting them go as deep into customization as they want

See references/artifacts.md for the full list with details.

Questions to Help Users

• "What is the specific emotion you want this feature to evoke in the user?"
• "If you couldn't use any data or metrics, what would your gut tell you to change right now?"
• "How does the feel of this product compare to the most delightful tools you use daily?"
• "What are the core technical primitives of this feature, and have you interacted with them directly?"
• "Can you identify any broken or friction-filled patterns in the current user flow?"
• "Is this feature solving a root problem or just responding to a surface-level request?"

Common Mistakes to Flag

• Metric-Obsessed Tunnel Vision - Relying solely on quantitative data can lead to a soulless product that lacks a cohesive, opinionated vision.
• Blind Deconstruction - Copying successful features from competitors without understanding their strategic context often results in poor fit for your own users.
• Seeking Only Validation - Using research only to confirm what you already believe prevents you from finding the fatal flaws in your strategy.
• The Quality-Skill Gap Stall - Waiting for your skills to match your high standards instead of producing a high volume of work to close that gap through practice.
• Over-Optimizing Hidden Metrics - Focusing on backend metrics that users can't see while neglecting the visible innovation that signals brand growth.

Deep Dive

For all 36 sourced insights from 35 guests, see references/guest-insights.md

Related Skills

• Customer Interviews
• Continuous Discovery
• Idea Validation
• Product Experiments