Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

When customers use your product in surprising ways, don't just build features for the new use case. Apply the "demand lens" by rewinding time. Investigate what struggle or "pull" existed in their world *before* they discovered your product to understand the core, pre-existing demand that is driving their behavior.

Related Insights

The most valuable product use cases are often discovered not through surveys, but through deep, intellectually curious immersion into the customer's world. This means observing their environment and processes firsthand to understand latent needs they cannot articulate, as proven by the karaoke company story.

Asking users for solutions yields incremental ideas like "faster horses." Instead, ask them to tell detailed stories about their workflow. This narrative approach uncovers the true context, pain points, and decision journeys that direct questions miss, leading to breakthrough insights about the actual problem to be solved.

If a prospect is unresponsive to discovery questions, describe the specific priorities and blockers of similar customers. Framing case studies around their demand ('they were trying to do X but were blocked by Y') can prompt recognition and help the prospect articulate their own 'pull'.

During customer discovery, don't just ask about current problems. Frame the question as, 'If you had a magic wand, what would the perfect solution be?' This helps users articulate their ultimate desired outcome, revealing profound insights beyond tactical feature requests.

True product demand lies in the gap between what customers are currently doing (observable on their calendar) and their ultimate goals (their mental to-do list). A successful product closes this gap, better aligning a customer's actions with their underlying objectives. This mismatch is where "pull" is found.

Major product opportunities are revealed by observing how customers use your product in unintended ways or "jump through hoops" to achieve a goal. For example, Anthropic noticed non-engineers struggling to use their coding tool, revealing the latent demand for CoWork, a knowledge-work assistant.

Some of the largest markets address needs customers have completely given up on because no viable solution existed. This powerful latent demand is invisible if you only observe current activities. You must uncover the high-priority goals on their mental "to-do list" that they have quit trying to achieve.

Identify how users are already "hacking" your product for unintended purposes (e.g., using Facebook Groups for commerce), then build dedicated features to serve that existing intent. You can't make people do new things, but you can help them do what they already want to do more easily.

Since "blocked" demand is unobservable, you must ask questions that reveal it indirectly. Asking "If I spent $100M to build something for you, what problem would it solve?" forces customers to consider their most critical, unaddressed needs, bypassing their current behaviors and revealing latent demand.

When customers actively work around your product's intended functionality to solve a different problem, it's a powerful indicator of a more significant market need. Following this user behavior can lead to a successful pivot.