Users say your product has gotten too complex
As you added features, your product became harder to use. Users who loved the simplicity now feel overwhelmed. Feature creep is silently killing retention. This happens to almost every successful product - Jira went from a simple issue tracker to a tool that requires a certified admin, and lost massive ground to Linear because of it. The paradox is real: users request features, you build them, and then those same users complain about complexity. Research from the Harvard Business Review shows that product complexity is the #1 reason loyal customers switch, ahead of price and competitors. Every feature you add makes your product 1% harder for everyone, even users who never touch it, because it adds cognitive load to navigation, search, and onboarding.
TL;DR
"Users say your product has gotten too complex" is a common retention problem. Key signs include long-time users (12+ months) specifically complain about recent changes making things harder and new feature adoption is under 10% despite being the #1 user request. Start by trying: Add role-based or use-case-based views that hide irrelevant features (linear shows only what's relevant to your workflow).
Overview
If you're dealing with “users say your product has gotten too complex”, you're not alone. This is one of the most common retention 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
- Long-time users (12+ months) specifically complain about recent changes making things harder
- New feature adoption is under 10% despite being the #1 user request
- Support tickets about confusion or "how do I" increasing 20%+ quarter over quarter
- Users request a "simple mode", "classic view", or "lite version"
- Time to complete core tasks has increased measurably (30%+ slower than 6 months ago)
- New user onboarding completion dropped as product grew more complex
Why this happens
- Every feature request got built without pruning - addition bias with no subtraction
- No information architecture redesign as product grew from 5 features to 50
- Power user needs drove complexity for everyone - 5% of users shaped 100% of the UI
- Features added but never removed, deprecated, or hidden behind progressive disclosure
- Navigation structure didn't scale with feature count - what worked for 10 features breaks at 40
Quick wins to try
Add role-based or use-case-based views that hide irrelevant features (Linear shows only what's relevant to your workflow)
Create a simplified default experience with an advanced mode toggle for power users
Audit features and hide or remove anything with under 5% monthly active usage
Improve navigation with better grouping, search, and a command palette (Notion's cmd+K is used more than their sidebar)
When to prioritize this
When "too complex" or "confusing" appears in 15%+ of feedback, or when new user onboarding completion drops below 50%. Simplify before you lose the users who loved your original product - they're your highest-value cohort and the hardest to win back.
Ready to solve “users say your product has gotten too complex”?
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