n o ren
Systems & Organizations

Your Data Hand‑off Is Killing Projects

When the Mars Climate Orbiter crashed, a single spreadsheet column missed a unit conversion, and the entire mission vanished.

The hidden culprit behind many stalled teams is the Information Bottleneck Law: every additional hand‑off in a workflow multiplies the chance of a critical distortion. The law works because each hand‑off adds a cognitive context switch, a formatting step, and a tacit assumption about meaning; any one of these can introduce error, and the probability compounds quickly. In 1999, NASA’s navigation team sent a trajectory file to the spacecraft operations group, but the file listed thrust in pound‑force while the receiving software expected newtons.

The mismatch went unnoticed through three layers of verification, and the orbiter entered the Martian atmosphere at the wrong angle, burning up. The mistake was not the engineers’ competence but the brittle chain of data translation that lacked a single source of truth. Teams that flatten these chains—by co‑locating owners, using shared schemas, and automating validation—see error rates collapse and velocity rise, because the same work no longer passes through opaque, manual filters.

The paradox is that adding “more documentation” often deepens the bottleneck, while a lean, automated contract between producers and consumers cuts distortion to near zero.

Every hand‑off adds a multiplicative risk of data distortion.
A single shared schema and automated validation turn a risky chain into a reliable pipeline.

Ignoring the bottleneck means a single typo can derail multi‑million‑dollar programs.

Over‑documenting without shared schema inflates hand‑off cost, slowing delivery and demotivating engineers.

1
Open the most recent design hand‑off document, locate the data schema version field, and verify that the producer and consumer sections list the same version number.
2
Run the automated schema‑validation script on the last three hand‑offs and count how many failed; zero failures means the bottleneck is under control.

The term “information bottleneck” originates from information theory, where it describes how compressing a signal inevitably loses details; in organizations the compression is manual re‑formatting. Studies of software defect injection show that each manual edit adds roughly a 5 % chance of error, confirming the exponential growth pattern.

The law also predicts diminishing returns from adding more reviewers; after a certain point, each extra reviewer contributes less error catching than the additional hand‑off risk they introduce, a phenomenon observed in code‑review studies at large tech firms.