Reality Is the Gauge
Most builders are running a runaway loop. Not because their ambition is wrong. Because their gauge is broken.
The Gauge Problem
A feedback loop has three parts: a setpoint, a gauge, and a controller. The setpoint is the north star — where you want to go. The controller is what executes. The gauge is the only part that reads reality.
When the gauge reads hope, the loop compounds hope. Features ship. Commits accumulate. Velocity dashboards turn green. The team celebrates. And the customer — if there is one — encounters something different from what anyone tested.
A broken gauge does not fail loudly. It fails confidently.
Aspiration as Input
Every builder has a setpoint. The problem is treating aspiration as evidence. "We believe customers want X" is not data. "We watched three customers try X and here is what happened" is data.
The corrective loop is corrective precisely because it compares output to setpoint and adjusts. If the comparison is between your output and your own expectations, the loop corrects nothing — it confirms. That is not a control system. That is a mirror.
| Gauge reading | Loop type | Trajectory |
|---|---|---|
| Internal belief | Runaway | Compounds in one direction until external reality forces correction |
| Lagging metrics | Corrective | Adjusts, but slowly — by the time the gauge reads, the cost is high |
| Leading reality signal | Virtuous | Adjusts before the cost compounds — the loop compounds improvement |
The leading reality signal is the hard part. You have to build the instrument before you need the reading.
What Reality Actually Looks Like
Reality has a specific texture. It is not a report. It is not a metric dashboard. It is not a sprint retrospective.
Reality is watching someone who is not you attempt to use the thing you built.
They navigate differently than you expected. They click where you did not put a button. They misread a label you considered obvious. They give up at a point you thought was frictionless.
This is not failure data. This is the gauge working correctly. The loop is operating. The setpoint is revealed as aspirational, not actual — and now you know what to adjust.
The builder who avoids this moment is not protecting their idea. They are disabling the gauge. The loop runs on — confident, compounding, wrong.
The Instrument Principle
Good instruments are built before they are needed. A clinician who waits until the patient collapses to install a monitor has not managed the situation — they have reacted to it.
The leading reality signal in software is the person who uses it before it is ready. This is uncomfortable because it exposes gaps. That is the function. Gaps found early are adjustments. Gaps found late are failures.
The discipline is to build the instrument first, read the gauge faithfully, and resist the temptation to optimise the readout instead of the reality.
Three ways builders optimise the readout instead of the reality:
- Selective dogfooding — testing happy paths they already know work
- Metric substitution — using proxy metrics (velocity, coverage) when the true metric (customer outcome) is hard to measure
- Feedback delay — shipping, pausing, then coming back to customer response after the team has moved on
In each case the gauge is present but not reading. The loop looks healthy. The compound is heading somewhere nobody intended.
The Virtuous Version
The virtuous loop is not smarter. It is not faster. It reads the gauge faithfully and adjusts before the cost of being wrong compounds.
The setpoint serves beyond self. The gauge measures reality, not hope. The controller adjusts based on the delta — not based on what you wish the delta said.
That is the instrument. It is uncomfortable to run. It is the only one that compounds in the right direction.
Context
- VVFL Loop — The full three-loop model: runaway, corrective, virtuous
- The North Star — Setpoint discipline — what the gauge is reading toward
- Feedback Loops — How loops compound and what determines direction
- Decision Making — How reality signals become adjustments
- Culture Is the Moat — The north star as the only thing that survives a broken gauge
Links
- Deming — System of Profound Knowledge — Variation, measurement, and what it means to understand a process
- Don Norman — The Design of Everyday Things — Feedback as the fundamental mechanism of usable systems
Questions
If your gauge reads internal belief, who or what would need to change for it to read reality — and why has that not happened?
- What is the minimum leading reality signal — the smallest real reading — that would change what you are building right now?
- When a gauge reads what you hoped rather than what is true, how long does it take to notice — and what is the average cost of the delay?
- If the virtuous loop requires reading an uncomfortable gauge faithfully, what organisational conditions make that sustainable rather than heroic?