A feature factory is a product team that measures success by features shipped rather than outcomes achieved. Features go out the door on schedule, the roadmap keeps moving, and everyone looks busy, but nobody's asking whether any of it actually made the product better.
John Cutler popularized the term. It stuck because the pattern is extremely common and hard to escape once you're in it.
What it looks like from the inside
The backlog is always full. Stakeholders add to it constantly. The team's job is to execute: estimate, build, ship, repeat. Discovery is thin or skipped entirely. Success is measured in features delivered, not problems solved.
You can read more about how this plays out in practice on the FeatureOS blog.
Why it's hard to break out of
Feature factories don't usually start that way. They evolve from good intentions, a team trying to be responsive to customers, to leadership, to the market. Over time, that responsiveness calcifies into a delivery machine.
Breaking out requires changing what you measure. If your team is only accountable for shipping, that's what you'll get. Tie work to outcomes like retention, activation, or revenue, and the calculus changes.
The fix isn't to ship less
It's to ship things that matter. A team shipping half as many features but moving the needle is doing better work than a team hitting every sprint target without knowing why.