Every engineering organization has heard the phrase:
> We've always done it this way.
Sometimes it is true. Sometimes it is even the right answer. But it is almost never a sufficient explanation.
Hidden inside that sentence is an assumption that deserves inspection.
No deployment process, architecture pattern, or approval rule appeared fully formed.
Someone made a decision. Someone accepted a tradeoff. Someone believed the benefits outweighed the costs.
Over time, the decision became habit. The habit became policy. The policy became culture. Eventually people forgot why it existed.
A company may have introduced weekend change windows when deployments were manual and rollback required restoring backups.
Years later, it may have continuous deployment, feature flags, immutable infrastructure, and automated rollback. The weekend change window remains.
The process survived. The assumptions did not.
Old approval chains, legacy review meetings, outdated controls, and permanent exceptions are organizational fossils.
They are evidence of earlier engineering realities.
The problem is not that they exist. The problem is treating artifacts of history as laws of nature.
A long-standing practice should preserve its original objective, assumptions, evidence, review date, and retirement conditions.
Then "we've always done it this way" can become:
> We continue doing this because the original reasoning still matches today's reality.
That is a completely different statement.