Feature Factory¶

The product-organisation anti-pattern of measuring success by features shipped per unit time while never asking whether any feature changed an outcome — a proxy output displacing the target it was meant to track, Goodhart's Law in the product operating loop.

Core Idea¶

A feature factory is the product-organisation anti-pattern in which success is measured by the number of features shipped per unit time, the operating rhythm is calibrated to keep throughput high, and whether any shipped feature changed user behaviour, revenue, or retention goes unasked. The output metric substitutes for the outcome metric through a four-stage move: a target outcome motivates the org, a measurable proxy output is rewarded, the loop closes on the proxy, and output and outcome decouple — Goodhart's Law in the product loop.

Scope of Application¶

Feature factory lives within product organisations, across every surface form the proxy-for-outcome substitution takes in software-product and digital-delivery work.

Roadmap-by-feature-list planning — a feature list carrying no outcome hypotheses or kill criteria.
Velocity-as-headline-metric cultures — story throughput as team health, outcomes never gating the next sprint.
Launch-then-move-on practice — features shipped and left behind with no instrumented validation.
Sales-led roadmaps — every feature promised to a deal, no one revisiting whether it is used.
Innovation theatre and after-the-fact bar inflation — feature counts substituting for outcome movement.

Clarity¶

Naming the feature factory reframes "we ship a lot but the numbers aren't moving" from an execution story into a metric-substitution diagnosis: the team may be correctly optimising the metric placed in front of it, and the defect is which metric the loop closes on. It sharpens the output/outcome distinction throughput charts erase and licenses one diagnostic question: for each shipped feature, what outcome was hypothesised, and was it measured?

Manages Complexity¶

Product organisations present a scatter of dysfunctions — sales-led roadmaps, velocity obsession, transformation theatre — that a leader might fix separately. Feature factory collapses them into one mechanism: the loop closed on a proxy. The diagnosis reduces to a single measurable ratio (the answer-rate to the outcome-hypothesis question), and one intervention family fixes all variants: pair every committed output with an outcome hypothesis and kill criterion before commit.

Abstract Reasoning¶

The proxy-target decoupling licenses diagnosis from the answer-rate not the throughput (and reading gaming tells), interventionist rewiring of the operating-metric graph rather than exhorting the team (predicting throughput should fall when fixed), boundary-drawing (is the outcome knowable and abdicated, versus deliberately deferred exploratory work), and an order-of-events forecast (the decoupling widens over time and surfaces late).

Knowledge Transfer¶

Within product organisations the diagnosis transfers as mechanism across every surface form — one mechanism with the pathology swapped — the answer-rate diagnostic and forcing-function fix carrying intact, supported by the outcomes-vs-outputs literature (Cutler, Cagan, Torres). The named concept stops at product orgs; its breadth is one substrate replayed. What travels to distant systems is the target_measure_substitution / Goodhart parent (test-score gaming, hospital waiting times, command-economy tonnage); the product-management vocabulary and the name stay home.

Relationships to Other Abstractions¶

Current abstraction Feature Factory Domain-specific

Parents (2) — more general patterns this builds on

Feature Factory is a kind of, typical Build Trap Domain-specific

A Feature Factory is the characteristic request-and-throughput realization of the broader Build Trap, though the full three-dial regime is not guaranteed.
Feature Factory is a decomposition of Proxy-Target Divergence Prime

Stripped of product vocabulary, the factory is an operating apparatus closed on a controllable proxy after that proxy has decoupled from its target.

Hierarchy paths (2) — routes to 2 parentless roots

Feature Factory → Build Trap

Show alternative path (1)

Neighborhood in Abstraction Space¶

Feature Factory sits in a crowded region of the domain-specific corpus (35^th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Proxy Metrics & Venture Adaptation (13 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-07-12