But we've always done it that way.
That has to be one of the most expensive sentences in modern business.
I've raged against it my entire career. Every time I've heard it, something productive was about to get strangled. A better process. A better tool. A better outcome. All of it killed by seven words that sound reasonable until you start adding up the cost.
And the funny thing about that sentence is that it does not protect excellence. It almost never does. In my experience, it protects inconvenience. It protects laziness. It protects the comfort of the people who built the current system and do not want to be the ones to change it. It protects nothing that actually matters to the business.
It is crazy to me that we spend so much energy at work protecting workflows that have no defense beyond their own age. A process is not good because it is old. A form is not valuable because it is familiar. A workflow does not earn its place by surviving long enough to become a tradition. Every one of those things has to earn its keep every single day. The moment it stops earning, it should go.
But that is not what happens. What happens is we protect the workflow, we defend the process, we keep the form, and we tell ourselves that the reason is tradition or consistency or some other word that sounds better than the real reason.
The real reason is usually that changing it would be hard.
It is not a statement. It is a confession.
And the funny thing I find at the end, the thing that actually made me stop in my tracks when I was walking today, is that the sentence itself is not even really a statement. It sounds like one. It has the cadence of one. But when you listen carefully to someone saying "we've always done it that way," what you are really hearing is a confession.
It is a confession that nobody has thought about this in a long time. It is a confession that the person saying it does not actually know why the process exists. It is a confession that the team is operating on autopilot and has been for years. It is a confession that there is no active defense of this workflow, only a passive defense rooted in habit.
A statement justifies something. A confession admits something.
"We've always done it that way" admits everything and justifies nothing.
The data on this is brutal
And the data on this is brutal.
McKinsey's research on large-scale transformations consistently finds that about 70 percent of them fail to meet their objectives. Think about that number for a second. Seven out of ten organizations that set out to change something meaningful end up back where they started, or worse. That is not a technology problem. That is not a budget problem. That is a cultural problem. That is a "we've always done it that way" problem showing up in the statistics.
The same research identifies the biggest reason these transformations fail, and it is not what most executives assume. It is not bad software. It is not insufficient funding. It is not poor project management. It is resistance. Specifically, it is the resistance of people inside the organization who are protecting their own existing workflows for reasons that have nothing to do with business performance.
And here is where it gets really expensive. The same McKinsey research breaks down the four pitfalls that most commonly sink a transformation. The first is setting aspirations based on consensus rather than facts. People pick a target that feels safe, not one that the business actually needs. The second is failing to attach a compelling reason that the people inside the organization can actually believe. The third is poor execution, driven in part by acting too slowly when it comes to hard people decisions. The fourth is failing to sustain the change after the initial push. Every one of those pitfalls has a "we've always done it that way" component baked into it. Every one of them is made worse by an organization that defaults to protecting the status quo.
So when you do the math on it, the cost is not theoretical. It is showing up in abandoned initiatives. It is showing up in stalled rollouts. It is showing up in competitive positions that erode quarter by quarter while the organization continues to protect workflows it has never stopped to question.
The real estate parallel
I see it constantly in real estate. The industry is full of processes that exist because they existed last year. Forms that exist because they existed last decade. Workflows that nobody actively chose. They just accumulated. They became the default. And now entire categories of agent frustration and client friction exist because nobody wants to be the one who questions the default.
Most of these workflows were designed for a world with different tools, different clients, and different expectations. The world has moved on. The workflows have not. And when someone suggests updating one, the response is almost always the same. "But we've always done it that way." The sentence does its job. The workflow survives another cycle. The tax on the business keeps running.
Questioning the default is not disrespect
Questioning the default is not disrespect. It is not disruption for its own sake. It is the most basic thing a serious operator can do. You look at a process. You ask what it is for. You ask whether it is still delivering value. You ask what it would look like if we were designing it today with modern tools. And then you make a decision based on those answers, not based on how long the process has been around.
The people who build the best companies are not necessarily the most innovative thinkers. Some of them are. But many of them are simply the operators who refuse to accept "we've always done it that way" as an answer to any question. They do not treat age as a credential. They do not treat familiarity as evidence. They evaluate every process on its current merits, and they keep the ones that earn their keep.
The follow-up question
If you are in a leadership position and someone on your team tells you "we've always done it that way," your follow-up question should always be the same. Why? Not in a combative way. In a genuinely curious way. Because the answer tells you everything you need to know about whether that workflow should survive another quarter.
If the person can give you a real reason rooted in business performance, you keep the workflow. You leave it alone. You move on to the next question.
If the person cannot give you a reason, or gives you a reason that amounts to "we just always have," you have identified a candidate for elimination. You have identified something that is costing the business something, even if you cannot quantify it exactly in the moment. Every process that exists without justification is a tax on the organization. It slows decisions. It ties up time. It blocks people who want to do things better from doing them better.
The compounding cost
And in a world where AI is compounding the advantage of companies that move fast, the tax on organizations that protect the status quo is getting bigger every month. Every workflow we keep out of tradition is a workflow that is not being rebuilt with the tools that are now available. Every hour someone spends defending a process that exists out of habit is an hour they are not spending building something that matters.
I am not saying change for the sake of change. That is its own trap. What I am saying is that the burden of proof should never rest on the person who wants to improve the process. The burden should rest on the person who wants to keep it the way it is. And if their only argument is that the process has been around for a long time, they have lost the argument before they started.
Listen to it differently
Next time you hear "we've always done it that way," listen to it the way it should be heard.
It is not a statement. It is a confession.
A confession that the speaker has not interrogated the process in years. A confession that there is no active reason, only inertia. A confession that the workflow under discussion has outlived its logic and is now being kept alive by habit. And like every confession, it is an opportunity. It is a chance for the organization to stop defending something it should not be defending, and to start building something that actually matches the world it operates in today.
The best operators I have worked with treat every instance of that sentence as a signal. It tells them exactly where to look. It tells them exactly which workflow to interrogate first. It tells them where the highest-leverage improvement is hiding. The sentence is not a wall. It is a map.
And the cost of ignoring that confession compounds every single day.
Judd Hoffman is CEO and Co-Founder of Ethica AI, building AI-powered tools for real estate transaction workflows.