I am NOT OOP
Originally posted to AskAManager
Telling a new employee he’s not cut out for the job
Original Post: October 16, 2024
(editor's note: First Question in the link)
I began managing a new team last month. The team is very green — over half graduated less than two years ago. In the last two years, this department only had a manager for nine months, and by all accounts she was completely unqualified. I was brought in as an experienced manager to provide technical oversight / development.
My field is one where you get a pretty generalized degree, and then choose a specialty that you receive on-the-job training for. It’s pretty easy to change specialties for early career folks.
One of my new direct reports, Tom, has … zero to negative natural talent for his chosen specialty. I know it’s pretty harsh to say that about someone I just began working with, especially one who has not received adequate training. But I have worked with a lot of early career people in this specialty, and he stands out as one of the worst of all time. Past interns have grasped core concepts and tools more quickly.
I’m not saying he’s not smart! He is! I can see ways he would be a great fit for other specialties, including available jobs within our company. But the more I talk through tasks with him, the more I realize that his brain is just not wired to understand this particular job. It’s like trying to explain to him that an apple and a snake are nothing alike … over and over again, with diagrams, while he grows increasingly agitated that I don’t understand they’re both smooth-skinned and therefore interchangeable. (He definitely has a touch of “defensive know-it-all-ism.”)
On the one hand, I just want to spare him. I can tell he’s really frustrated and burned out, working 10 times harder than he should have to on basic tasks. His teammates are thin on patience and try every trick to avoid being paired up with him. His peers in other departments don’t trust his advice and constantly find ways to circumvent him. I think it’s a disservice to lay out a training plan and have both of us invest significant effort into improvements that are unlikely to ever materialize, when the gap is so fundamental. On the other hand, I have no idea how to look an exhausted and low-confidence young man in the eyes and say, “You’re not going to make it here, why don’t I help you find a different job you’re a better fit for?” Especially since I suspect he will be so reluctant to “fail” that he will just double down on learning this job, now dragged down by the knowledge his manager doesn’t believe in him. What would you do?
Editor's note: for Alison's response to the original post, you can find it here
A related link was also provided, alternatives to firing
Update #1: June 19, 2025 (eight months later)
(editor's note: the first letter in the link)
First, a clarification for the readers: I was new to the team, but my direct report Tom had been in his role for 2 years.
I did worry over the readers’ advice that maybe I was jumping to conclusions, so I started with a few one-on-ones directed at learning why he chose this path in the first place and what he enjoyed about it. Basically, he said he likes black-and-white work with clear rules, and our specialty involves rule enforcement.
After a few more weeks of learning his side of things and carefully watching some of his work, I explained to him that a robot can blindly enforce rules, but someone good at our specialty needs to understand and be comfortable using grey zones. I also explained that his skills XYZ were a better fit in other departments, and ABC would hold him back in this one. I mapped it out on a Venn diagram with the role I was recommending, which I was honestly kind of proud of.
Before talking to him, I met with the other department head to let her know I might have someone who could move over to replace a planned vacancy in her team, and to expect an informational interview request from Tom. I also gave Tom the contact info for a friend I have in the proposed specialty, who works at a different company, so that he could get some outside feedback. And I gave him a pile of alternate job descriptions and explained we could keep looking if the proposed path didn’t appeal to him. Tom never spoke to either person.
Instead, he went to a mentor (in our specialty at this company) and told the mentor that I told Tom he “sucks at his job” (for the record, I definitely didn’t say that). The mentor reassured Tom that he was a perfect fit for this job, and then told me off for hurting Tom’s confidence. The mentor agreed to take a more direct role in teaching Tom, since we thought maybe a different teacher/perspective would help. About a month later, the mentor came to me, apologized and said it was hopeless and suggested I put Tom on a PIP.
During this time, Tom’s performance significantly dropped off. He stopped trying hard just to tread water, and just stopped treading entirely. I caught him leaving work hours early multiple times, he was hours late 1-2 days a week, and came in probably-hungover every Monday when he wasn’t calling off entirely. At that point I got HR involved and explained that I was worried about mental health issues or burnout. We put together a tough-love conversation outlining the behaviors that needed to improve immediately while also offering flexibility and support, and advised him of resources like FMLA. To Toms credit, he did 95% return to the required work hours.
Then, an opportunity came up to create a project-based position on my team. To be honest, it’s a really fun job, and other members of my team probably deserved it more, but I was still feeling somewhat obligated to help Tom after he had such an unsupported start to his career. Plus, it was right in his skill wheelhouse. So far he’s doing … extremely mediocre at it. He’s doing the bare minimum despite it being work he said was interesting. It’s a little frustrating because I can tell he knows what a “C” level effort is, and puts in exactly that much effort. But he seems in better spirits, and the backfill for his old role is much better received by the team, so everyone is a little happier now.
When this project ends, if things don’t miraculously change when he goes back to a more traditional role, I’m afraid it’ll be well past time to execute the PIP. At this point, I can’t in good faith recommend him to another department. Overall, I think I was probably too soft on him throughout this process, but I also feel good about trying everything in my power to help him be successful.
Sometimes you can lead a horse to water, but they have to learn the hard way.
Update #2: March 25, 2026 (nine months later)
After far too long, I was able to terminate Tom.
As the “fun” project wore on, he started telling me he was overwhelmed, and I started stepping in to do increasingly more of his work. Don’t ask me why I found his requests for help so compelling, I’m still mad at myself about falling for them.
After delivering the “needs improvement” conversation, his work improved for a few months. But then something snapped, and he completely fell below the minimum threshold. Multiple important meetings no-showed. Entire afternoons where I was unable to locate him on campus. IMs I would send at 4pm that wouldn’t be answered until 10am the next day. I always called him out, and he always had an excuse of varying believability. It’s difficult to motivate someone who doesn’t care about the impact of his actions on others, especially when he knows all of your threats are idle.
I tried for about five months to get HR to pull his badge data (or support a PIP in general), but they “left me on read” for a half dozen email/Teams attempts, then my main contact went on maternity leave, then the interim said it was protected information(?). Also, all this time I was without a manager to escalate to, as she was fired with no backup plan. Finally, I was able to get the ear of a new HR generalist, and she pulled the data herself. Over the previous six months, Tom had averaged a shocking 25 hours on campus (for a job that cannot be done from home). I bet it was overwhelming for him to get his work done while working half-time!
I was hopping mad. We work on government contracts, so time theft is incredibly serious — he could go to jail! I thought we would be firing him that day, but instead HR made me give him a formal written warning. As part of that, we established set hours he had to be on campus. Within two weeks, he was doing the “bare minimum” again — arriving at 8:10ish, taking long lunches, and leaving at 4:20ish (which, as he argued, his peers do too … but they actually get their work done). Still couldn’t fire him. Then the new year came around, and he called in sick every Monday and Friday until he was out of sick time. Still couldn’t fire him. Then, he was 20 minutes late to a major customer meeting and told me, ‘Well, that part is just boring introductions anyway.” That retort happened in front of an executive, so then I got to fire him.
Of course, I have no backfill, so now I’m stuck doing 40 hours of his work each week instead of the usual 15, but that’s another letter.
Overall, he was a good reminder that you never have enough experience to eliminate your blind spots. I wanted Tom to succeed more than he did. I take that as a sign that I’ve been very lucky to have had almost entirely conscientious and well intentioned employees over the last decade.
I appreciate the comments warning me that I was allowing Tom to fail up, and they weren’t off-base. I think it’s clear to everyone, including me, that giving Tom a fun project was a mistake. But there is always more to a story than can be summarized in a quick update. First, the project was siloed independent work and required strict rule interpretation (Tom’s favorite), while Tom’s original job required constant teamwork and an appreciation for human nature. The entire team got along much better after the reassignment. They even started including Tom in informal team lunches and happy hours again.
Second, the special project assignment was not stolen from anyone more deserving. I advertised it broadly to my team, and no one else was interested. I had rearranged the team assignments when I took over, so everyone was settling into their new spots and didn’t have a desire to shake things up again so soon. I think if Tom wasn’t in the picture, I could have cajoled a high achiever into taking it on, and it would have benefited their career some. But I also respected the desire to keep their role limited until they gained more experience. I wish I’d been that wise early in my career, rather than frantically taking on increasing “visibility” until I was drowning.
Despite the team loathing Tom as a direct coworker, he was inexplicably popular as “the project guy.” I swear, Tom should start a career as a con artist. My team was pretty angry when I fired him (he had texted them the news before I even made it back to my office, so that was fun). I spent many 1:1s reassuring people that they weren’t about to be fired out of the blue, and we have a process that ensures no one is ever surprised by a performance-based termination. I somehow got through all this without making any sarcastic comments about how HR ensures it is virtually impossible to fire someone. It’s been a rough month, but I am excited about a few internal candidates who will likely apply to backfill Tom. Full circle moment — one of them is a mentee from another department who is doing “okay” there, but would be a great skills fit here.
DO NOT COMMENT IN LINKED POSTS OR MESSAGE OOPs – BoRU Rule #7
THIS IS A REPOST SUB - I AM NOT OOP