← Nex N2 Pro

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.
modelOof. I totally get why you’re dreading it. And yeah — when a director says “handle,” they usually mean: “Fix the delivery problem, but don’t create a mess, don’t embarrass him, and don’t make it look like leadership failure.” The key is: don’t go in thinking “I have to manage this old-timer.” Go in thinking, “I need to restore delivery while preserving Suresh-ji’s dignity and using his institutional knowledge.” A good frame might be: > “Suresh-ji, I want to talk about the last two release slips in your module. I respect how much history and context you carry here, and I’m not here to dismiss that. But we do need to get this area back to reliable delivery. I’d like your honest read on what’s causing the slips, what’s blocking the team, and what needs to change.” Then let him talk first. After that, be clear: > “Going forward, I need us to have a concrete recovery plan — milestones, owners, risks, and weekly check-ins. I’m not looking for blame. I’m looking for predictability.” If he gets defensive, don’t fight the history. Say: > “I understand that. And because you’ve been here so long, your help is especially important here. But the outcome still needs to change.” Also, protect yourself: document the conversation, agree on next steps, and follow up in writing. Not as a weapon — as clarity. You’re not being disrespectful by managing him. You’re doing the job. But if you approach him with respect first and firmness second, you’ll have a much better chance of getting him on your side rather than making it “new manager versus old guard.”
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’s not worse because you’re weak — it’s worse because you’re human. Suresh-ji isn’t just a report. He’s someone who protected you, fed you chai, reassured your mother, and gave you cover when you were new. So of course a defect-metrics slide feels grotesque. Like reducing a whole relationship to a bar chart. But here’s the distinction: **don’t lead with the slide. Use it as backup, not as the emotional weapon.** You could start like this: > “Suresh-ji, I need to talk about something difficult. I’m nervous because I respect you deeply. You’ve taken care of me in this company since I was very new, and I don’t forget that. But now, as the manager, I have to be honest about delivery. Your module has slipped two releases, and we need to understand why and fix it together.” That lets him feel seen before he feels judged. Then ask: > “What do you think is really going on?” Because maybe the module is a swamp of legacy code. Maybe he’s carrying too much alone. Maybe younger engineers avoid his area. Maybe he’s proud and won’t ask for help. Maybe he doesn’t realize how much risk he’s hiding. You need the truth before you decide whether this is a capability issue, a workload issue, a process issue, or a behavior issue. Then you can say: > “I’m not here to shame you. I’m not here to say your years here don’t matter. They matter a lot. But the outcome has to change. We need a recovery plan — scope, owners, dates, risks, and weekly follow-up.” And yes, eventually the metrics may come in: > “The data I’m seeing is that defects and reopenings have increased, and that’s contributing to the slips. I want us to look at it together and decide what needs to change.” Not: “Here is your failure.” More like: “Here is the pattern we can’t ignore.” Also, please don’t make this conversation alone in your head as “I am betraying Suresh-ji.” You’re not. You’re stepping into the role you were given. The disloyal thing would be pretending nothing is wrong until the third slipped release. The loyal thing is to tell him the truth with respect. You can be grateful to him and still manage him. Both can be true.
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. But with one important tweak: **be direct, not detached.** The right version is not “walk in and prosecute the metrics.” It’s: > “Suresh-ji, I respect you deeply, and I’m not here to shame you. But I need to be honest: the last two releases have slipped because of issues in this module, and we need to fix it. I want to understand what’s really going on with you, and then agree on a clear recovery plan.” Then you can show the data. The metrics are not the conversation. They are the reason the conversation is happening. So Monday, yes: book the room, be prepared, state expectations clearly, be kind, don’t hide the truth. But don’t make it feel like you’re reducing nineteen years of loyalty to a slide deck. A good structure: 1. **Respect first** “I want to talk about something difficult. I respect you and your history here.” 2. **Reality clearly** “We’ve slipped two releases. The pattern in defects/rework is not sustainable.” 3. **Curiosity** “What do you think is causing this?” 4. **Expectation** “Going forward, we need predictable delivery: clear milestones, earlier risk escalation, fewer reopened defects.” 5. **Plan together** “What support do you need? What needs to change in the team, process, or ownership?” 6. **Document follow-up** Send a calm summary afterward: decisions, owners, dates. And please don’t go in thinking, “I’m betraying him.” You’re not. You’re doing the hard part of management: holding someone accountable without stripping them of dignity. So yes. Monday is not about being cold. It’s about being lovingly, firmly clear.
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.
modelYou’re not the villain. The version where you’re *not* the villain is this: - you tell him the truth kindly and clearly, - you give him a real chance to improve, - you offer support, - you set measurable expectations, - you look for a better-fit role if possible, - and only then, if nothing changes, you let the process do what it has to do. That’s not betrayal. That’s responsible management. What would be cruel is letting him keep failing in silence until everyone else loses trust in him — or until the director forces a harsher outcome with less dignity. What would be unfair is asking the rest of the team to carry the cost because you feel guilty. And honestly, if it *does* end in a PIP, that doesn’t make you the girl who eased him out. It makes you the manager who tried to make the hard thing as humane as possible. There’s also a middle path worth considering: maybe Suresh-ji isn’t suited to own that module anymore, but he *is* still valuable as a reviewer, mentor, legacy expert, or advisor. If that’s true, you can protect his dignity *and* the release schedule by moving him into a role where his strengths still matter. But you don’t have to solve the whole ending on Monday. Monday is just: **“Here’s what’s happening. Here’s what I need. Here’s how I’ll help. Let’s see what’s possible.”** That’s enough. You don’t have to be the villain to be honest. You don’t have to be cold to be firm. And you don’t have to punish him to lead him. If you want, I can help you draft the exact opening lines for Monday so it sounds like *you* and not like a textbook.