The most dangerous phrase in enterprise technology is not a technical one. It does not involve architecture patterns or deployment models or governance frameworks. It involves six words that can stop a transformation programme, preserve a failing system for another decade, or prevent the adoption of an approach that would solve a problem the organisation has been struggling with for years.
"We've always done it."
What follows those six words varies: this way, like this, with this vendor, through this committee. The specific completion changes. The function is consistent: to close off the examination of an assumption by appealing to historical practice as evidence of validity.
How It Is Actually Used
The phrase is almost never deployed as deliberate obstruction. The people who use it believe it. They have worked a certain way for a long time, the approach has not produced catastrophic failures, and the implied logic is sound: if this approach had been seriously wrong, something bad would have happened by now. The absence of disaster is taken as evidence of correctness.
In a major European insurer, the argument against replacing a thirty-year-old commissions calculation system was not technical — the technical case was clear. It was historical. The system had never produced a wrong payment. It had never gone down at month-end. It had, in its way, worked. The fact that it required three specialists to maintain it, that no documentation of its logic existed, and that extending it took months rather than days — these were costs that had been normalised over decades. We've always done it this way. It's always been fine.
The phrase works because it carries an implicit claim about evidence — past performance as proof of suitability. The flaw in that logic is that "it has not failed yet" is not the same as "it is fit for purpose now or will be tomorrow."
What It Is Actually Protecting
When the phrase appears in a transformation discussion, it is usually protecting one of a small number of things. Familiarity — the comfort of a known approach, even if the known approach is not optimal. Expertise — someone's position as the authority on the current way of doing things, which a change would diminish. Accountability avoidance — the current approach has been approved; a change requires a new approval, a new owner, a new potential point of failure. Each of these is a human, understandable motivation. None of them is a technical argument.
How to Answer It
The direct counter — "we can't keep doing things this way" — rarely works, because it sounds like an attack on the person saying it. The more effective response is to separate the historical practice from its justification: not "we've always done it this way" but "why do we do it this way, and does that reason still apply?" The question forces the examination of the underlying assumption rather than the defence of the historical fact.
In most cases, the reason the practice was adopted made sense at the time. The question is whether the conditions that made it sensible still exist. If they do, the practice should continue. If they do not, the phrase "we've always done it this way" is not a reason to maintain it — it is simply a description of what happened to date.
The past is not evidence that the present is correctly designed. It is evidence that the present existed — which is a weaker claim than it is usually taken to be.
The organisations that change successfully are not those that dismiss history. They are those that examine it honestly, distinguish what was deliberately chosen from what was simply inherited, and ask — without defensiveness — whether it still applies.