Product teams are rewarded for adding. New features make roadmaps look alive, launch notes feel substantial, and meetings end with a reassuring sense of momentum. The harder discipline is subtraction: deciding which request, platform, workflow, or product line should never be built in the first place.
A feature is never just a feature. It is a permanent obligation to secure, support, explain, update, test, and eventually untangle.
In a thoughtful essay on product restraint, Liam Nugent uses the familiar examples of a document hub and a notifications centre. Both sound harmless at first. A stakeholder wants one place for documents. Another wants a bell icon. But each generic solution can expand into a costly mini-platform with permissions, archives, channels, status rules, edge cases, and years of maintenance.
Build cost is the easy number
Teams often estimate the cost of getting something live. That is only the opening bill. The real cost arrives later: operating-system changes, browser quirks, compliance updates, accessibility work, analytics, customer support, security reviews, integrations, and the inevitable request to add one more exception.
For a local business, agency, or software team, this is more than an engineering concern. Complexity slows down marketing, service delivery, and customer communication. Every unnecessary system creates another place where a customer can get lost and another process staff have to remember.
Before approving a new hub, dashboard, portal, or internal tool, ask a more useful question: what specific customer job cannot be handled by a simpler workflow or an existing capability?
The danger of the universal solution
One-size-fits-all products are seductive because they appear to solve several problems at once. Yet broad platforms often become a compromise for every use case and a great experience for none of them.
A document centre can become a poorly maintained file manager. A notification centre can become a second-rate inbox. A custom customer portal can become a small software company hiding inside a business that was supposed to sell a service.
The best product decision is frequently a focused decision: solve the job in front of you without building an entire universe around it.
Make removal visible
Additions are easy to celebrate. Deletions are harder to present as progress, even when they reduce support tickets, improve conversion, and make the customer journey clearer. That is a management problem as much as a product problem.
Track the work that gets removed. Measure the systems that do not get created. Include ongoing maintenance in every business case. When teams can see the future burden of a proposed feature, they are more likely to challenge whether it earns its place.
Pruning is not anti-innovation. It is how a company protects attention and investment for the things that genuinely matter.
AI makes the question more urgent
With AI tools lowering the cost of prototyping and code generation, the temptation to build everything gets stronger. A fast prototype can make a weak idea feel inevitable. But cheap creation does not make a feature cheap to own.
The strategic use of AI may be to help teams audit, simplify, maintain, and retire digital clutter. Use it to identify duplicate workflows, summarize recurring support issues, spot unused pages, and find complexity that no longer serves the customer.
A practical filter for new requests
- Name the customer job: describe the exact outcome someone needs, not the product feature being proposed.
- Find the simplest path: test existing channels and tools before inventing a new platform.
- Price the lifecycle: include support, security, updates, training, and retirement in the decision.
- Assign an owner: if nobody owns the feature for its full life, it should not be added.
- Decide what comes out: a new addition should trigger a conversation about what can be removed.
The bigger lesson
Good product strategy is not an inventory of everything a company can make. It is a commitment to concentration. By refusing to build the wrong things, teams make room to build the few things that improve the customer experience and the business at the same time.
Source: Liam Nugent,+�u���\The most important product decision is what you don�w^~)�ut builk�u���].