The instinct in product development is to add — one more feature, one more setting, one more selling point. Often the real improvement is the opposite: find the part causing the complaints and take it out.
When a product is drawing repeated complaints, the reflex is to reach for more. Add a mode. Add an accessory. Add a clever mechanism that promises to solve the frustration. It feels like progress, and it makes for a longer feature list on the box. But more often than we'd expect, the feature list is exactly where the problem lives. The thing customers hate isn't something the product is missing — it's something the maker bolted on to look competitive.
So before we ask what a product needs, we ask a quieter question: what could it lose? A surprising number of the best improvements we come across aren't additions at all. They're subtractions.
Complexity is where products break
Every extra part is another thing that can fail, jam, confuse, or wear out. A moving mechanism seizes. A second setting no one understands generates support emails. An adjustable feature loosens over time and becomes the exact rattle people complain about. When you read the one- and two-star reviews of an over-built product, the pattern is usually the same: the failures cluster around the fanciest parts, not the simple ones.
That's the tell. If the complaints trace back to a component that was added to differentiate the product rather than to make it work, the strongest fix might be to design that component out entirely. Fewer parts, fewer failure points, fewer things to explain. The product gets more reliable precisely because there's less of it.
Removing a part usually helps the margin too
Subtraction has a second advantage that addition never does: it tends to make the economics better, not worse. Adding a feature adds cost — new tooling, another component, extra assembly, more that can go wrong under warranty. Removing one strips cost out at the same time as it strips out the complaint. You end up with a product that's cheaper to make, simpler to ship, and less likely to come back.
That matters because we hold every idea to an honest margin. A fix that solves the complaint but wrecks the contribution margin isn't really a fix — it's a more expensive way to lose. Subtraction is one of the few changes that can push reliability up and cost down in the same move, which is why we look for it first.
The discipline is knowing which part to keep
This isn't an argument for stripping products to the bone. Take away the wrong thing and you've gutted the reason people bought it. The skill is telling the difference between the part that's doing real work and the part that's only there to pad the marketing. The first is sacred. The second is fair game.
We work that out the same way we find everything else: in the reviews and in the conversations. What do people actually use? What do they praise? What do they switch off, ignore, or wish wasn't there? When a feature is quietly cursed by everyone who owns the thing, that's not a feature — it's a liability wearing a feature's clothes. And the honest improvement is to let it go.
One clean job, done properly
The products we like best do one thing and do it without drama. They're easy to explain, easy to trust, and hard to break because there isn't much to break. That's not a compromise; it's the point. A single, well-made SKU that nails its one job will usually beat a cluttered competitor that does five jobs adequately and two of them badly.
So when we look at a product that's frustrating its owners, we don't only ask what's missing. We ask what's in the way. Sometimes the best version of a product is the one with a part removed — and the complaint removed along with it.
Adding is easy and it looks like effort. Taking the right thing away is harder, and it's often where the better product has been hiding the whole time.