What you'll understand by the end of this lesson
- Why discoverability is about obvious paths, not adding more labels
- Why features users say they love still show low usage data
- How session replays reveal discoverability failures that analytics miss
- How to audit your product or site for hidden actions and buried content
The principle in plain English
A feature that users can't find is a feature that doesn't exist — from a usage and conversion perspective.
Discoverability is the degree to which users can find the things they need: navigation items, CTAs, product features, content, support options. Poor discoverability doesn't mean those things are absent — it means they're not on the mental paths users follow.
This is important because designers and product teams know where everything is. They built it. They've looked at it hundreds of times. The cognitive model that makes a feature "obvious" to the team is often completely invisible to a first-time user who doesn't have that context.
The fix is not to add more labels, tooltips, or pop-ups explaining how to find things. It's to design paths that are obvious to users with no prior knowledge of the product.
A simple example
A project management tool adds a powerful feature that lets teams create custom workflow templates. The team is excited — in user research, people consistently say this feature is valuable once they find it.
But usage data shows almost nobody uses it. The feature lives in Settings > Advanced > Workflow > Templates. It requires three menu levels and one non-obvious label to reach.
The feature isn't bad. The feature isn't broken. The feature is simply not discoverable. The path to it requires knowledge that most users don't have and never acquire. It might as well not exist.
Why discoverability failures are hard to see from the inside
The curse of knowledge
When you know where something is, you lose the ability to imagine not knowing. This is called the curse of knowledge — and it is the single biggest reason discoverability problems go undetected by the people who built the product.
The solution is observation. You cannot guess your way to good discoverability once you've lost the beginner's perspective. You have to watch real users navigate without guidance.
Session replay tools (Hotjar, FullStory, Microsoft Clarity) let you watch real users navigate your site or product without any intervention. Look specifically for: clicks on non-clickable elements (users think it's a link but it isn't), rage clicks (frustration clicks indicating something expected to be interactive isn't responding), and dead-end navigations where users reach a page and then go back immediately. These are discoverability failure signatures.
High satisfaction, low adoption
A common pattern in SaaS products: a survey asks users about a feature and they rate it highly. Usage data shows the feature is barely used. The apparent contradiction is resolved by discoverability.
Users who have found the feature love it. Users who haven't found it don't answer the survey question because they don't know the feature exists. The satisfaction score is high because it's self-selected from the subset of users who discovered it — not representative of the whole user base.
This means satisfaction scores for individual features are not reliable signals of discoverability. You need usage data, not satisfaction data, to understand whether users are finding something.
CTA discoverability on landing pages
Discoverability isn't only a product problem — it affects landing pages too. A CTA button that blends into the background, a secondary navigation that buries the primary action, or a form that appears below a long block of copy all create discoverability failures.
The test is simple: can a user who has never seen this page before identify what they're supposed to do within five seconds? If the answer requires scrolling, hunting, or guessing — the primary action is not discoverable enough.
Adding more elements to a page to improve discoverability often makes it worse. When everything competes for attention, nothing is obvious. Discoverability improves by simplifying paths and reducing noise, not by adding more signposts. A page with one clear action is more discoverable than a page with five actions, all labelled.
The CRO audit
Look at your site or product and ask:
1. What is the one primary action on each key page?
If you can't name it in one second, neither can a user. And if there are multiple competing primary actions on the same page, all of them are less discoverable than any single one of them would be.
2. Watch five session replays of new users on your most important page.
Where do they click that doesn't respond? Where do they hesitate? Where do they go back? These are the discoverability failure points that analytics won't show you.
3. What is your most-loved but least-used feature?
If you have a feature that scores well in surveys but shows low usage data, map the path to reach it. How many clicks does it take from the homepage? How many of those steps have labels that a new user would understand without context?
A SaaS product team adds a new reporting feature. User survey scores for the feature are high (4.6/5). Usage data shows only 8% of users have tried it. What is the most likely explanation?
You can now find where users get stuck and what they can't find. But what happens when you try to correct a visitor's existing belief head-on? Next — why challenging beliefs directly can make them stronger, and how to reframe instead of confront.