“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.
The root cause varies. 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.
Other times it is 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 sometimes 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.
Sometimes 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.