Make each feature work hard to be implemented. Make each…
““Make each feature work hard to be implemented. Make each feature prove itself and show that it's a survivor. It's like "Fight Club". You should only consider features if they're willing to stand on the porch for three days waiting to be let in. That's why you start with no. Every feature request that comes in to us — or from us — meets a no. We listen but don't act. The initial response is "not now". If a request for a feature keeps coming back, that's when we know it's time to take a deeper look. Then, and only then, do we start considering the feature for real.””
About This Quote
This interpretation was drafted with AI assistance. It is one reading of the quote, not the author's own explanation.
The quote advises strict feature vetting: only consider features that persistently demand inclusion; otherwise reject.
In simple terms: Reject features unless they prove persistent value.
Key Takeaway
Only adopt features that survive repeated scrutiny.
Themes
product development
feature management
prioritization
efficiency
decision making
Mood
analytical
pragmatic
Type
management
process
When to use this quote
- software roadmap planning
- product backlog grooming
- feature request evaluation
Key Concepts
lean methodology
user feedback loops
strategic planning
Questions to Reflect On
- What criteria define a feature’s persistence?
- How to balance persistence with breakthrough innovation?
A Different Perspective
May be too rigid for innovative ideas.