Users never find your best features
You built powerful features, but users stick to the basics and never explore. They're getting 10% of the value because they don't know the other 90% exists. Slack found that teams using channels, integrations, and search were far stickier than those who just used DMs. Most products have a similar pattern: 2-3 features that are strong retention predictors, and most users never discover them. If your feature usage data looks like a power law where one feature gets 80% of usage, you have a discovery problem, not a product problem.
TL;DR
"Users never find your best features" is a common activation problem. Key signs include most users only use 1-2 features out of a dozen available and power features have single-digit percentage adoption rates. Start by trying: Add contextual tooltips that appear when a user does something the hard way that a feature could solve.
Overview
If you're dealing with “users never find your best features”, you're not alone. This is one of the most common activation challenges that solo founders and indie hackers face. Below you'll find the warning signs to watch for, root causes to investigate, and quick wins you can try today.
Signs you have this problem
- Most users only use 1-2 features out of a dozen available
- Power features have single-digit percentage adoption rates
- Users submit feature requests for things that already exist in the product
- Feature announcement emails get under 10% open rate
- Users who discover key features retain 2-4x better than those who don't
Why this happens
- Features are hidden behind hamburger menus, settings pages, or nested navigation
- No contextual prompts to introduce features when they'd be most useful
- Users developed habits before new features launched and never changed workflow
- Feature names describe mechanics ('batch operations') not outcomes ('update 100 items at once')
- No progressive disclosure strategy - everything is either shown or hidden
Quick wins to try
Add contextual tooltips that appear when a user does something the hard way that a feature could solve
Create a 'did you know?' prompt triggered by behavior, like Notion's slash command hints
Rename features to describe outcomes, not mechanics - Superhuman calls it 'split inbox' not 'email categorization'
Build a feature adoption checklist users can track with visible progress
When to prioritize this
When there's a 2x+ retention difference between users who discover key features and those who don't. Run a correlation analysis between feature usage and 30-day retention to identify which features to push.
Ready to solve “users never find your best features”?
Golden Gecko matches you with the right experiments based on your specific situation. Sign up free to get step-by-step guidance and track your results.
- AI matches playbooks to your goals
- Step-by-step experiment guidance
- AI interprets your results