That feature nobody asked for? It's quietly costing you.

Unused features do not sit politely in the backlog like spare socks. They live in the product, the docs, the pricing page, and the onboarding tour that now takes seventeen minutes. Shipping something nobody asked for feels like progress. It is often a tax you will keep paying with interest, which is a very modern kind of generosity toward your future self.

The cost is not only engineering hours. Complexity slows decisions, dilutes the story, and trains customers to expect a Swiss Army knife that still cannot open the bottle they hired you for. Build less, learn more, and protect the wedge.

Feature appetite vs feature discipline

**Bad SaaS:** a settings panel that looks like an aircraft cockpit because every stakeholder got a toggle. New users bounce before first value. **Good SaaS:** Basecamp-style restraint (or any team that ships opinionated defaults) where the product refuses to be everything and therefore becomes something.

**Bad consumer app:** feature announcements that outpace usage. **Good consumer product:** remove or hide what does not serve the core job, then market the clarity.

Stop paying the unused-feature tax

1. List features with usage under a clear threshold. Mark candidates to hide, cut, or freeze.
2. For each new request, require the job, who asked, and what they do today without it.
3. Add a non-goals list to the roadmap and read it in planning.
4. Measure time-to-first-value before and after any feature that touches onboarding.
5. Rewrite the homepage without orphan features. If you cannot mention them cleanly, they are diluting you.
6. Run a thirty-day build freeze on anything not tied to the wedge after a bloat quarter.

Harvard Business Review still covers jobs-to-be-done as a better filter than competitor bingo. Related: before you build another feature, ask five questions.