Appeal to Tradition

In plain terms

"We've always done it this way." The appeal to tradition offers longevity as a reason on its own. Age becomes the argument, and whether the practice works never gets examined.

This one is not a clean error, and pretending otherwise would make for a lazy entry. A practice that has survived two centuries has survived something. Bad practices do get abandoned, sometimes. Age is a genuine signal of fitness, just a weak and noisy one.

The fallacy is not in counting that signal. It is in treating it as conclusive, or in using it to avoid looking at the practice at all.

Why it's fallacious

"Old, therefore good" has obvious counterexamples. Bloodletting lasted two thousand years. Lead plumbing outlived most of the institutions that installed it. Practices persist for many reasons other than working: habit, sunk cost, the interests of whoever benefits, and the plain absence of anyone with the standing to change them.

Survival evidence is also selection evidence, so it inherits every problem in survivorship bias. You see the traditions still standing. The ones that failed left no monument, and nobody counts them when tallying the wisdom of the ages.

The strongest version of the argument is Chesterton's fence: before removing a fence you don't understand, find out why it was built. That is a demand for investigation, not a defence of the fence. It stops working the moment it becomes a reason to stop asking.

Canonical example

"We've run the Monday all-hands at 8am for fifteen years. It's part of who we are." "Half the team is remote across three time zones now." "It's how we start the week here."

Fifteen years of the meeting is a fact about the calendar. The question on the table is whether the meeting still serves a team that no longer sits in one building. The tradition answer never touches the change that raised the question.

There may be a good case for the meeting: shared rhythm, a fixed point in the week, a habit that costs little to keep. None of it was offered. Age was offered instead, and age is not a mechanism.

Counter-example (not a fallacy)

"This release process has run for thirty years, through four management teams and about two thousand builds. Before we replace it, I want to know which failure it was protecting against. I doubt it survived that long by accident."

Not an appeal to tradition. It treats age as weak evidence of fitness and as a prompt to investigate, then asks for the mechanism. That is Chesterton's fence used properly, and it is ordinary good engineering practice.

The related idea, sometimes called the Lindy effect, holds that for things which do not age biologically, past survival predicts further survival. It is a real observation with real limits: it performs badly when the environment changes, which is exactly the moment people invoke tradition hardest.

The line: is the age of the practice a reason to look closer, or a reason to stop looking?

How to fix it

If you've been linked here, convert the history into a mechanism. Say what the practice does, what it prevents, or what broke the last time someone tried the alternative. "We tried the other way in 2019 and it cost us two weeks" is a far stronger sentence than "this is how we do things," and it is usually available, because long-standing practices tend to have stories attached. If you go looking and find no reason at all, that is worth knowing too.

If you're on the receiving end, treat age as a hypothesis rather than a punchline. Ask what the practice was for. People defending traditions often know something they have never put into words, and understanding it is the fastest route to changing the practice. Waving it away as "just tradition" is the mirror error, and it is how organisations delete safeguards they later have to reinvent.