Back to lens

Dimension 2

Error Correction

mistake -> learning -> system update

Every company makes mistakes. The useful question is what happens next.

The question is whether the mistake updates the system or gets renamed, explained away, and repeated until it becomes normal.

The Read

A mistake updating the system is tuition. A mistake repeating itself is operating debt.

Scale

Read the low end and high end as field position. The live pressure decides what the score means.

Score 1-3Problems surface quickly, ownership is clear, fixes change the workflow, and the lesson travels.
Score 4-6Visible problems get fixed, but protected work, political mistakes, or cross-team failures still linger.
Score 7-10Problems are hidden, normalized, explained away, or fixed locally without changing the larger system.

Signals

The tells you would expect to see when the read is close.

The same failure appears in different departments with different names.

Post-mortems produce documents but not changed behavior.

People are punished for surfacing problems before they become visible externally.

Customer complaints are treated as anecdotes instead of signal.

Data says one thing and incentives reward another.

The fix depends on one heroic person instead of the operating system.

Tape

Company tape gives the pattern something real to push against.

NetflixFast correction: Qwikster was reversed quickly and later pivots showed willingness to change under pressure.
AmazonFast correction: failed experiments can be killed while learning feeds new tools and systems.
NorthvoltSlow correction: production issues and capital commitments compounded until the correction window narrowed sharply.
BoeingSlow correction: safety and production failures revealed errors accumulated across many layers.

Use Today

How the read turns into a map, packet, or decision people can use.

Trace recurrenceLook for the same problem repeating under different names.
Separate blame from updateAsk whether the system changed or only the person responsible changed.
Build the loopDefine how future errors will be noticed, fixed, and remembered.