More Options Make Users Quit

The roadmap is a lie you tell yourself. Every feature on your roadmap felt reasonable when someone added it. A user asked for it, or a competitor shipped something close, or a stakeholder needed to show progress in the quarterly review. One by one, each addition made sense. Together, they turned your product into something that takes three days to learn, a dedicated admin to configure, and a five-minute onboarding video that nobody watches. The people you built it for are right now looking for something simpler.

Most product teams treat this as someone else’s problem.

Adding features feels like care. It looks like ambition. It gives everyone in the room something concrete to point at. What it actually does is shift work onto the person you built the product for. Every option you add to a screen is a small decision you are handing to your user, and most of them did not sign up to make decisions. They signed up to do the thing the product promised to help them do. When the product makes that harder instead of easier, they find something that does not.

People choose the feature-heavy version, then regret it

Here is the pattern that nobody wants to see in their analytics. Before people buy a product, they care a lot about what it can do. The longer the feature list, the more capable the product looks. That logic drives purchase decisions every day. But once people start using something, their priorities flip. Now they care about how easy it is to use, and all those features that looked so good in the comparison chart become things they have to navigate around. Debora Viana Thompson, Rebecca Hamilton, and Roland Rust at the University of Maryland ran three separate studies on this and published the results in the Journal of Marketing Research in 2005. They found that consumers “tend to choose overly complex products that do not maximize their satisfaction when they use them,” a pattern they named feature fatigue. People pick the product with the most features and then get worn down by it. The feature list closes the deal. The feature list then loses the customer.

Users cannot predict this about themselves. Before they have a product, they genuinely believe they will use the advanced reporting view, the bulk action tools, the custom workflow builder. Then they have it, and all they want is to move a ticket from one column to another without clicking through four confirmation dialogs. Barry Schwartz called this the paradox of choice: more options do not produce more satisfaction, they produce more anxiety and more regret. The rational response to that feeling is not to choose more carefully. It is to stop choosing at all.

Eight out of ten features are dead weight

In 2019, Pendo analyzed feature usage across 615 software products and found that 80 percent of features were rarely or never used. Not infrequently. Rarely or never. Pendo estimated that publicly traded cloud software companies had collectively spent up to $29.5 billion building features that generated almost no daily usage. Every one of those features had a ticket, a designer, a developer, a code review, and a release note. Then nothing.

Those unused features do not disappear once you ship them. They live in your navigation, your onboarding flow, your settings screen. Every new user has to scan past all of it to find what they came for. William Hick measured the cost of that scanning in 1952: decision time rises as options multiply, and the first few additions to any screen are the most expensive ones. Each one slows users down a little more. Past a certain point, they stop trying and leave.

Jira has every feature you could want and teams hate using it

Jira started as a bug tracker in 2002. Clean, fast, specific. You filed a bug, tracked it, it got fixed. Then over two decades it grew. Custom fields, permission schemes, automation rules, roadmap views, service management modules, portfolio planning tools, a marketplace with thousands of plugins. Jira can, in theory, run your entire organization.

Most teams do not want it to.

What happens at companies that use Jira at any real scale follows a pattern you will recognize. It starts with a simple board. Then someone adds a custom field because the defaults do not cover what they need to track. Then another team joins and brings their own workflow. Then a process change requires a new issue type. Then the permission layers stack up until nobody knows who can see what. Then a new developer joins and needs a week before they can work without someone showing them around. Jira admins become a full-time job at teams bigger than fifty people. Teams that switch away name complexity as the primary reason. Not cost. Not missing features. Too many features, organized badly.

Linear launched in 2019 with a single bet. Fast. Opinionated. No custom fields. Fixed issue statuses. The tool makes decisions so you do not have to. Pages load in milliseconds. An issue takes two seconds to create. Linear does less than Jira by design. Development teams moved to it by the thousands, not because it was more capable, but because it got out of the way.

That is the whole argument, made visible.

The options audit

Before you ship any screen, count the decisions it asks users to make. A top-nav item is a decision. A secondary button is a decision. A settings panel that opens from inside another settings panel is a decision stacked on a decision. If the total is above five, something needs to go. Not into a dropdown. Not behind a “more” link. Gone.

The test for whether a feature stays is not whether somebody asked for it. That test keeps everything, because somebody always asks for something. The test is whether taking it out would break the main task for most of your users most of the time. If you cannot answer that with usage data, the feature is probably not earning its place on the screen.

Thompson and her colleagues found something that belongs in every roadmap meeting: as companies focus more on keeping customers long-term, the right number of features goes down, not up. Simpler products hold users longer. The product that loaded up on features to win the sale pays for it later in churn, in support tickets, in the quiet departure of users who stopped logging in and never sent a cancellation email. You will not see the moment they gave up. You will see it in the retention report three months later.

Do not add a new feature to win them back. Strip the roadmap. Audit the navigation. Kill anything nobody asked for twice. The product that does one thing so well that users never have to think about how to use it is much harder to build than the product that does everything. It is also the only one worth building.

Every feature you add is a tax. Your users pay it whether they wanted it or not.