Hebel

Systems archetypes

Seeking the Wrong Goal

Systems are highly reliable at reaching the goal you set them — the catastrophe lies in setting the wrong one.

BSystem drives toward the stated proxy goalRProxy-gaming crowds out real value

Definition

Seeking the Wrong Goal is a system trap described by Donella Meadows: systems are remarkably efficient at achieving the goals set for their feedback loops. That is precisely why catastrophe strikes when the quantitative indicator is a poor proxy for the truly desired outcome (GDP for well-being, test scores for education quality). When the proxy becomes the goal, the system reconfigures to maximise the proxy at the expense of real value — closely related to Goodhart’s Law.

Structure

A balancing loop (B) drives the system relentlessly toward the stated proxy goal: deviation detected → correction → indicator back to target. As long as the indicator and the real goal coincide, this is useful. When they diverge, a reinforcing loop (R) of proxy-gaming also appears: hitting the indicator is rewarded, so more effort flows into optimising the metric itself — which increasingly crowds out real value. The system gets measurably “better” and actually worse.

When it applies

Economies maximising GDP growth while quality of life and the environment suffer. Schools raising test scores instead of educating. Sales teams hitting close rates while torching customer relationships. Whenever a conveniently measurable metric stands in for the outcome you actually want.

Leverage points

Do not confuse indicators with welfare. Regularly audit metrics for whether they still capture the intended real-world result, and re-specify the goal to the outcome you actually want — not its convenient proxy. It helps to carry several countervailing measures (so no single proxy dominates) and to deliberately keep qualitative goals that resist compression into one number.

Examples

A country prizing GDP above all while ignoring inequality and environmental harm. A hospital meeting waiting-time targets by relabelling patients. A support team rapidly “closing” tickets without solving problems.

Model it in Hebel

Build this pattern as a causal loop and simulate it.

Get invited

Related concepts

Sources: Meadows (2008), Thinking in Systems · Goodhart (1975)