A feature factory is a team that measures success by how much it ships, features launched and story points closed, instead of by what actually changes in the user. The term was coined by John Cutler.
The tell is subtle: a feature factory usually looks productive. It ships fast, keeps velocity high, and has a visible record of finished work. It has optimized the activity of building, not the result of building.
Warning signs you’re in one
- Success is measured in output (releases, points, features), not in behavior change or business outcomes.
- Features get added because a competitor has them, a big customer asked, or someone said “it’d be nice to have,” each with its own local logic and no target behavior behind it.
- Nobody can answer “what new behavior did we install this quarter?”
- The roadmap grows; the reason for any single user to stay does not.
Why teams fall into it
Not on purpose. Productizing produces immediate signals of progress, demos, changelogs, meetings where you show something new, while changing behavior is invisible for months. Almost no organization rewards the invisible. It rewards activity. And adding surface is activity.
What it costs
Roughly 80% of the features in average software are used rarely or never, and only about 12% drives most of the daily use (Pendo; the Standish Chaos report puts it near 64%, methodologies debatable, direction consistent). That’s surface that exists without changing anything, plus the growing team needed to maintain it. It’s not free. Every living line carries a cost every day, used or not.
The one test that gets you out
Before anything goes on the roadmap, complete this sentence:
Thanks to this, [type of user] will go from doing [X] to doing [Y], and we’ll know it when we see [metric Z].
If you can’t fill it in, you have a feature idea, not a product idea. Making product is installing a behavior, not accumulating surface. That distinction is the difference between a moat and attention debt, and in the AI era, when copying a feature costs an afternoon, it’s the only one that matters.
FAQ
Who coined “feature factory”? John Cutler.
Is shipping features always bad? No. Sometimes productizing is the right call, reaching parity, keeping a customer, buying time. The problem is doing it on autopilot, without knowing it.
How is this related to AI coding? AI makes generating features nearly free, which accelerates the feature factory unless intent and verification sit upstream. The discipline that counters it is the same idea applied one level down: a green build is not a correct feature.