McBryan's Law

principle

Improvement needs an object to act on. A flawed working version exposes real defects; an imagined perfect version exposes nothing.

The spacecraft-design lesson is blunt: “You can’t make it better until you make it work.” That reverses the instinct to perfect a design before exposing it to reality.

E1

Reality must get a vote

Before something works, its weaknesses are predictions. Once it works—even crudely—its failures become observable: a component breaks, an assumption collides with a constraint, or a result falls short. That working baseline turns improvement from speculation into diagnosis. This is the operational core of Perfect Is the Enemy of Good: the rough version creates the feedback that polish requires. It also explains why executing a usable plan reveals information that more planning cannot. When performance can be observed repeatedly, measurement can identify which defect deserves the next iteration.

E1

Working is not the same as safe

McBryan’s Law does not license careless deployment. Where a first failure could cause irreversible harm, “make it work” may need to happen in a simulation, prototype, test environment, or tightly bounded trial. Nor should the baseline become an excuse to stop: rising standards can be useful when they direct attention to consequential defects rather than endless cosmetic refinement.

Define the first observable run

Choose one stalled project and specify the smallest version that can complete its core function once. Build that version, run it, and record the single failure that most obstructs the result—then fix that failure before adding features.

Episodes that teach this