Imagine a support engineer who has just found the fault behind a customer’s recurring outage. Give her a stubborn problem and two uninterrupted hours, and she will follow the evidence long after others have run out of ideas. Ask her to coordinate five people during a live incident, and she keeps disappearing from the call to investigate. The customer waits for updates. Her colleagues quietly take over.
Her manager promoted her to incident lead because she was the best troubleshooter on the team. Six months later, he is still telling her, “You’re doing fine.” She knows she isn’t. The considerate thing would have been to tell her the truth months ago. There may still be time to find her a better role. If there is no such role in this organization, letting her go may be kinder than asking her to spend another year trying to become someone she has no wish to be.
What would you keep doing if nobody asked?
There is a useful intuition behind the question “What would you do even without pay?” Think of the technician who gets the machine running, goes home, and still wants to know why the bearing failed. That second question is a clue. Curiosity can carry a person into the less glamorous practice that makes them good: reading the manual, trying another explanation, learning from someone who spotted what they missed.
Use the question for reflection. Never turn it into an expectation of unpaid work. A parent who closes the laptop promptly can love the craft as much as a colleague who spends the evening on it. People also perform difficult work exceptionally well out of duty, discipline or pride, even when they dislike it. A review of 74 studies found a modest overall relationship between vocational interests and job performance. That gives a manager a reason to ask about interests. It gives no basis for assuming an unhappy employee is mediocre. Van Iddekinge and colleagues, Journal of Applied Psychology.
Ask a question the employee can answer from experience: “Looking at last week, which assignment would you gladly take again? Which one would you give away? What made the difference?” Listen closely. “I hate incident calls because nobody lets me make a decision” points to an authority problem the manager can fix. “Even when I have the authority, I want to be the one diagnosing the fault” points somewhere else.
Give the job and the person a fair test
The manager owes the engineer an account of what he has seen: “In our last two incidents, we went past the agreed time for a customer update while you investigated. I should have raised this after the first one. The lead needs to assign the investigation and stay available to coordinate the response. Do you want to do that work? What am I missing?” Then let her answer, including the possibility that he has his facts wrong.
If she wants to lead, agree on a test that resembles the job. In this example, she could lead two rehearsals with a designated troubleshooter and clear authority to direct the team. Then review one live incident together. Did the customer receive the agreed updates? Did each responder know who owned the next action? Set the review date now. Judge her by the same job requirements used for anyone else in the role. A different communication style or an absence of visible enthusiasm tells you little about whether the customer got what was promised.
If she is meeting those requirements and says she wants to stay, take her answer seriously. A manager’s theory that she would be happier elsewhere is a poor reason to fire her. And if the manager removed the technical career path when he promoted her, he should own his part in the mismatch. Ask whether an actual specialist vacancy exists, what it pays, and whether she wants it. She deserves a real choice with real terms.
Know when another month serves only the manager
Suppose the tests are complete. The engineer still takes over the diagnosis, essential updates still go missing, and the company has no specialist vacancy. What would another month establish? If the honest answer is “nothing,” delay buys the manager relief from one uncomfortable conversation. The engineer pays for it in repeated public struggles. Her colleagues pay for it each time they cover the same gap. And she spends another month being assessed on the work she does least well, while the work she does best becomes a smaller part of her record.
That is the case for separation. The manager can decide what the organization requires and whether this employee is delivering it. Only the employee can decide what kind of future she wants. Losing a paycheck is an immediate cost. A better next job is a possibility. Compassion means facing both facts without asking the employee to be grateful.
Say it plainly, and offer help she can use
A private conversation can be brief: “We’ve decided to end your employment. This role requires someone to direct the response and keep the customer informed during incidents. We discussed those requirements and reviewed the results together. We don’t have a specialist opening to offer you. I know this is difficult news.” Pause. Give her time and the practical information she needs about the transition.
Then make any offer of help specific and credible: “If it would be useful, I can give you a reference about your diagnostic work. I can describe how you isolated that recurring fault and how you verified the repair.” Let her decide whether to use it. A truthful account of something she did well is worth more than a prediction that everything will work out.
This applies the Mission First practice from The Vitaver Playbook. Leadership owes the employee an honest judgment while there is still time to act on it. Sometimes the most compassionate investment is coaching. Sometimes it is a transfer. And sometimes it is the courage to stop asking a capable person to fail at the wrong job.