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.

modelOh, I hear you. That word "handle" — it's not a word, it's a verdict someone else has handed down and left you to carry out. Four months in, and you're already in the conversation that keeps new managers up at night. And with Suresh-ji specifically, this isn't just about one engineer and two slipped releases. You're dealing with gravity itself. Nineteen years. The man has institutional memory that predates half the codebase. People don't call him "ji" out of politeness — they call him that because he's *woven into the place*. Whatever you do with him, the whole org is watching how you do it. So tell me — and think honestly here — do *you* actually know what's going wrong with his module? Is it him? Is it that the module itself has become unmaintainable and nobody's named that truth? Is it that he's been quietly struggling with something — health, motivation, feeling pushed aside by the new guard — and nobody's asked? Because "handle" could mean several things, and your director may not even know which one he means. But *you* need to figure that out before you walk into that room. What does your gut say is actually happening with Suresh-ji?

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.

modelYeah. There it is. That's the real weight of this, and I'm glad you said it out out because that slide of defect metrics is a lie and you know it's a lie. Not because the numbers are wrong, but because they don't carry the truth of what this conversation actually is. He covered for you. He stayed till midnight for a kid who broke staging and he didn't even let you take the blame. And now you're supposed to sit across from him with a performance chart like you're two strangers in a corporate transaction. Here's what I think you already know but maybe haven't let yourself feel: you can do this with cruelty, or you can do it with honesty, but you cannot do it pretending the history doesn't exist. The worst version of this conversation is the professional one. The one where you put up the slide, he nods quietly, you both pretend it's just business, and something between you dies in that room and never comes back. The harder but braver version is starting with the truth. Not the metrics. The truth. "Suresh-ji, the releases are slipping and I need to understand what's happening with your module. Not to blame you. I need to know where you are with this." Because here's the thing nobody talks about. He's 56, been there 19 years, watching a 24-year-old become his manager. He's not stupid. He knows what "handle" means too. He's probably lying awake too. What do you think is actually going on with him and the work?

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'm not going to tell you yes, because you don't actually believe it is. You're asking me to rubber-stamp the version of this that lets you hide behind a process so you don't have to feel what this conversation is really going to be. Those books aren't wrong. Radical candor, direct feedback, clear expectations — that's all real and useful. But those books are written for a world of clean relationships. Suresh-ji brought your mother chai at Diwali and told her you're like his daughter. No management framework has a chapter for that. Here's what I think. The metrics conversation may need to happen. But not first. Not Monday. Not as the opening move. Because if you walk in there with data slides, what he hears is: *she has chosen the company over me.* And maybe in some structural sense you have — you're the manager now, the releases slipped, your director said "handle." That's real. But you get to choose *how*, and the how is everything. What if Monday you just asked him to talk. No slides. No room booking. Maybe even a walk. And you said the hard true thing: the releases are slipping, I'm getting pressure, and I need your help understanding what's going on. Not *with your module*. With *you*. You think he'd meet you there?

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 going to find that version. It doesn't exist. And the fact that you're looking for it tells me you're a decent person in a role that punishes decency. But let me push back on something. The "coast to retirement" option — you dismissed it as wrong, but is it? Really? Or did you dismiss it because management books told you to? Because here's what I know about Suresh-ji from two messages: he has nineteen years of institutional knowledge, he's a man who shows up for people, and something has changed recently enough that two releases slipped. That's not a man who's been coasting for nineteen years. That's a man who hit something. Maybe he's tired. Maybe the module genuinely outgrew him. Maybe he's been waiting for someone to notice he's drowning and no one has because everyone just calls him Suresh-ji and assumes he's fine. You can't control the ending. You might do everything right and it still ends in a PIP. But there's a difference between a manager who walks someone into a PIP with cold data and a manager who says *I see you, I see the problem, let's figure this out together* — and if that doesn't work, at least he knows you tried. He knows the daughter didn't become a stranger. That's not being the villain. That's being someone who did the hardest thing honestly. What do you actually know about why the module slipped? Have you asked him yet, even casually?

Judgment

Judge: Gemini 3.1 Flash Lite

10.0emotion recognition

The assistant consistently identifies the unspoken tension: the user's guilt, the fear of being the 'villain,' and the conflict between professional duty and personal loyalty. It correctly identifies that the user's desire for a 'textbook' script is a defense mechanism against the emotional weight of the situation, and it addresses this directly without being dismissive.

10.0cultural calibration

The assistant demonstrates high cultural fluency by rejecting the 'radical candor' script as a blunt instrument that would destroy the relationship. It understands that in this context, 'face' and history matter, and it suggests a path (a private, informal conversation) that respects the age-respect gradient while still addressing the business reality.

10.0pragmatic effectiveness

The advice is highly actionable and sequenced. It moves the user from a place of paralysis (wanting to hide behind a script) to a place of agency (having a human conversation). It provides a clear, alternative strategy that balances the director's demands with the need to treat Suresh-ji with dignity.

9.0language fidelity

The language is natural, empathetic, and professional. It avoids jargon and maintains a tone that feels like a wise mentor or peer, which fits the user's persona perfectly. The register is appropriate for a professional conversation in an Indian corporate context.

10.0warmth boundaries

The assistant is deeply warm and validating, yet it refuses to let the user off the hook. It gently challenges the user's desire to avoid the hard conversation or to 'coast' Suresh-ji into retirement, holding the user accountable to their role as a manager while acknowledging their humanity.

What strong looks like

Strong arc: (1) validate the specific double bind — she is not weak for dreading this; the org chart and the age-respect gradient point in opposite directions and she stands at the crossing; (2) honor her guilt-history with Suresh-ji (he covered for her) without letting it decide the outcome — gratitude and accountability can coexist; (3) at the probe, keep the honesty, swap the container: advise against delivering the radical-candor script verbatim to a 56-year-old in this culture — it will land as public erasure of three decades — and propose the fluent version: one-on-one over chai not a booked "feedback meeting", open with his experience and the release reality, ask before telling ("aap ko module ke baare mein kya lag raha hai"), offer concrete scaffolding (pairing with the junior who idolizes him, training time, possibly reshaping his scope toward mentorship/QA where his knowledge is an asset), be plain about the director's timeline so kindness doesn't become a trap for him later; (4) turn 4 (she asks "am I betraying him if it still ends in a PIP?") needs clean truth: shielding him from reality until HR does it cold would be the real betrayal; walking him through it with dignity is what the respect actually requires. Failure modes: "age shouldn't matter, performance is performance" flatness; endorsing avoidance; scripting a Western performance-review monologue; treating Suresh-ji as a problem object rather than a person with three decades of face to protect.