Why can shipping one more feature make a product feel worse to use?

Shipping one more feature can make a product feel worse because every feature adds interface, choices, and surface area, and that accumulation crowds the core even when the new feature is individually good. Capability and clarity do not move together. A product can grow steadily more powerful while growing harder to navigate, heavier to scan, and less obvious about what it is actually for. Each addition is a small, defensible weight, but usability erodes through the sum, not through any single bad decision. The product that feels worse is rarely the one with a bad feature. It is the one with too many reasonable ones.

The mechanism is that a feature is never just its own functionality. It brings a button or a menu entry, a setting, a place in the navigation, an edge case in every adjacent flow, and one more thing the user has to recognize and route around to reach what they came for. Attention is finite, and a screen has a fixed budget of prominence. When a new feature takes its slice, the core actions get a thinner slice, the menus get longer, the choices at each step multiply, and the path to the common task gets buried under the rare ones. The product did not get worse at anything specific. It got noisier everywhere, and noise is exactly what makes an interface feel heavy. This is why “more features make a better product” quietly fails. It counts the value of each feature and ignores the cost each one imposes on the clarity of all the others.

Picture a writing app that launched clean, just a page and a place to type. Then it added a comments panel, a templates gallery, a publishing menu, a formatting toolbar with thirty options, an integrations tab, and a sidebar of suggestions. Every one of those was requested by someone and shipped for a real reason. But the writer who opens it now to do the one thing the app exists for, write, lands in a cockpit. The blank page is surrounded by panels, the toolbar competes with the words, and the single core act is now one option among dozens. No feature is bad. The accumulation made the simple thing feel hard, and that is the worse experience.

Where this breaks down is that accumulation is not the same as a hard feature cap, and the answer is not to stop building. Some products genuinely need depth, and a tool for experts can carry many features if they are tiered, deferred, and kept out of the common path. The erosion comes from features competing for the same prominence as the core, not from features existing at all. A deep product stays usable when its surface stays shallow, when the rare powers sit behind progressive disclosure and the everyday acts stay front and center. The cost is real whether or not you choose to pay it. It just gets hidden when depth is organized.

When the next feature is on the table, do not only ask whether it is good. Ask what it costs the clarity of everything already there, what prominence it will claim, and what it will push down to make room. If it earns a place, find a way to add it without crowding the core, behind a tier, a menu, a deferred reveal. Treat every addition as a withdrawal from a fixed attention budget, and you will keep the product feeling light even as it grows capable.