Zawinski’s Law

Jamie Zawinski's observation that 'every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can.' More broadly: software (and organizations, and products) inevitably accumulates features until it becomes bloated, trying to be everything to everyone. Zawinski's Law describes feature creep as a gravitational force—not a design flaw but an emergent property of successful systems responding to user demands. Each individual feature addition seems reasonable; the cumulative effect is a system that does many things poorly rather than one thing well.

When to use it

When products, organizations, or processes have accumulated scope beyond their original purpose; when feature requests seem individually reasonable but collectively dilute the core value proposition; when designing product strategy and need to resist scope creep; when evaluating whether software or organizational bloat is undermining core effectiveness.

How it can help

Recognize Zawinski's Law as an ever-present force and build active countermeasures. Product discipline means saying no to features that seem individually reasonable but collectively bloat the product. The test: does this feature serve our CORE use case, or is it expanding our scope toward 'reading mail'? Organizational version: does this initiative serve our core mission, or are we expanding to justify our existence? The countermeasure is active pruning—regularly removing features, programs, and initiatives rather than only adding them.