Part Two: When Expertise Suddenly Doesn't Count

What leaders owe people when change alters the value of hard-earned knowledge

Michael T. Neiss | The Wisdom Orchard

One of the easiest ways to lose good people during a change is to treat their experience as an obstacle.

A new system arrives. A new strategy is announced. Artificial intelligence begins doing in seconds what once took hours. The organization is excited about speed, efficiency and possibility.

Then someone who has spent twenty years learning the work asks a hard question.

Too often, the question is heard as resistance. It may be something else entirely. What sounds like resistance may be a person trying to understand whether the knowledge that made them valuable yesterday still matters today.

Change can reach deeper than a job description.

When leaders talk about change, we often describe tasks, roles and technology. Employees may be thinking about identity. They remember the years it took to learn which problems matter, which shortcuts are dangerous, which customers need a different approach, and which warning signs never appear on a dashboard. Their expertise is not simply a collection of facts. It is part of how they contribute and how they know they are useful.

Now imagine hearing that much of this work will be automated, standardized or moved elsewhere. Even when the decision is sensible, the message can land as: What you spent your career learning no longer counts. That is not a small adjustment. It can feel like a loss of standing, confidence and belonging.

I have worked with leaders and organizations for more than forty years. In every season of change, people have asked some version of the same questions: Do you still need what I know? Is there a place for me in what comes next? Will I be given a fair chance to learn? Those questions deserve more than a training link and a deadline.

Old expertise is not always obsolete Some knowledge does lose value. Leaders should be honest about that. Pretending nothing is changing only delays the conversation and weakens trust.

But organizations also make a costly mistake when they confuse a new tool with complete understanding of the work.

Technology can process information. It does not automatically carry the judgment earned by seeing consequences unfold over time. A new employee can learn a procedure. That does not mean the employee yet knows where the procedure breaks down. A model can offer an answer. That does not mean it understands the customer, the history or the human cost of being wrong.

Experienced people often hold the context that makes new capability safer and more useful. They know where the roots run beneath the ground.

The question is not whether we keep every old practice. We should not. The better question is: What wisdom must travel forward, even if the way we apply it changes?

Do not make people audition for their dignity. I have seen leaders introduce a major change and immediately sort people into two groups: those who are enthusiastic and those who are resistant. That is a poor diagnosis.

Enthusiasm is not the same as readiness. Concern is not the same as refusal. A person who raises a risk may be protecting the work. A person who is quiet may be deciding whether it is safe to speak. A person who asks what will happen to the team may be thinking like a leader.

If people must cheer for every announcement before they are allowed into the future, leaders will hear less truth precisely when they need more of it.

Respect does not require leaders to preserve every role or accept every objection. It requires us to tell the truth, listen carefully and separate the person from the practice that may need to change.