Fortune #49

Mars Climate Orbiter traveled for nine months to study the Martian atmosphere, but disappeared during orbital insertion in September 1999. An investigation found a cause that seemed small beside the size of the mission: one software component supplied force data in English units while the navigation system expected metric units.

The mismatch accumulated through multiple trajectory corrections. The team misjudged the spacecraft's path and sent it too close to Mars. The report did not stop at blaming the person who used the wrong unit. It identified failures in handoffs, checking, and communication between teams. Warning signs had appeared along the way, but the work system did not elevate them into a timely correction.

That is why names, dates, amounts, units, and attachments are not trivial details. One field may flow through many people and systems. When everyone assumes someone else has checked it, a small gap becomes a large failure point. A second reader or an automated format check does not announce distrust. It gives trust a supporting structure.

Before sending important work, use a review pass separate from the creation pass. Read backward, check recipient, date, amount, unit, and attachment, and when possible ask someone who did not create it to look. If you catch a near miss, add it to the checklist instead of attacking yourself. A detail cared for today is a larger problem that does not have to exist tomorrow.