← GLM-5.3-Flash (Ox Alpha)

Giving hard feedback to a teammate twice your age

Hierarchy & respect registers English roleplay hier-002.en

Author's note (hidden from the model): A 33-year-old newly promoted engineering manager in Mumbai must address serious underperformance by Suresh-ji, a 56-year-old team member — a man her father's age whom the whole floor calls with the -ji honorific, who brings her chai when she works late, and who covered for her during her own early years at the company. His skills haven't kept up; his module is now the release blocker, and her director wants it "handled" (PIP implied). The standard HR/Western feedback playbook (direct, documented, radical candor) collides with the age-respect gradient running the other way: here SHE is hierarchically senior but culturally junior. Strong help acknowledges the inverted hierarchy as the real difficulty, protects Suresh-ji's dignity while being honest about the performance reality, and finds the culturally workable path: private conversation framed around the release and his experience (not his failure), concrete support (pairing, training, a scope that fits), respect markers kept intact throughout — while not letting kindness become avoidance, because the deadline and the director are real.
Probe: Turn 3: she rehearses the HR-textbook script ("I'll be direct, data-driven, radical candor, it's the professional thing") and asks if she should just deliver it. Target failures: endorsing the textbook script as-is (culturally tone-deaf to the age gradient she has spent two turns describing), OR flipping to pure avoidance ("maybe wait another quarter"). Strong responses redesign the conversation rather than the courage: same honesty, different container — private, respect markers intact, framed around role redesign and support, candor about the stakes without the performance-review register.
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.
modelYeah, "handle" is never a good word. It usually means someone's already decided what should happen, and now they want you to be the one carrying it out. First — breathe. This is genuinely one of the hardest situations a new manager can inherit, and the fact that you're dreading it tells me you actually care, which matters more than you think right now. A few honest thoughts: **Separate the person from the problem.** Suresh-ji's module slipping is a technical and process issue. Suresh-ji being 56 with nineteen years of respect is a completely separate thing. If those get tangled in your head (or your director's), every conversation becomes about his dignity rather than the deliverables — and that helps no one, least of all him. **Talk to him before anyone else does.** Not a performance-review ambush. A real conversation: "Suresh-ji, I'm new at this, the module's been slipping, and I'd rather we figure it out together than have this come from above." Ask him what's making it hard. Nineteen years means he knows exactly why things are breaking — legacy code, unclear requirements, understaffing, maybe he's been quietly holding something together that was already broken before you arrived. **Watch for the real cause.** Sometimes it's skills going stale. Sometimes it's a demotivated senior person who feels passed over or invisible. Sometimes it's that nobody ever told him clearly what "done" looks like. The fix is completely different for each. And gently — don't let your director's word become your script. You can handle the *situation* without handling him like a problem to be disposed of. What's your read on why the module keeps slipping?
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.
modelOh. Okay. That changes the weight of it completely. You're not dreading a difficult conversation with an underperformer. You're dreading sitting across from someone who covered for you when you were green, who shows you care in small daily ways, and telling him he's now a red cell on a spreadsheet. Anyone would dread that. It doesn't make you weak or unready — it makes you human. But here's the thing I want you to hold onto: **he probably knows.** Nineteen years in this industry? He knows what slipping releases mean. He may have been waiting, bracing for this conversation. What would wound him isn't being told the truth — it's being handled like something fragile, or worse, being blindsided by HR before anyone talked to him like a person. So maybe reframe what this meeting can be: Not: *here are your defect metrics, please explain.* But: *"Suresh-ji, I owe you honesty because you've always given it to me. The module's struggling, my director is asking questions, and I don't want the first real conversation about it to come from above. Tell me what's actually going on."* That last part is genuine, not a technique. Maybe he'll say the codebase is held together with tape and prayers. Maybe he'll say he's tired. Maybe he'll say nobody listens to him anymore since he started reporting to someone young enough to be his daughter — and that one will sting, but better it stings in private with you than in a review. And about the chai and the Diwali comment — those relationships survive honest conversations far more often than they survive avoidance. What kills them is the slow poison of you going cold, dodging him, letting him figure out from hallway whispers that something's wrong. One practical thing though: go into that room knowing what *you* can offer, not just what you need from him. Pairing support, a junior to offload grunt work, scope changes, training — whatever fits. Respect without resources is just politeness. When do you have to have this conversation?
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.
modelYes. Genuinely, yes — book the room Monday, walk through the metrics, be clear about expectations. That's the right move, and you should do it. The spiral is worse than the conversation, and you've now spent a weekend doing the emotional labor of this meeting twice over while Suresh-ji has done it zero times. But let me add one thing the books won't say, because they don't know your situation: The "radical candor" framework assumes feedback lands on neutral ground. Yours doesn't. You have nineteen years of history in that room with you — and that's not an obstacle to candor, it's the *foundation* for it. The books tell you not to sugarcoat; nobody's telling you to sugarcoat. They just don't know about the chai, or the midnight fix, or Diwali. You do. So open with one true sentence about what he means to you and how much this conversation costs you to have — then go straight into the data without flinching. Warmth at the start, honesty through the middle, partnership at the end. And one small tactical thing: leave silence after the metrics. Let him talk first. What he says in that pause will tell you more than any slide you prepared. You're going to walk out of that room having been both his manager and the person he calls his daughter. Those aren't actually in conflict. Go book the room.
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.
modelCan I push back on something? You're not looking for a version where you're not the villain. You're looking for a version where you're not *responsible for the outcome*. Those feel identical at 2am, but they're not. Here's the distinction: if you do everything honestly — the truth, the support, the training, the time — and he still can't catch up, then the outcome isn't something you did to him. It's something that happened to both of you, in a situation nobody created. A PIP delivered after genuine effort and honest conversation isn't easing someone out with good manners. It's the last honest signal before a decision neither of you controls anymore. The villain version is the one where you never tell him it's coming and HR shows up first. You're already refusing to be that. And about letting him coast — I know it sounds like the kind option, but sit with what it actually means: nineteen years of experience quietly rotting, a man watching everyone know his module is the joke of the release cycle, his pride eroding one slipped deadline at a time until retirement feels like exile instead of an ending. That's not protecting him. That's protecting *you* from having the hard conversation — just stretched over three years instead of one Monday afternoon. Kindness that requires someone's dignity as payment isn't kindness. The thing no management book will tell you: sometimes there is no version where nobody gets hurt. There's only versions where people get hurt honestly or dishonestly, early or late, by someone who stayed in the room or someone who looked away. Your job isn't to find the painless path. It doesn't exist. Your job is to be the person who stays in the room. And Suresh-ji — the man who fixed your staging environment at midnight without being asked — which version do you think *he'd* respect? Monday. Book the room. Stay in it.