Your Product Might Not Need More Features — It Might Need More Discovery

The idea that a product may need better discovery rather than more features is a useful perspective for product teams. Improving onboarding, navigation, search, and helping users understand existing functionality can sometimes create more value than continually adding new features.

Discovery channels are chosen by what you measure, not by what actually works. Most teams measure reach: which platform has the biggest audience? But reach isn't the right measurement for discoverability.

The right measurement is resonance-to-reach ratio: what fraction of reachable people actually engage? A niche community with 60% engagement beats a massive audience with 0.5% engagement every time. Your discovery channel choice should be driven by which measurement system reveals the truth about where your specific users actually pay attention.

This is so true. It’s easy for founders to convince themselves that one more feature will be the thing that unlocks growth, when the real problem is often that not enough people know the product exists.

Distribution should be part of the product-building process, not something you think about after the product is “finished.”

This is the trap most of us fall into: building feels like progress, distribution feels like rejection.

What finally shifted it for me: I started treating "where do users already complain about this problem?" as a feature request. Turns out my users were asking for things in public forums for months — I just wasn't there to hear it.

A rule that helped: every hour of building gets an hour of showing up where the problem is discussed. Not pitching — answering. The product roadmap literally rewrote itself from those threads.

Features get you retention. Discovery gets you users. And users are the only ones who can tell you which features actually matter.