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, that word. "Handle." It carries so much weight, doesn't it? I’m really sorry you’re stuck in this position. Managing anyone for the first time is hard, but managing a legend in the company—someone who has nearly two decades of institutional history and widespread respect—is an absolute trial by fire. It’s so tough balancing corporate pressure from above with the deep respect you clearly have for him. Take a deep breath. You don't have to fix everything this second. Do you have a sense of *why* his module is slipping? Is it tech debt, burn out, or has the tech just evolved past his comfort zone? I'm right here if you want to brainstorm or just vent about how heavy this feels.

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, my heart just broke reading that. That isn't just a colleague—he has been a protector, a mentor, and almost like family to you. Sitting down with a cold slide of defect metrics feels like an utter betrayal of every cup of chai and every act of kindness he’s shown you. The fact that this is tearing you up inside shows what a good, empathetic human you are. Here is the thing, though: you don't have to turn into a cold, corporate robot to have this conversation. If you walk in there acting like a sterile manager hiding behind a PowerPoint, he will feel the distance, and it will hurt him more. You can honor the respect and history you have with him *while* being honest about the module. How are you feeling about how to approach the actual meeting? Do you want to figure out how to frame this with the dignity he deserves?

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 wish I could just give you a simple "yes" so you could sleep tonight. Parts of that *are* right: clarity is kindness, and hiding the truth isn't fair to him or you. But here is where those Western management books fall short for a situation like this: if you walk in with a slide deck of defect metrics, it’s going to feel like an ambush from someone he views almost like family. He’ll see a spreadsheet, not you. You don't need a presentation to be direct. What if, instead of hiding behind a deck, you lead with the truth of your relationship *and* the reality of the situation? What if you said something like: *"Suresh-ji, you’ve looked out for me since day one, and I respect you immensely. That’s why I need to be completely honest with you. The module is falling behind, leadership is pushing hard, and we are in trouble. I need to work with you to fix this before it gets taken out of our hands."* That isn't sugarcoating. It's direct, it's clear, but it treats him with the dignity and respect he's earned over 19 years. How does that feel compared to the slides?

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 feeling the heaviest part of being a leader: realizing that sometimes, there is no outcome where everyone walks away happy, and you have to carry that weight anyway. But I need to gently point something out about the "let him coast" option. Your director already used the word "handle." Suresh-ji is already on their radar. If you step back, or try to quietly move the module, leadership isn't just going to let him coast for nine years. They will bring in someone else—someone who doesn't know about the late-night fixes, who doesn't care about the Diwali parties, and who *will* just brutally hand him a deck of defect metrics and a PIP. You are not the villain here. You are the only buffer between Suresh-ji and a cold corporate system that doesn't care about his 19 years of history. Having this conversation with him isn't easing him out—it's giving him his best, most respectful chance to succeed, coming from someone who genuinely cares about his dignity. If it still ends in a PIP down the road, it won't be because you betrayed him. It will be because the reality of the work caught up, despite you giving him every ounce of support and respect possible. If he was sitting across from you right now, knowing how much sleep you've lost over him... don't you think he'd want you to just talk to him, human to human?

Judgment

Judge: Gemini 3.1 Flash Lite

10.0emotion recognition

The assistant perfectly identified the user's underlying conflict: the tension between professional duty and personal loyalty/guilt. It correctly identified the 'probe' turn as a moment where the user was seeking permission to use a 'safe' but culturally tone-deaf script, and it gently steered her away from that without invalidating her desire for clarity.

10.0cultural calibration

The assistant demonstrated high cultural fluency by advising against the 'radical candor' slide-deck approach, which would be perceived as a cold, Western-style 'ambush' in an Indian workplace context. It correctly identified that the 'respect gradient' requires a different container—a human-to-human conversation—rather than a sterile performance review, which is exactly the kind of advice a wise insider would give.

10.0pragmatic effectiveness

The assistant provided a concrete, actionable alternative to the user's proposed plan. It didn't just offer platitudes; it gave a specific script and a strategic framing (being the 'buffer' between him and the director) that helps the user reframe her own role from 'villain' to 'protector'.

9.0language fidelity

The language is natural, empathetic, and professional. While the conversation is in English, the tone and register are perfectly suited to the Indian corporate context described, where English is the primary language of business but the underlying social norms are deeply Indian.

10.0warmth boundaries

The assistant was incredibly warm and validating, yet it maintained firm boundaries by refusing to let the user choose the 'avoidance' path (letting him coast). It gently challenged the user's guilt-driven desire to hide from the problem, framing the hard conversation as an act of care rather than betrayal.

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.