Every feature you add is a promise you have to keep forever. It has to be maintained, supported, documented, and explained to every new user — long after the excitement of shipping it fades. Which is why the most underrated founder skill isn’t generating ideas. It’s killing them.
Your best ideas are the most dangerous ones
Bad ideas die on their own. It’s the good ideas that quietly sink products — because each one is individually justifiable, and collectively they bury the one thing your product was supposed to do brilliantly. Nobody churns because you lack features. They churn because they can’t find the value in the pile.
A simple filter that works
Before anything goes on the roadmap, make it pass three questions:
- Does it serve the core promise? Not “is it useful” — everything is useful to someone. Does it make the main job your product does faster, clearer, or more reliable?
- Will you still want to maintain it in two years? Features age. Integrations break. If the answer is “we’ll deal with it later,” the answer is no.
- What are you saying no to by saying yes? Engineering time is zero-sum. The real cost of a feature is the better thing you didn’t build.
Write the no down
A decision to not build something evaporates unless you record it. Keep a simple “not doing” list with one line of reasoning each. It stops the same debate from resurfacing every quarter, and — more often than you’d expect — reading old entries confirms the no was right.
Focus isn’t the absence of ideas. It’s the presence of a decision.
Being frugal with scope is the same discipline as being frugal with money: it’s not about doing less, it’s about refusing to spend on what doesn’t compound.