Feature creep is the gradual accumulation of features beyond a product’s core purpose — each addition individually defensible, the sum a slower, harder, blunter product. It enters through reasonable doors: the big customer’s “one thing,” the sales team’s lost-deal checklist, competitor matching, and the organisational truth that shipping something new is more rewarded than deleting something old. The costs compound invisibly: interface complexity taxes every user, each feature multiplies QA surface and technical debt, and positioning blurs until the product is “everything for everyone,” which converts as nothing for anyone.
The counter-disciplines are structural rather than heroic: a sharply written product strategy that makes “no” explainable, a single owner with deletion authority, usage instrumentation that exposes zombie features, cost-of-ownership estimates attached to every feature request, and periodic pruning treated as seriously as launching. The MMF/MVP lens helps — every addition should either serve the core job or be consciously priced as a new bet.
Creep in the contract stack
Feature creep has a legal twin. Every shipped feature widens the compliance surface: new data types collected (privacy notices and records of processing now stale), new integrations (new DPAs and security reviews), occasionally a regulated capability absorbed casually — payments, health data, messaging — that quietly changes the company’s licensing posture. Enterprise contracts deepen the lock-in: features promised in order forms or roadmap commitments cannot be deleted without breach analysis, which is why pruning programs need contract review as much as code review. Lean products are easier to govern; that is not a metaphor.
If this is on your desk
Templates and checklists are free in the Founder Academy; for a specific situation, book a 30-minute intro call.
Founder AcademyBook an intro call