Every Default Has an Author
A chapter revealing the intentional origin of familiar things, from buttons and forms to classrooms and professional profiles
Tracing the decision, belief and hidden assumption behind a system to understand why it exists and whether it still fits
Every default begins as a design decision
A design team debated a button position until someone asked why it had to be there. The room fell silent because nobody remembered the original reason; they were preserving a choice only because it had existed for a long time.
Repetition turns choices into defaults
Roads, forms, classrooms and professional profiles are all outcomes of human decisions. Repeated long enough, those decisions become defaults.
Defaults create stability and blindness
Defaults create stability and prevent us from rethinking everything each day. Yet they also make us forget that every process was once considered and chosen, leading us to confuse “designed” with “unchangeable.”
Every product reflects the beliefs of its creator
A complicated form may reflect the belief that more information creates more value. A long process may have been designed to reduce risk. Understanding the belief behind a design matters more than its surface.
Understand before criticizing or defending
Do not rush to condemn what exists; understand why it appeared. But do not defend something merely because it is familiar. Every generation inherits past designs and must leave better ones.
Look again at the systems in your own work
Ask what remains unchanged at work only because it has always been that way, what you would preserve if redesigning from scratch, and which assumption hides behind the current method.
Every default deserves review when conditions change
Every default began as a human decision. When conditions change, those decisions deserve to be reconsidered.
The next step is when familiarity becomes authority
The next chapter explores how familiarity starts to look like proof of correctness and becomes a form of invisible authority.