He knows when he plans to retire. He has not said it. The team builds project plans around a date that nobody has confirmed. You are managing around a gap that does not exist on any calendar.
What Happens
- He mentions retirement in passing but never names a year, let alone a month.
- The team either over-plans for his absence or ignores the question entirely. Either way, the planning is wrong.
- Nobody asks him directly. “Are you going to be here for the launch?” is as close as anyone gets.
- After he announces, he gets dropped from meetings. Decisions move forward without him.
- Knowledge transfer becomes the only thing anyone wants from him. He goes from colleague to source material.
- HR sends a checklist. He fills it in. Nobody asks what the job meant to him.
Why It Happens
Announcing retirement means saying the career ends. He knows this. Naming the date makes it real, so he keeps the date vague. This connects directly to Legacy Consciousness: he still has things to build. Stepping back before the ending is written feels wrong.
There is also Fear of Change. A fixed date turns a distant future into a deadline. Once it is spoken, the outcome is fixed. He prefers the date to stay open.
The question “when are you retiring?” sounds like “when are you finally leaving?” He reads the subtext even when it is not there. His Need for Relevance makes the question feel like pressure. So he deflects.
If he has spent years as The Expert on the team, announcing means handing that role away. He is not ready. The Desire for Stability keeps him holding the position even when he knows the time is near.
After the announcement, things move fast. Meetings he used to lead happen without him. Knowledge transfer sessions replace real work. He knew this would happen. Fear of Vulnerability is part of why he waited.
What You Can Do
Ask about plans, not dates. “What do you want to build in your last year here?” opens a different conversation than “when are you leaving?” It asks about his work, not his exit date.
Frame the announcement conversation around what he wants to leave behind. Sit down privately before any formal step. Ask which projects matter to him and who he wants to develop. The answer includes the date.
Keep him on real work. Drop him from a project after the announcement and you confirm the fear that the end has already started. He should own real deliverables until the final month. A handover month at the end is enough for most roles.
Agree together on what he owns until the end. Write it down. A clear scope protects him from being sidelined and protects the team from planning blind.
Quick Tip
In the first meeting after his announcement, assign him something with a real deadline. One concrete task signals the team still counts on him. It takes two minutes and prevents the slow fade.
Tell him directly what you need from him, and when. “We need you on the client renewal through October. After that, we plan the handover together.” That sentence gives him a role and a shared timeline.
See also: Supporting Retirement Transitions