Get your free personalized podcast brief

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

Jeff Patton points to Jira, released as a help desk ticketing system but adopted as agile project management. He says companies sometimes notice customers using a product for an unintended purpose, dig in, and find a problem they did not know needed solving; that signal can redirect strategy.

Related Insights

Figma's expansion into multiple products (FigJam, Slides) wasn't based on abstract strategy but on observing users pushing the main design tool to its limits for unintended use cases. Identifying these 'hacks' revealed validated market needs for dedicated products.

When Figma saw users adopting its design tool for unintended purposes like brainstorming, it created separate, dedicated products (e.g., FigJam). This strategy prevents the core product from becoming bloated and complex, allowing each new product to develop its own focused identity and user experience.

Intentionally create open-ended, flexible products. Observe how power users "abuse" them for unintended purposes. This "latent demand" reveals valuable, pre-validated opportunities for new features or products, as seen with Facebook's Marketplace and Dating features.

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.

QuickBooks was created after Intuit discovered small business owners were using Quicken—a personal finance tool—for their businesses. This organic, unintended use case revealed a massive, underserved market, highlighting the power of analyzing user data for off-label adoption patterns.

Zapier evolved from a simple trigger-action tool by observing how advanced users "hacked" it for unintended purposes. When users treated Google Sheets like databases, Zapier built Tables and Interfaces, proving that emergent behavior is the clearest signal for your product roadmap.

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.

Uber observed users unofficially using its Courier service for personal shopping. Instead of stopping it, they recognized this "hack" as a clear market signal and built a dedicated "Shop for Me" feature, turning user ingenuity into a new product.

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.

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.