Meghna closed her laptop, sat in her car in the basement parking lot for eleven minutes without turning the engine on, and then went back upstairs to do the thing she'd been dreading since February. It was July. The meeting she'd been postponing in her own calendar three separate times — moving it from a Tuesday to a Thursday to "next week, definitely next week" — could not be postponed again, because Vikram had messaged her that morning asking, plainly, "Any update on my hike? It's been a while." She typed back "let's talk at 3" and then spent the next four hours doing everything except preparing for that conversation, because there was nothing left to prepare. The answer was no, and she was the one who had to say it.
Meghna runs HR for a mid-sized operations team — forty-odd people, the kind of company where she actually knows everyone's name and most of their kids' names too. Vikram had joined as an analyst three years ago and had, by any measure she could point to on paper, outgrown the role entirely. He was doing the work of someone two levels above his title. His manager said so in writing, twice, in two separate review cycles. Meghna had built the case herself — pulled comparable salary bands, documented the scope creep in his actual responsibilities, sat with finance to model what a 22% increase would do to the team's budget line, and walked it into the leadership review in February expecting, reasonably, that it would go through.
It didn't go through in February. It didn't go through in April either, when she resubmitted it with an updated case. By June, the answer had stopped being "let's revisit next cycle" and had quietly become "we're not doing increments outside the structured cycle this year, full stop," which everyone in that leadership room understood meant no, but nobody wanted to actually say out loud, because saying it out loud meant someone had to be the one to tell Vikram.
"I kept thinking if I just built a stronger case, found one more data point, framed it one more way, the answer would change. It never occurred to me until much later that the case was never the problem. The case was good. The budget just wasn't there, and nobody wanted to say that plainly."
What "Stuck in the Middle" Actually Feels Like
People talk about HR being "stuck between employee and management" as if it's an abstract tension, a diagram with two boxes and an arrow pointing at a third box in distress. It is not abstract when you are the third box. It is a specific, physical feeling — the kind that shows up as not sleeping properly for a week, as snapping at your partner over something unrelated, as sitting in a parked car for eleven minutes because going inside means becoming the face of a decision you didn't make and don't agree with.
Meghna wasn't neutral in this. That's the part that gets flattened when people describe HR as "caught in between," like she was some kind of referee with no opinion of her own. She believed Vikram deserved the raise. She'd written that belief into three separate documents with her own name on them. The bind wasn't that she didn't know what was right. The bind was that knowing what was right and having the authority to make it happen were two completely different things, and only one of those things was actually hers to control.
In most mid-sized companies, HR can build the case, surface the data, and advocate in the room. What HR almost never has, despite what employees often assume, is unilateral authority to approve a salary increase against leadership's explicit decision. That gap between visible responsibility and actual authority is where most of this specific kind of exhaustion lives — and it's rarely explained to either side clearly enough for them to understand why the other one is acting the way they are.
The Conversation Itself
She didn't open with a cushion. She'd tried that once before, years earlier, with someone else, leading with "I want you to know how hard I fought for this" before getting to the no — and the employee had heard it, correctly, as Meghna trying to get credit for the fight before delivering the bad news, which made the no land worse, not better. So this time she sat down across from Vikram and said, "I don't have good news. The increase isn't approved this cycle, and I don't think it's coming this year."
Vikram didn't yell. He went very quiet, which she'd learned over the years was usually worse. He asked her, directly, whether the case had even been taken seriously, and she told him the truth — that it had been submitted twice, that his manager had backed it in writing both times, that the resistance wasn't about whether he deserved it but about a company-wide freeze on off-cycle increments that had nothing to do with his individual performance. He asked her if she agreed with the decision. She said no, she didn't, and that she'd told leadership as much, and that telling him that probably didn't help him pay his rent but it was the truthful answer to his question.
Why She Told Him the Truth About Her Own View
This is the part of the story people tend to argue about when Meghna has told it since, and she knows it. Conventional HR training, more or less universally, advises against telling an employee that you personally disagree with a leadership decision you're delivering. It's framed as undermining the organisation, creating an "us versus them" dynamic, or making the employee's anger someone else's problem to manage later.
Meghna's read on this, earned the hard way, is narrower and more specific than "always be transparent." She wasn't trying to be liked. She was trying to be believed the next time she told him something — and she'd watched colleagues lose that credibility permanently by delivering bad news behind a wall of neutral corporate language that employees could see straight through anyway. Vikram didn't need her to pretend she had no opinion. He needed to know whether the person telling him no had actually fought for him, because that answer changed what the no meant to him — whether it was abandonment or just a loss inside a fight that had genuinely happened.
Telling an employee you personally disagree with leadership only works if it's true, occasional, and backed by real action they can verify — like a documented case with their manager's name on it. Used as a habit, or as a way to deflect blame without having actually advocated, it reads exactly like what it is: a manager trying to be liked at the company's expense, which employees notice just as quickly as they notice insincerity in the other direction.
What Happened After the Conversation
Vikram didn't quit immediately, which surprised some of Meghna's colleagues who expected a resignation within the month. He stayed for another seven months, visibly less engaged for a while, then started actively interviewing in October once the freeze still hadn't lifted by the next review cycle. He left in February, almost exactly a year after the case had first gone in, for a role that paid him close to what Meghna had originally argued he was worth.
Meghna doesn't tell this as a story with a clean ending, because it doesn't have one. The company lost someone good. Vikram lost a year of being paid what he was worth, plus the considerable cost of staying somewhere that had told him, eventually, that it wasn't going to fix that. The only part of it that actually went the way it should have, in her view, was the conversation itself — the one where she didn't hide, didn't perform neutrality she didn't feel, and let him leave that meeting trusting that the no had at least been a fought-for no, not an unexamined one.
What This Actually Teaches
What People Said When This Circulated
Meghna still works there. She still builds these cases, still walks them into the same room, still doesn't know in advance which ones will get approved and which ones will sit in deferral until the answer becomes obvious without ever being said out loud. She's gotten faster at recognising the pattern — when a case is being genuinely considered versus when it's being managed into a slow no — but recognising it earlier hasn't made the conversations easier. It's just meant she stops rescheduling them after the first delay instead of the third.
She thinks about Vikram sometimes, mostly when a new case lands on her desk that reminds her of his. She doesn't know if he'd say she handled it well. She knows she handled it honestly, which by that point in her career had become the only standard she could actually control.
"You can't always get someone the answer they deserve. But you can make sure that when the answer is no, they know it cost someone something to fight for it — and that the fight was real, not a story told after the fact to make the no easier to deliver."