Approximate reading time: 5m 26s
How the phrase sounds in meetings, emails, and everyday decisions
"That's how we've always done it." Sometimes it is said directly. Sometimes it is wrapped in a softer form: "Let's not touch this, it works," "It will take too much time," "People are used to it." At first glance, this sounds like reasonable caution. In reality, it is often a signal of organizational inertia.
The phrase almost always appears in three situations: when someone proposes a process change, when a new tool is discussed, or when a model that used to be convenient but is no longer effective needs to be reconsidered. It rarely comes from bad intent. More often, it comes from fatigue, fear of making mistakes, lack of time, or the feeling that "it's safer this way."
The problem is that what is safe today may turn out to be expensive tomorrow.
Why "That's How We've Always Done It" kills learning agility
Learning agility is the ability to learn quickly from new situations, transfer experience into unfamiliar environments, and change behavior according to context. When this ability is missing, the organization begins to prefer repetition over development.
The phrase "That's how we've always done it" is dangerous not because it stops one specific proposal, but because it gradually teaches people not to propose anything. If every new attempt meets automatic resistance, the team starts to self-censor. Over time, the most active people stop raising their hands, and the most valuable ideas remain unspoken.
This is the moment when culture starts taking talent away instead of developing it.
Three hidden consequences
- Slower adaptation — processes become outdated, but no one changes them.
- Lower engagement — people feel that their opinion does not lead to action.
- Weaker development — there is no environment for experimentation, learning, and improvement.
How organizational culture becomes a barrier to AI readiness
AI readiness does not mean only having access to tools. It means having a culture in which people use them wisely, ask questions, verify results, and change processes when it makes sense. If the culture is "don't touch anything," AI implementation becomes formal — a bought license, a short training, and zero real change.
In many organizations, the barrier is not technological. The barrier is psychological. People are afraid that the new tool will make them redundant, expose weaknesses, or require extra effort without a clear benefit.
Here, the role of leaders is crucial. If management presents AI as a threat or as yet another "initiative from above," people will accept it passively. If it is connected to concrete problems — time, quality, errors, workload — resistance decreases.
Examples from banks, HR processes, and corporate teams
In a bank, it may look like this: the team handles the same documentation the old way, even though there is a tool for automatic data extraction. Someone proposes testing a new workflow, but the response is: "There is no point, we've always done it manually and it works." It works — but slowly, with strain, and with unnecessary risk of errors.
In HR, the situation is similar. Recruitment may rely too heavily on emails, manual spreadsheets, and duplicate steps, even though part of the coordination can be automated. Instead of freeing time for quality interviews and candidate work, the team remains in administration mode.
In a corporate team, we often see the following: the weekly meeting lasts 90 minutes, everyone reports their status, but no one asks whether the format is useful at all. "This is how we're used to doing it" becomes a substitute for analysis.
What the healthy alternative looks like
- "What task is this process solving?"
- "Which parts are habit, and which are real necessity?"
- "What would we gain if we simplified it?"
- "What is the smallest safe test we can run?"
The role of middle management in change management
Middle management is where change most often succeeds or dies. Leaders at this level are between strategy and day-to-day work. They feel the pressure to deliver results quickly, but they also see the real obstacles: lack of time, fatigue, old habits, and fear of additional complexity.
That is why their role is not simply to "pass on the message." They need to translate change into understandable actions. Not with slogans, but with specifics.
A good middle manager does not ask only, "Why didn't you do it?" They ask:
- "What is stopping you?"
- "What would make the change easier?"
- "Where exactly is the process too heavy?"
- "How can we test this without risking everything?"
This approach does not remove accountability. On the contrary, it makes it workable.
How to ask questions that open the conversation instead of closing it
If you want to change culture, start with language. One phrase can close a conversation in seconds. One question can open it.
Here is a practical model for a team conversation when someone says: "That's how we've always done it."
- Acknowledge the context — "I understand why this approach has worked so far."
- Shift the focus to the goal — "What result are we trying to achieve with it?"
- Check relevance — "Are the conditions today the same as they were two years ago?"
- Suggest a small test — "Can we try an alternative for one week?"
- Measure the effect — "How will we know whether the new approach is better?"
This is critical thinking in action. You are not arguing for the sake of arguing. You are not imposing change at any cost. You are simply refusing to accept habit as an argument.
Five signs that the culture is already stopping development
- New ideas are discussed, but rarely tested.
- Employees avoid suggesting improvements because "there is no point."
- Processes are defended with history, not results.
- Changes are seen as extra burden, not as a tool for better work.
- The team is better at explaining why something cannot be done than at finding how it can.
How HR can help without becoming the "fixer"
HR often ends up between business expectations and the real behavior of teams. If the approach is too general, change remains at the initiative level. If it is too intrusive, even more resistance is triggered.
A more useful approach is to work with concrete behaviors and micro-habits:
- selecting team leaders for learning agility, not only experience;
- training in change management and adaptive leadership;
- conversation scenarios for resistance to change;
- pilot projects with clear metrics;
- feedback that rewards experimentation and learning.
When HR and management speak the same language, change becomes less abstract and easier to accept.
How to turn resistance into a working conversation
Resistance is not always a problem that needs to be "broken." Sometimes it is a useful indicator that the change has not been explained well or that the risk is real. The point is to use it constructively.
Instead of asking, "Why are you against it?", try:
- "What is unclear about this approach?"
- "What risk do you see?"
- "What needs to be true for it to work?"
- "What would make the solution safe to try?"
This moves the conversation from defense to analysis. And that is the difference between stagnation and development.
FAQ
Why is the phrase "That's how we've always done it" a problem if the process works?
Because "works" does not always mean "works well." In a dynamic environment, a process that does not change gradually loses efficiency, even if it does not seem broken.
How do I challenge this phrase without conflict?
With questions, not accusations. Focus on the goal, the result, and the small test rather than defending a position.
What does this have to do with AI and the future of work?
AI and automation require a culture in which people are ready to change processes, learn new tools, and think critically. Without this, technologies are used superficially.
What is the most common mistake of middle management?
Assuming that resistance is a lack of willingness rather than a lack of clarity, safety, or meaning. In many cases, the problem is in the way change is introduced, not in the people.
How does real change begin?
With a small, measurable pilot. Not with a huge transformation on paper, but with a concrete process that can be tested, analyzed, and improved.
Conclusion
"That's how we've always done it" sounds convenient because it saves thinking. But that is exactly where the risk lies. In the age of AI, change, and higher expectations at work, it is not the most stubborn defenders of the status quo who win, but the people and teams who can adapt, learn, and change processes thoughtfully.
If you want the culture to move forward, start with better questions, smaller experiments, and leadership that does not defend habits, but results.
If this topic matters for your team, you can also review the main article on adaptability and learning in 2026, and we can discuss suitable change management, leadership, and AI readiness training for your organization. Sometimes a well-structured program is the shortest path from "this is how we're used to doing it" to "this is how we work better."