What do you prioritize when a product has too many features but users still feel lost?
I’ve been thinking about a problem that seems to become more difficult as products grow: adding features can make a product more capable while also making the experience harder to understand.
A product might start with one clear workflow, then gradually add dashboards, integrations, settings, automation, notifications, and other features. Eventually, the challenge isn't necessarily “what should we build next?” but “how do we keep the main experience simple?”
My instinct is to separate the core workflow from everything else and make secondary features progressively discoverable rather than putting everything in front of the user at once. But I’m not sure that works equally well for every type of product.
For people who have built or redesigned products as they grew:
How have you decided what should remain immediately visible and what should be hidden behind menus, settings, or secondary screens?
Have you ever removed or moved a feature because it was making the product harder to understand?
I’d be particularly interested in examples from SaaS, AI products, developer tools, or products with increasingly complex workflows.
Replies