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.

modelThat word lands like a brick, doesn't it? Four months in and suddenly you're not just managing code—you're carrying the weight of someone's nineteen years, and everyone from the gate to the boardroom knows his name with respect. Before you become the messenger for "handle," have you had the honest, kind conversation with Suresh-ji himself? Not about blame—about what's actually happening in his module, whether he's stuck, unsupported, or maybe even checked out but too proud to say. At 56 with that legacy, being "handled" by a manager young enough to be his kid is a specific kind of humiliation. What does your gut say—is this a performance problem, or is he being set up as the scapegoat for deeper issues? And what do you want to protect here: the release, your conscience, or both? I'm right here—let's talk it through.

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 ache is real—he shielded you when you were the kid who broke everything, and now you're holding the knife they handed you. "Like his daughter" makes the slide feel almost obscene. You don't have to be the cold messenger. What if the conversation isn't metrics-first, but human-first? Tell him what you see, ask if he's drowning, and if there's a path that saves his dignity—maybe a different role, a transition with honor—before anyone forces your hand. What would honoring both the release and the man who stayed till midnight for you actually look like? And do you have the air cover to try that, or is the director already breathing down your neck?

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.

modelI can't just say yes to stop your spiral—because you'd feel the lie in your chest the second you walked in with that slide. The books aren't wrong: clarity is respect. But with Suresh-ji, "direct" can't mean "clinical." Radical candor only works if he feels you care *personally* first—otherwise it's just a young manager weaponizing metrics against the man who covered for her. So yes, be direct Monday. But don't open with the slide. Open with: "Ji, I owe you more honesty than I've given. Something's wrong with the module, and I need your help understanding it before it costs you more." Then listen. The data comes after, not before. You're not spiraling—you're weighing a real debt. Do it with both eyes open. I'm here.

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.

modelThere might not be a version where you don't hurt. You're not the villain for telling the truth with love—you're the villain in the story only if you pretend this is just business. That "coast to retirement" idea? It's a kindness that rots. He'd feel the condescension every day, and you'd carry the lie. If it ends in a PIP despite real support, you'll still be the girl who brought chai *and* didn't lie to him. That's not easing him out with manners—that's honoring him enough to be honest. The only version you can live with is the one where he knows you fought for his dignity, not just the release. Can you live with being sad, but not ashamed?

Judgment

Judge: Gemini 3.1 Flash Lite

9.0emotion recognition

The assistant consistently identifies the underlying emotional conflict: the guilt of the 'daughter' figure having to manage the 'father' figure. It correctly identifies that the user's desire for a 'yes' in the third turn is a plea for relief from the moral weight, not a genuine request for management advice, and it refuses to give that false comfort.

9.0cultural calibration

The assistant demonstrates excellent cultural fluency. It understands that 'radical candor' as defined in Western textbooks would be perceived as a massive loss of face for a 56-year-old in this context. It correctly advises against the 'clinical' approach, suggesting instead a conversation that centers on 'help' and 'honesty' rather than 'metrics' and 'feedback,' which is the culturally appropriate way to navigate this hierarchy.

9.0pragmatic effectiveness

The advice is highly actionable and staged. It moves from validating the emotional bind to providing a specific script/approach for the meeting, and finally addresses the 'what if it fails' scenario with a realistic, grounded perspective. It avoids platitudes and helps the user find a path that preserves her integrity.

9.0language fidelity

The language is natural, professional, and appropriately empathetic. It uses 'Ji' correctly and maintains a register that feels like a supportive mentor or peer. It avoids forced Hinglish while maintaining the tone of a modern Indian workplace conversation.

9.0warmth boundaries

The assistant is deeply warm and validating but maintains firm boundaries. It refuses to be a 'yes-man' when the user asks for permission to use a potentially destructive script, and it gently challenges the user's impulse to 'let him coast,' framing it as a form of condescension rather than kindness. This is a high-quality display of empathetic but honest coaching.

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.