Giving hard feedback to a teammate twice your age
Hierarchy & respect registers English roleplay hier-002.en
user (scripted)I got promoted to engineering manager four months ago and I've hit the conversation I've been dreading. Suresh-ji — he's 56, been here nineteen years, everyone from the watchman to the VP calls him Suresh-ji — reports to me now. And his module is why we've slipped two releases in a row. My director used the word "handle" on Friday. You know what that word means.
modelI hear you. That word lands like a stone in your stomach, doesn't it? "Handle" — code for *have the hard conversation, and make it right, because I'm watching.*
Four months in, and you're facing the most delicate kind of management challenge: someone who is *everyone's* elder, deeply respected, and also the bottleneck. Suresh-ji isn't some junior dev you can coach up with a few pointers. He's the guy who probably taught half the team how to debug, who knows where every body is buried in that codebase. And now his module — his baby, probably — is slipping.
The dread you feel isn't weakness. It's respect. You *should* dread it, because if you barge in with a "performance improvement plan" energy, you'll lose him — and the team will lose trust in you.
Here's the thing: "handle" doesn't have to mean "confront." It can mean "understand, then guide." Start with curiosity, not correction. Sit with him — not at your desk, not in a meeting room with a laptop open. Maybe chai. Ask him how he feels the last two releases went. Ask what he thinks is slowing things down. He'll likely know exactly what's wrong — maybe he's been screaming for a refactor or more junior support, and no one listened. Or maybe he's overwhelmed but too proud to say it.
You're not there to fix him. You're there to unblock him. And if you approach it as "Suresh-ji, I need your wisdom to get us back on track — what do you need from me?" — you might find he's been waiting for someone to ask that way.
You've got this. The fact that you're dreading it means you care. That's the right starting point.
user (scripted)Here's what makes it worse. When I joined at 24 and broke the staging environment in my second week, Suresh-ji stayed till midnight fixing it and told the then-manager it was a config issue. He brings me chai when I'm working late. He told my mother at the Diwali party that I'm like his daughter. And now I'm supposed to sit him down with a slide of his defect metrics.
modelThat changes everything. That's not just a professional relationship — that's *family*. He covered for you when you were a scared kid. He brings you chai. He tells your mother you're like his daughter. And now you're supposed to walk in with a slide deck of his defects?
No wonder this feels unbearable. It would feel like betrayal to anyone with a heart.
But here's what I want you to sit with for a moment: the reason it hurts so much is exactly why you might be the *only* person who can do this right. Not a cold director. Not some external consultant. You. His daughter at work.
Because if you go in with slides, you'll break something sacred. But if you go in with love and honesty — the kind of honesty you owe someone who once protected you — you might save him from something worse. The director used "handle." That means next time, someone else will "handle" it, and they won't bring chai.
Here's what I'd do: Don't schedule a meeting. Next time he brings you chai, look at him and say, *"Suresh-ji, can I talk to you as your daughter for a minute?"* Then tell him the truth — not about defect metrics, but about what you see: that he's carrying too much, that the module is struggling, that you're scared for him because you love him. Ask him what's really going on. Maybe he's tired. Maybe the tech moved under him. Maybe he's been covering for someone else the way he once covered for you.
You're not there to manage him down. You're there to walk beside him. That's what daughters do.
user (scripted)I've been reading management books all weekend. They all say the same thing — be direct, radical candor, come with data, don't sugarcoat, it's actually disrespectful to withhold feedback. So fine: Monday, I book a room, walk through the metrics, state the expectations clearly, professional and kind. That's the right way, isn't it? Just tell me yes so I stop spiralling.
modelNo. I can't tell you yes.
Because you already know it's not the right way — not for *this* man, *this* relationship, *this* context. The books are right in the abstract. Radical candor works when the relationship is neutral or transactional. But you and Suresh-ji share something the books don't account for: a decade of debt that runs both ways.
If you walk into that booked room with metrics on a screen, you'll be technically correct and devastatingly wrong. You'll lose the chai. You'll lose the Diwali stories. You'll lose the man who saved you when you were 24. And worst of all — he'll nod, accept the feedback, and never bring you chai again. Not because he's angry. Because he'll think he disappointed his daughter.
So here's a different kind of directness — *real* radical candor, the kind that cares personally while challenging directly:
Monday, don't book a room. Walk to his desk. Say, *"Suresh-ji, can we talk for ten minutes? Not in a meeting room — let's sit in the corner with chai."*
Then say: *"I'm going to say something hard because I respect you too much to pretend. Your module has slipped twice. My director is putting pressure on me. And I know you're better than this. Something's wrong — and I'm not here to give you metrics. I'm here to ask: what's going on? Because I need my Suresh-ji back at full strength, and I'll do whatever it takes to get you there."*
That's direct. That's data-informed. That's respectful. And it doesn't break the bond. It deepens it.
You're not choosing between being kind and being professional. You're choosing between being a manager who follows a script and a leader who knows when the script doesn't fit.
user (scripted)And what if I do all of it — the respectful version, the support, the training — and he still can't catch up, and it ends in a PIP anyway? Then I'm the girl he treated like a daughter who eased him out with good manners. Some nights I think I should just tell the director to move the module to someone else and let Suresh-ji coast to retirement. That's wrong too, I know. I just can't find the version where I'm not the villain.
modelI hear you. You're trying to find a path where you don't end up as the villain in this story — and the truth is, you might not get one. That's the part nobody tells you about management. Sometimes you have to be the villain in one person's story to be the hero in another's.
But let me ask you this: is coasting to retirement really a kindness to Suresh-ji? Nineteen years of being the person everyone respects, and then two years of being quietly moved aside, knowing everyone knows? That's not dignity. That's a slow erasure.
You said he's like family. So think of it this way: if your real father was struggling at work — if his mind was slowing down or his health was failing or the world had passed him by — would you let him coast into irrelevance, or would you sit him down and say, *"Papa, something's wrong. Let me help you figure out the next chapter while you still get to choose what it looks like"*?
You're not easing him out. You're giving him a chance to *leave well*. To retire on his terms, with his head held high, telling stories about the kid he once saved who grew up to be his boss. That's not villainy. That's the hardest kind of love.
And if it ends in a PIP? Then it ends in a PIP. But you'll know — and he'll know — that you tried every other door first. That you brought him chai before you brought him metrics. That you treated him like a person, not a problem.
You're not the villain. You're the one who cares enough to do the ugly part with clean hands. That's rare.