| name | continuous-discovery |
| description | Help users build a sustainable habit of regular customer interaction to ensure product development is driven by real-world needs rather than internal assumptions. |
Continuous Product Discovery
Turn customer feedback from a periodic chore into a high-frequency engine for product decisions.
Help the user with continuous product discovery using insights from 23 guests and posts across Lenny's Podcast and Newsletter.
How to Help
- Audit current proximity - Evaluate the frequency and quality of direct team-to-user interactions and identify existing gatekeepers.
- Define discovery rituals - Help set up recurring cadences for interviews, demo days, and support shifts that involve the entire product trio.
- Structure the opportunity space - Guide the translation of raw feedback into a visual map of unmet needs, pain points, and desires.
- Accelerate evidence gathering - Recommend lightweight methods for testing assumptions through prototypes and behavior mapping before committing to full builds.
Core Principles
Distinguish needs from solutions
Teresa Torres: "I can tell you that opportunity is an unmet need pain point or desire, and that's great. But I can tell you that 98% of people that write opportunities write them as solutions. So we tend to just really struggle with this distinction between the problem space and the solution space."
True discovery requires defining every opportunity strictly as an unmet customer need rather than a pre-conceived feature idea.
Remove layers between builders and users
Brian Tolkin: "Talking to customers every single day like one-on-one onboarding drivers responding to support tickets, there's no centralized support team, there was no closer to the customer, right? And so I think that foundation actually for really understanding what moves the business and being super close to the customer actually is a pretty good foundation for them going on to say, okay, what do we actually want to build in a more scalable technology way?"
