As she refreshed her inbox, her heart felt a sharp jab of pain. The word “Resignation” popped in.

It was the third one in just six weeks. She wasn’t facing a casual turnover hiccup. This was a downward spiral. Quietly, she sat trembling, breathing heavily, wondering how she could stop the impending avalanche. She knew that if things continued like this, the sheer weight of it would bury her.

Akansha was a team manager at a top BPO in India. Even though she excelled at her job, she couldn’t point a finger at what was causing these recurring employee retention issues. Each goodbye was delivered with absolute grace—filled with standard corporate phrases like “moving on” and “thank you for your support.”

But hiding underneath those polite messages was something much deeper.

The Trap of the “Recruitment Engine”

Akansha was exhausted by the vicious cycle of hiring people every few months, only to see them leave. She wasn’t a bad leader; she had her heart in the right place and was highly strategic about recruitment. It wasn’t a matter of hiring the wrong people.

Furthermore, like all great places to work, she ensured her team had a comfortable working environment: flexible hours, wellness reimbursements, and top-tier incentives were all on the table.

Yet, people kept leaving.

At first, she rationalized it. “Maybe these are just different times. It’s Gen Z. You can’t expect the younger generation to stick around in one place for too long, right?”

Believing this high turnover was inevitable, she shifted her focus from retention to speed.

“If I can create a fast-paced recruitment engine, I won’t have to worry about people leaving. I can just replace them with a snap,” she thought.

She teamed up with her HR Manager, Jessica, to build a process where sourcing external candidates was faster than asking for internal referrals. In doing so, she turned her attention completely away from the underlying crisis, ignoring the early signs of the avalanche.

But retention problems are like a recession. At first, things appear manageable. Then, one day, the stocks crash, and fortunes are lost in a matter of hours, not days. The third resignation in six weeks was the avalanche announcing its arrival.

It was time to signal mayday.

The Confession and the Blind Spot

A few minutes after her breathing settled, Akansha dropped Jessica a note: “We need to talk.”

Soon, they were sitting across the table in the conference room. Akansha admitted that the situation was getting completely out of hand, the retention issues were unprecedented, and even their fast-track hiring process couldn’t save them.

Jessica agreed. They needed a solution, fast.

As they talked, Jessica pulled up the exit interviews. The feedback was standard corporate niceties: “great learning,” “appreciate the opportunities,” “looking for a new challenge.”

This was the most frustrating part of the puzzle. But Jessica paused, reflecting deeply. Turning to Akansha in a more detective-like tone, she noted, “Look at the feedback. Everybody is playing it safe, holding back the real reason they’re leaving. Exit interviews are a chance for employees to speak up, maybe even vent. But no one is doing us that favor here.”

Akansha quietly agreed. She took a deep breath, and then a spark of inspiration hit her. “Hey! I think we should speak to Nirmala. She’s been here for a long time. Perhaps she can give us a different perspective on what’s really happening.”

The Missing Link

A few minutes later, Nirmala joined them. Akansha took the lead. After a bit of small talk, she got straight to the point.

“Nirmala, you’ve been here for a while, and I trust your integrity completely. What we speak about stays in this room. Jessica and I are trying to understand why we are suddenly seeing so many resignations. For the life of me, I don’t understand what we are missing.”

Nirmala hadn’t expected the question, but she appreciated the trust.

“Akansha, while I can’t say why others are leaving, I can definitely speak for myself,” Nirmala said. “The perks and flexibility offered here, competitors offer too. That’s not a big differentiator. But when I hear of other opportunities where I could grow more financially, I don’t just look at the money. I look at the connection I have here. I feel connected to you, and to this company, which I’ve been with since its inception. You have been there for me whenever I faced personal challenges.”

She continued:

“I feel like we have a genuine bond—a connection that isn’t easy to establish quickly. Even with better benefits elsewhere, I’d miss this connection. Right now, this place hits the right spot for me when it comes to both support and compensation.”

Jessica, who had been listening quietly, suddenly stood up and hugged Nirmala. “Nirmala, you’re a genius!”

Nirmala smiled, wondering exactly what she had done to earn such praise, before politely heading back to work.

Tactical Retention vs. Real Connection

Once the door closed, Jessica’s eyes sparkled with newfound zeal.

“Akansha, I think I’ve got it,” Jessica smiled. “We’ve been trying to fix this problem all wrong. Nirmala is entirely right. Bigger companies out there can easily outdo us on perks and benefits. Why would a young person looking for growth hang around with us unless we offer something unique? And do you know what that unique thing is?”

Akansha looked at her with increasing curiosity.

“It’s the word support. Nirmala doesn’t work here for the perks alone; she works here because she feels valued and safe. She doesn’t feel like just another resource; she feels like part of a team.

Akansha, this is a wake-up call. You are a great manager, but Nirmala just revealed a major blind spot. For as long as I’ve known you, you’ve been technical in your hiring, but highly tactical with retention. Tactics can only go so far. What truly works is connection. We need to evolve your leadership style to build a culture centered around relationships, not just raw performance.”

Jessica leaned in. “Let me ask you honestly: How often does your team come to you and tell you they’re struggling? How comfortable do they feel telling you they had a difficult day at home? All those polite comments in the exit interviews reflect a deeper truth: People don’t feel safe to be vulnerable here. They feel compensated, but they don’t feel at home. Being a taskmaster or a boss is one thing. Being a leader is a whole new level.”

Then, she delivered the ultimate truth:

“From now on, let us focus on creating a culture where people can safely come to you and say, ‘I’m overwhelmed,’ ‘I’m struggling,’ or ‘I disagree.’ Because if they don’t feel safe doing that, the safest choice left for them is to leave.”

The Result: Finding Home

It was a hard pill for Akansha to swallow, but she knew Jessica was right. Armed with this realization, she wasted no time making the shift. Support, connection, and safety became her core metrics.

Every conversation and meeting from that point on reflected this new mindset. She started leading with openness, sharing her own challenges instead of acting like a boss who had everything perfectly figured out.

Slowly, the team responded. The office environment shifted from a bland, corporate landscape to a warm, supportive culture where people could bring their whole selves to work.

Fast forward three months later: the avalanche never came.

Instead, Akansha found exactly what she had been searching for all along: a place among her people, not as a boss, but as a true leader. She had finally found home—and so had her team.

In the end, it wasn’t the perks or the performance plans that turned things around. It was something far simpler, and far more human.

It’s a shift that most leaders overlook until it’s too late.

Are you facing employee retention issues on your own team? There is one fundamental thing you need to address before you tweak your perks or job descriptions. Want to know what it is? Ask Robin – He has helped dozens of corporate leaders spot their leadership blind spots, shift their cultures, and build the kind of cohesive teams that stay, grow, and thrive together.

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.

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.

So, I was on vacation in India. I had just lost my mother. I was anxious, sensitive, and irritable.

During a Zoom call, my team reported a lapse in an audit check. And I said—“I’m realizing I can’t be on vacation right now.”

I just said it. I didn’t think about how it would land. In fact, I recall justifying to myself: ‘I am being generous. I am announcing to my team that I am willing to be present as much as possible, even during a personal crisis.’ I felt magnanimous.

Is this what they call arrogance? Possibly.

My status quo dictated that I subconsciously default to a sense that my team couldn’t do their job without my physical presence. This assumption was that I had to be there all the time, and if I was gone, things wouldn’t get done. In other words, I fed my own flawed belief system.

But that sentence—those words—landed hard. And I didn’t know it yet.

So, I go back to Paris. I’m in my office, and then one of my lead statistician Aurelie, a strong woman, and mother of 3 boys, walks in—doesn’t ask, just walks in—and says, “Robin, I need to talk to you.”

“Of course, really, tell me what’s up?”

She looked me straight in the eye and said, “You said: I’m realizing I can’t be on vacation right now. Things just fall apart when I do. That hurt us. It’s as if you don’t trust us, as if you don’t think we are capable. Yes, we want to check things by you, but that does not mean we are incompetent. That was hurtful, Robin.”

And in that moment, boom! It hit me.

She was right. What I said, while I had my reasons, wasn’t just about me—it had hurt them. It was tantamount to disrespect, and I couldn’t brush it off.

I looked at her and said, “You’re right. You’re absolutely right. And unfortunately, the way I said it actually destroyed the truth—the fact is, I do trust you.”

I paused and then said, “Whatever anxiety I was feeling, that was my problem. But my words affected the team. And for this, I am going to apologize publicly and make sure this doesn’t happen again.”

And she just broke down in tears right there. And I let her.

That was the moment I realized that leadership isn’t about holding power—it’s about holding space. It’s about making people feel safe, making them feel trusted.

That was a turning point for me.

Shifting from Apology to Sufficiency

An apology is necessary to repair the crack, but it is not sufficient to rebuild the foundation. Real leadership requires digging beneath your own anxiety to uncover the flawed assumptions driving your management style.

To complete the repair of the rupture I walked into the bullpen and openly told my entire team “During my recent visit to India I had made a statement that implied that I don’t trust your skill. This is far from the truth. In fact, I trust your competence and commitment completely. Please accept my apology.

And I will do more, I will ensure that next time I am more thoughtful about my language so that my emotions don’t leak out inappropriately. Also, I thank Aurelie for her courage to tell me how I can correct the rupture I caused. I invite you to tell me anytime you feel slighted in the future.”

Having completed the repair, I was happy.

I consider myself very fortunate to have had such priceless, levelling experiences.

Have you ever found yourself in a similar situation, realizing your own blind spots were alienating your best people?

Stop managing the symptoms of team friction. Fix the root cause. Let’s talk– Book Your 15-Min Call