He says “we tried that in ‘94.” He doesn’t say what happened in ‘94. He doesn’t need to. In his view, the experiment closed the question. This is the Experience Shield pattern. His past experience is real knowledge. The task is making room for new approaches without dismissing what he knows.
Practical Techniques
Frame New as Continuation
Don’t present an innovation as a replacement for what he built. Present it as an addition.
Say: “Your process has handled this well for years. This new tool covers the part that always slips through.”
A replacement threatens. An addition extends.
Give Him the Problem First
Before presenting the solution, name the problem you are trying to solve. Let him respond.
Say: “We’re losing about two hours a week on the manual reconciliation. What would you try first?”
He has probably solved similar problems before. His solution and your solution can both fit.
Make His Knowledge Part of the New Approach
Ask him to review the new method for gaps. Ask him where it would have failed in ‘94.
Say: “What would have broken this approach back then?”
His critique improves the approach. He becomes a contributor instead of a blocker.
Why This Works
The Experience Shield goes up when he feels his knowledge is being discarded. These techniques keep his knowledge in play. He does not need to defend what is already being used.
Know When to Stop
If he raises a real concern about the new approach, take it seriously. Change for its own sake is not the goal. The better outcome is.
At Work
You pitch the new stack. He lists everything that went wrong since 2004. The room goes quiet. Dismiss the list and the migration hits the same problems again. That list is free risk analysis from the person who lived it. Assign him the risk register for the migration. He moves from critic to contributor. Say: “You know this system’s history. Which of these risks is real?”
More for the workplace: Men Over 50 at Work