“That’s just how we’ve always done it.”
How often have you heard this reply after asking someone why they perform a function? It is a familiar reply. It sounds harmless. Perhaps even reasonable. Yet it is one of the clearest red flags a leader can encounter.
A team member spends 20 minutes each morning generating a report in a specific format. When asked why, they shrug. No one on the receiving end has opened it in months. No one remembers who requested it or when it became routine.
But beneath that familiar reply often lies circular thinking, passive execution, and unexamined habits. In most cases, it is not the task itself that is broken. It is the lack of clarity behind it.
That kind of answer is rarely a root cause. More often, it is a symptom. And when you start pulling on that thread, you might find a deeper cultural issue, one that quietly slows teams down and limits performance.
A team member manually copies data between two systems every day, even though both systems support file imports and exports. When asked why they do not automate it, they pause: “I’m not sure. That’s just how I was shown.”
Sometimes, familiar answers reveal deeper problems.
When Familiarity Becomes a Liability
Routine is not inherently bad. Consistent processes reduce errors, lower training costs, and create predictability. The problem is not that people follow established ways of working. The problem is when those ways of working are never examined, never questioned, and never connected to outcomes.
A process that made sense three years ago may no longer fit the tools, team, or goals of today. Markets shift. Technology changes. Organizations restructure. Yet the process often outlives the conditions that created it, running quietly in the background while the world it was designed for no longer exists.
The phrase “we have always done it this way” is not just a description of habit. It is a signal that a process has become disconnected from its purpose. And a process without a clear purpose is not neutral. It consumes time, creates drag, and in some cases, actively prevents better approaches from taking hold.
Leaders who tolerate this signal without investigating it are not preserving stability. They are allowing drift. The cost is rarely visible in a single instance, but it accumulates across teams, departments, and years into a meaningful drag on performance.
What a Healthy Culture Does Instead
Organizations that avoid this trap share a common trait: they treat process review as a normal part of operations, not as a sign that something has gone wrong. Questions about why things are done a certain way are welcomed, not deflected. Employees at every level understand not just what they do but what their work is meant to achieve.
This does not require a formal continuous improvement program or a dedicated team. It requires a management habit. Leaders who regularly ask “what is this for?” and “does this still make sense?” create an environment where those questions become second nature across the organization.
The practical mechanics are straightforward. Regular one-on-ones that include a standing question about friction or redundancy. Onboarding processes that explain outcomes, not just steps. Team meetings that occasionally zoom out from execution to examine whether the work being done is the right work. None of these require significant investment. They require intention.
Why It Happens
The root cause varies.
Organizations often underestimate the difference between training people on a task and educating them on an outcome. A task-focused employee can perform a process exactly as taught. An outcome-focused employee can recognize when the process itself no longer serves its purpose. The first follows instructions. The second contributes to improvement. The distinction may seem subtle, but over time it has a significant impact on an organization’s capacity to correct course.
Sometimes it began at onboarding: the employee learned the steps but never understood what the task was actually for. Without that context, they go through the motions rather than contribute as informed team members.
Other times it is a knowledge gap. The employee knows their task exists within a larger process, but has never seen how their work connects to the outcome. They cannot spot problems upstream or suggest improvements downstream because no one showed them the whole picture.
It may also be a management issue. No one reviewed the training or confirmed it landed. No one followed up afterward. The manager may not have realized there was a gap, or may not have addressed it if they did.
And occasionally the problem runs all the way up to leadership. The culture does not encourage questions. It values execution over understanding and rewards routine over critical thinking. In other cases, the culture may be well-intended, but was never clearly communicated or reinforced.
None of this is irreversible. Once spotted, these issues are straightforward to address.
The starting point is awareness. Leaders who actively listen for phrases like “that is just how we do it” or “I was told to do it this way” are already ahead. Those phrases are invitations to dig deeper, not dismissals to accept. A single follow-up question, asked with genuine curiosity rather than criticism, often surfaces more useful information than a formal process audit.
Often, all it takes is a better question. Asking “What outcome is this meant to support?” or “Why is this step necessary?” can open the door to conversations that routine rarely invites.
More context, better onboarding, smarter training, and regular check-ins can all make a meaningful difference. A few simple shifts can turn passive task-doers into engaged problem-solvers. That obsolete morning report? A single conversation about outcomes could have ended it months ago. And when people understand why they do something, not just how, the difference becomes visible in morale, in quality, and in outcomes.
Managers and leaders need to reject “We’ve always done it this way” as a sufficient answer. They must question the habit, clarify the reasoning, and confirm the process still serves a purpose.
Because answers like that are not the end of the conversation. They are the start of a better one.