A Manager’s Priceless Lesson
Rahul sat at his desk, staring at yet another email complaint about Rajiv, his most challenging senior developer.
On paper, Rajiv was brilliant. But his attitude? It was becoming an absolute nightmare. He routinely dismissed feedback from his teammates, clashed with colleagues in meetings, and simply refused to take instructions.
This was the fourth complaint this month, and Rahul’s patience had officially run out.
He had already tried the standard management playbook: private feedback sessions, shifting him to independent projects, and even offering more perks. Nothing worked. It felt as though Rajiv had built an impenetrable wall around himself.
Time was running out. Critical project deadlines were slipping, and Rajiv had missed his milestones. Rahul knew he would ultimately be held accountable for his team’s shortcomings, and Rajiv was making his life incredibly difficult.
Yet, Rahul couldn’t deny the facts: Rajiv possessed extraordinary skills, even if his current output was suffering. Replacing top talent is both exhausting and expensive. Determined to find a way to make the partnership work before resorting to dismissal, Rahul rolled up his sleeves and decided to try a completely different approach.
The Silent Observation
Instead of stepping in to correct, control, or micromanage, Rahul decided to do something counter-intuitive for the first few days: he simply observed.
As he did, the dynamics in the room began to shift. Unfortunately, not for the better.
Rajiv, sensing he was already in deep trouble, expected a heavy-handed confrontation. When Rahul remained calm, the lack of a reaction made Rajiv incredibly uncomfortable. Braced for friction, he instead got an entire week of silence. In that vacuum—completely devoid of feedback—Rajiv’s anxiety spiked. He assumed the silence meant his job was on the line, and his instinct as a high-performer was to do more. He began showing up early and leaving late, desperately trying to clear a backlogged project queue that was meant for a three-person team.
But you cannot out-work systemic overload. The more pressure Rajiv piled onto himself, the more his productivity fractured. Driven by panic, he began taking frantic shortcuts on core architecture, creating mistakes he usually wouldn’t make. Then, swinging to the opposite extreme, he would spend hours paralyzing himself over the minutiae of a single line of code, trying to make it bulletproof against criticism. He was running on fumes, completely refusing to ask for help. Because he assumed that asking for help or feedback would seal his fate. He would be proven incompetent.
While he maintained ‘good behavior’ on the outside, the internal simmer was reaching a boiling point-all in complete silence. A medical crisis waiting to happen.
Rajiv was burning out.
Then slowly an epiphany emerged for Rahul:
“How strange. The moment I stepped back, he started making more mistakes. But that is not characteristic of Rajiv—he is an expert at this. Look at the sheer volume of tasks on his plate. Also, I have given zero feedback, nor have I established the measure of success. I wonder if the problem is Rajiv’s attitude—or if he is drowning under the weight of how I’ve been allocating the work?”
The Blind Spot of the High Performer
By the second week, Rahul knew it was time to talk. He scheduled a one-on-one and invited Rajiv into his office.
After breaking the ice, Rahul got straight to the point.
“Rajiv, first of all, I’m genuinely impressed with the progress you’re making on the project right now. We missed the deadline, but I know you’re doing everything you can to expedite delivery. On another note, I’ve been reflecting deeply on my own management style, and I want to understand how I can better support you. Your failure is my failure, because we are a team. I want to put two simple questions on the table for both of us:
First, what are you getting right now that you don’t want? And second, what do you want that you aren’t getting? Let’s figure this out together.”
Rajiv was stunned. The manager he had known to be obsessed with micromanagement and perfection was suddenly speaking a completely different language. The defensive, arrogant armor Rajiv wore began to soften.
“Rahul, thank you for asking,” Rajiv replied quietly. “I didn’t want to miss that deadline. But Pia and Santosh were given the exact same workload I was, yet they had two full weeks longer to complete their parts. I appreciate that you see me as a quality developer, but I am not superhuman. I felt completely trapped under unreasonable pressure, and I didn’t understand what I did to deserve it.”
Rajiv took a breath, the tension visibly leaving his shoulders before he added, “It also felt like I was shooting in the dark. Without clear milestones or expected quality checks along the way, I had no idea how to pace myself to hit your expectations.”
Suddenly, it hit Rahul.
He had fallen into the trap that catches so many well-meaning managers: punishing the performer. Without realizing it, he had been piling extra work onto his best developer simply because he knew Rajiv could handle it, unintentionally crushing him under undue pressure. By failing to provide clear goals and progress markers, he had unwittingly set his top talent up to fail.
Shifting from Boss to Diagnostic Leader
Because Rahul had spent the last week self-reflecting, he didn’t get defensive. “I see exactly what you’re talking about, Rajiv, and you are completely right,” Rahul admitted openly. “I never realized I was overloading you just because of your talent. Being capable shouldn’t warrant an unfair workload. And yes, mile markers and checkpoints of progress would help remove anxiety for both of us. Thank you for being so open with me.”
The relief in the room was palpable. Rahul promised they would establish reasonable schedules moving forward, ensuring Rajiv would no longer face unfair pressure just because he was a top performer.
This conversation was a massive turning point. Rahul felt relieved that he wouldn’t have to fire a talented team member, but he walked away with a profound leadership truth:
Difficult team members are often just symptoms. Leadership is usually the root cause.
Rajiv’s toxic pushback wasn’t born out of malicious intent; it came from an inability to constructively communicate how unfair he felt his treatment was. While he certainly could have handled his frustrations better, the ultimate responsibility lay with Rahul to take a diagnostic approach and figure out what was the underlying issue.
By giving Rajiv the safety to speak up, dropping his ego, and displaying genuine vulnerability, Rahul proved that his workplace was a safe environment to struggle, ask for help, and address systemic issues.
Look Past the Behavior
When you are weathering the storm of a difficult employee, don’t just react to the behavior—look for the underlying root cause. There is always a story behind the scenes; most of which are unfinished.
What looks like resistance might actually be a cry for help.
What looks like a bad attitude might actually be unfair pressure.
And the person you think is a “difficult employee” might just be a mismanaged top performer.
Turning a team around starts with a single, fundamental shift in leadership perspective. In Rahul’s case, practicing one specific core principle completely transformed a hostile workplace dynamic into an alliance built on mutual loyalty.
This is the essence of Diagnostic Leadership—the exact framework executive coach Robin helps organization leaders master.
If you are ready to turn your toughest team members into your strongest allies, stop managing the symptoms. Fix the root cause.👉 Ask Robin – Book Your 15-min Discovery Call
Disclaimer: This story is an illustrative narrative designed to convey leadership insights through storytelling. The characters and events are fictional and meant to reflect real-world situations many leaders face. Any resemblance to actual persons or events is purely coincidental.