There are certain sentences that appear so frequently in organizational life that people stop hearing them.
They pass through meetings unnoticed. They appear in planning discussions, committee conversations, and board reports without attracting much attention. Most of the time they are spoken casually, almost as background information. Nobody regards them as controversial. In fact, they often arrive carrying a sense of reassurance. The sentence suggests continuity, experience, and institutional memory. It implies that whatever is being discussed has survived long enough to become established.
The sentence is simple.
“We’ve always done it this way.”
I’ve become interested in that phrase because it rarely appears where people think it does. Most organizations assume it represents resistance to change. Occasionally it does. More often, however, it reflects something else entirely. It reflects the gradual accumulation of decisions that were never revisited because they stopped feeling like decisions.
That distinction matters.
When people hear “We’ve always done it this way,” they often imagine someone actively defending a process, program, or tradition. Sometimes that happens. Yet many of the examples I encounter are less deliberate than that. The people involved are not protecting the status quo. They simply inherited it. The program existed before they arrived. The committee was already meeting. The report was already being produced. The annual event was already scheduled. What began as a decision years ago has gradually transformed into a fact of organizational life.
Like many things in organizations, this happens slowly enough that nobody notices.
A program is created to address a particular need. A process is introduced to solve a particular problem. A committee is formed to respond to a particular circumstance. At the time, the decision often makes perfect sense. People identify a challenge and develop a reasonable response. There is nothing inherently problematic about that. In fact, organizations depend upon these decisions to function.
The interesting part comes later.
Years pass. Staff change. Board members rotate. Leadership evolves. The environment around the organization shifts in ways both subtle and significant. Audiences change. Technology changes. Funding structures change. Expectations change. The organization itself changes. Yet many of the systems created in response to an earlier reality remain exactly where they are.
Some continue to serve an important purpose.
Some do not.
The challenge is that the distinction is not always obvious from the inside.
I occasionally ask organizations a question that seems simple enough on the surface: if you were creating this organization today, would you build it this way? The response is often revealing. People laugh. They pause. They look around the room. Eventually someone says what everyone appears to be thinking.
“Probably not.”
That answer should not necessarily alarm anyone.
Organizations are not supposed to remain frozen in time. They are living systems responding to changing circumstances. It would be surprising if a structure designed twenty years ago remained perfectly suited to today’s environment. The more interesting question is why organizations find it so difficult to examine those inherited decisions once they become established.
Part of the answer, I suspect, is that history carries a certain authority.
The longer something has existed, the more legitimate it appears. A process that has survived for a decade feels important simply because it has survived for a decade. People naturally assume there must be a reason. After all, surely someone would have questioned it by now if it no longer served a purpose.
Unfortunately, organizations are quite capable of carrying outdated practices for remarkably long periods of time.
Not because people are inattentive.
Not because people lack intelligence.
Simply because organizational attention tends to focus on immediate challenges. New issues arrive constantly. New demands emerge. New opportunities compete for consideration. Under those conditions, examining long-standing assumptions can feel less urgent than responding to whatever arrived in the inbox this morning.
As a result, organizations often become experts at addition.
New programs are added.
New responsibilities are added.
New reporting requirements are added.
New committees are added.
Far less energy is devoted to subtraction.
This tendency produces an interesting effect over time. Organizations begin to resemble old houses that have been renovated repeatedly by different owners. Each addition made sense when it was built. A wall moved here. An extra room appeared there. A hallway was extended to accommodate a need that seemed pressing at the time. Decades later, the structure still functions, but it contains traces of decisions made in response to circumstances that no longer exist.
Nobody intentionally designed the final result.
It emerged through accumulation.
Organizational complexity often develops in exactly the same way.
This is one reason strategic planning can feel unexpectedly emotional. People assume they are discussing the future. Frequently they are also discussing the past. Programs have histories attached to them. Committees have histories attached to them. Processes have histories attached to them. The conversation is no longer simply about efficiency or effectiveness. It becomes connected to relationships, effort, identity, and institutional memory.
Understandably, people hesitate.
Questioning a long-standing practice can feel like questioning the people who created it. Suggesting that something may no longer serve a purpose can sound uncomfortably close to suggesting it never had one. Those are very different statements, but organizations do not always distinguish between them.
What gets lost in the process is curiosity.
The healthiest organizations I encounter are not necessarily the most innovative organizations. They are often the most curious ones. They remain willing to ask why. They periodically revisit assumptions. They examine long-standing practices with the same attention they would give to a brand-new proposal. They recognize that a decision can have been completely appropriate at one moment in time and entirely misaligned with present circumstances.
That recognition requires a certain humility.
It asks organizations to acknowledge that previous decisions were made by intelligent people responding to the information available at the time. It also asks them to acknowledge that circumstances have changed. Neither conclusion diminishes the other.
In fact, they can comfortably coexist.
A committee may have been exactly what the organization needed ten years ago and entirely unnecessary today. A reporting structure may have solved an important problem in the past while creating new difficulties in the present. A program may have achieved everything it was intended to achieve and still be ready to conclude. None of these outcomes represent failure. They simply reflect the reality that organizations evolve.
What fascinates me is how often strategic conversations become easier once people accept this.
The goal is not to defend every historical decision.
Nor is it to abandon tradition for the sake of appearing modern.
The goal is to understand which inherited choices continue to serve the organization and which have quietly drifted beyond their useful life. That work requires reflection rather than reaction. It requires people to become interested in the origins of things rather than merely their existence.
Perhaps that is why the sentence “We’ve always done it this way” deserves more attention than it usually receives.
Not because it is always wrong.
Sometimes the reason something has always been done a particular way is that it continues to work remarkably well.
The danger appears when the sentence ends the conversation rather than beginning it.
Once history becomes justification in itself, curiosity tends to disappear. Decisions stop being examined. Assumptions stop being tested. Habit gradually replaces intention.
And while habit can be useful in many parts of life, it is a surprisingly fragile foundation for strategy.
Strategy asks organizations to decide deliberately. Habit asks them not to decide at all.
The two can look remarkably similar from a distance.
Up close, they lead in very different directions.