Hofstadter's Law

"It always takes longer than you expect, even when you take into account Hofstadter's Law." Douglas Hofstadter stated this in Gödel, Escher, Bach (1979). The formulation is self-referential: the law predicts that your correction for the law will also be wrong. You add buffer; the work still overruns. The mechanism is not laziness or bad faith. Complexity compounds. Dependencies surface. Unknown unknowns become known unknowns, then known knowns — each step consuming more time than the optimistic case assumed. The law applies to projects, products, and decisions. Software ships late. Construction overruns. Mergers take longer to integrate than the deal team projected. The strategic move is not to "estimate better" in the abstract. It is to build the law into your process: pad explicitly, cut scope early, or use reference-class forecasts from similar past efforts instead of bottom-up optimism.

Short horizons hide the effect. A one-day task can finish on time. A six-month initiative almost never does. As the chain of dependencies lengthens, the variance of each link multiplies. One slip propagates. Hofstadter's Law is the name for that propagation when it systematically runs one direction — longer. Teams that have shipped before know the feeling: the last 10% takes half the project. The law explains why. That last 10% is where the hidden complexity lived. You only see it when you get there.