The best product I ever built had three features. The worst product I ever built had twenty-seven.
The three-feature product was profitable within six weeks. Customers understood it immediately, recommended it to colleagues, and rarely needed support. The twenty-seven-feature product confused everyone, generated more support tickets than revenue, and was eventually shut down after a year of struggling.
The difference wasn’t the quality of individual features. Both products had well-built, thoughtful features. The difference was that the three-feature product was easy to understand, easy to use, and easy to explain to someone else. The twenty-seven-feature product was none of those things.
Building less is harder than building more. Adding features feels productive. Removing them (or never adding them) feels like giving up. But the most successful products in history succeed through what they leave out, not what they include. Apple didn’t make the iPod by adding features — they made it by removing everything that wasn’t essential to playing music.
The Subtraction Mindset
Most founders operate with an addition mindset: the product needs to be better, so I need to add something. More features, more integrations, more options, more content.
The subtraction mindset asks a different question: what can I remove that would make the product better? What’s getting in the way of the customer reaching the core outcome?
Here’s how to shift from addition to subtraction:
Step 1: List every feature in your product.
All of them. Including the ones you’ve forgotten about. The settings page counts. The help section counts. Every button, every page, every workflow.
Step 2: For each feature, ask: “If I removed this, would a paying customer complain?”
Not a free user. Not a potential customer. A paying customer — someone who’s given you money and is actively using the product.
Step 3: For every feature where the answer is “no,” remove it. Or at minimum, hide it behind an advanced settings panel. If nobody would miss it, it’s clutter. Clutter confuses new customers, increases support burden, and slows down development.
I run this exercise — a subtraction audit — every quarter. Each time, I find 2-5 features or elements that can be removed without anyone noticing. The product gets simpler. Support tickets drop. New customer comprehension improves. And the development team can focus on fewer things at a higher quality.
Why Customers Ask for More But Want Less
There’s a paradox in customer feedback: customers request more features but prefer simpler products.
When you ask a customer “what should we add?” they’ll always have an answer. A new integration, a new view, a new export format, a new option. Each request is individually reasonable.
But when you observe how customers actually use the product — through analytics, screen recordings, or session observations — you discover that 80% of usage concentrates on 20% of features. The features customers request are features they think they want. The features they actually use are the ones that deliver the core outcome.
This is why customer feedback should inform but not dictate product decisions. Listen to what they request. Observe what they use. Build based on the observation, not the request.
A founder I advised was getting constant requests for a mobile app. The analytics showed that 97% of usage happened on desktop during business hours. A mobile app would have cost 3 months of development time to serve 3% of usage. Instead, they invested those 3 months in improving the desktop experience — which was where the actual value was created.
The Feature Kill Protocol
When you decide to remove a feature, here’s the protocol I follow.
Step 1: Check usage data. What percentage of active users used this feature in the last 30 days? If it’s below 5%, removal is almost certainly safe.
Step 2: Notify affected users. If anyone is using the feature, give them advance notice. “We’re simplifying [product] and removing [feature] on [date]. Here’s what we recommend instead.”
Step 3: Remove it cleanly. Don’t leave ghost references — dead links, empty menu items, or orphaned settings. A clean removal means nobody encounters a trace of the feature after it’s gone.
Step 4: Monitor for complaints. Wait 2 weeks. If nobody complains (or only 1-2 people do), the removal was correct. If a significant number complain, consider restoring it.
Step 5: Document the decision. Why was this feature removed? What data supported the decision? This goes in the anti-feature list to prevent it from being rebuilt in 6 months when someone has the same idea again.
Most of the time, Step 4 produces silence. Features you think are important often aren’t. The courage to remove them comes from trusting the data over your attachment.
Strategic Subtraction in Business Operations
Subtraction isn’t just for product features. It applies to everything in your business.
Subtract marketing channels. If you’re posting on Twitter, LinkedIn, Instagram, and a blog, and only LinkedIn drives customers, drop the other three. One channel, mastered, outperforms four channels half-executed.
Subtract customer segments. If you serve three customer types but one generates 80% of revenue and the other two generate headaches, focus exclusively on the profitable segment. Say no to the others.
Subtract meetings. Every recurring meeting should justify its continued existence every quarter. If a meeting doesn’t produce decisions, learning, or accountability, kill it.
Subtract tools. Your tool stack should be audited quarterly. Every unused subscription is a subtraction opportunity.
Subtract your own involvement. The owner dependency score measures how much the business depends on you specifically. Reducing that dependency — through documentation, delegation, and automation — is subtraction of the most important kind.
The Simplicity Premium
There’s a market advantage to being simple that most founders underestimate.
In a market full of complex products, the simple one wins. Not because simplicity is inherently better, but because:
Simple products are easier to sell. “It does X” is a clearer pitch than “It does X, Y, Z, and also sort of does A and B with the premium plan.” Clear pitches convert better.
Simple products are easier to onboard. If a customer can get value in 5 minutes with no tutorial, they’re more likely to stay than if they need a 30-minute training session. Time to first value is directly correlated with retention.
Simple products generate less support. Fewer features means fewer things that can confuse or break. Lower support burden means lower cost to serve, which improves unit economics.
Simple products are easier to improve. A product with 3 features can be improved faster and more thoroughly than one with 27. Development velocity on a focused product is dramatically higher.
The simplicity premium is real and measurable. Track your conversion rate, onboarding completion rate, support ticket volume, and development velocity. Subtract features and watch these numbers improve.
Key Takeaways
- The most important product decisions are what you leave out. Three focused features beat twenty-seven scattered ones.
- Run a subtraction audit quarterly. List every feature, ask “would a paying customer complain if this disappeared?”, and remove everything that gets a no.
- Customers request more but prefer less. Listen to what they ask for but observe what they actually use. Build for usage, not requests.
- Follow the feature kill protocol: check usage, notify affected users, remove cleanly, monitor, document.
- Apply subtraction to everything: marketing channels, customer segments, meetings, tools, and your own involvement. Simplicity creates a competitive advantage.
