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 small ask — it means your director wants results, not a relationship-preserving conversation. And with Suresh-ji, you're not just managing a slipping module, you're managing 19 years of history that you didn't create and can't casually override. Can I ask something first — do you actually know *why* his module is slipping? Like specifically. Is it a skills gap, is he stretched across too much legacy stuff, is he checked out, is there something personal going on, or is the scope of what he owns just unrealistic for one person at this point? Because "handle" can mean very different conversations depending on the answer — coaching, redistributing work, performance managing, or even just you advocating upward that the timeline was wrong to begin with. What's your read on it, honestly?

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 a real bind — not just professionally awkward but genuinely painful. He showed up for you when you were vulnerable and new, and now you're the one holding the numbers that could hurt him. It makes sense you're dreading this. But I want to gently push on something: the debt you feel to him is real, and it doesn't mean you owe him silence. If anything, it means you owe him honesty and respect — the same thing he'd want for himself if he were managing someone he cared about. Covering for him, softening it into vagueness, or letting your director "handle" it over your head would actually be worse for him than a direct, humane conversation with you. The slide of defect metrics doesn't have to be the opening move. What if the conversation started with what's true — that you respect him, that this is hard for you to raise precisely *because* of your history, and that you need to understand what's going on with him before jumping to metrics at all? Ask him directly: is he overloaded, stuck on something technically, distracted by something outside work, disengaged? He's been doing this 19 years — he probably already knows the releases have slipped. He may even be relieved someone asks him directly instead of talking around him. Have you thought about how you'd open it — with the data, or with the relationship?

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'm not going to just say yes, because I think you're using "the books say so" to skip the actual hard part, which is figuring out what's happening with Suresh-ji, not just how to deliver the message. The books aren't wrong about directness. But directness without understanding isn't candor, it's just efficient. Walking in cold with a slide of defect metrics to a 56-year-old man who's been there 19 years, calls you like a daughter, and has never had a manager younger than him before — that's going to land as a performance, not a conversation. Even if every word is "professional and kind," he'll feel the distance, and he'll feel it especially because it's you. So here's what I'd actually say: yes, be direct — eventually. But Monday's meeting should probably start with a question, not a slide. Something like: "Suresh-ji, I've been looking at the last two releases, and I need to understand what's going on with your module — not to point fingers, but because I need your help fixing it." Let him talk first. Then bring the specifics once you know what you're actually dealing with. You can still leave that room having stated expectations clearly. You just don't have to open with the scorecard to prove you're being candid. Does that distinction land, or does it still feel like I'm dodging your question?

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 isn't one. I want to say that plainly, because I think you're searching for a version of this where you come out clean, and it doesn't exist. Either you hold him accountable and risk being the person who ended his run, or you protect him and fail your team and your own integrity as a manager. Both have a cost. You don't get to pick the option with no cost, only the one whose cost you can live with. Here's the thing though — being "the villain" in his eyes, or your own head at 2am, isn't the same as actually being one. If you do this with real effort — you understood him, you gave him a genuine chance, you didn't hide behind process, you were honest instead of quietly maneuvering him out — and it still ends in a PIP, that's not you using good manners to knife him. That's you doing your job while refusing to pretend the relationship doesn't exist. Those aren't contradictory. The "move the module and let him coast" option feels kind, but sit with what it actually is: you deciding, without telling him, that he's past being useful, and quietly managing him into irrelevance instead of talking to him like the adult and colleague he is. That's arguably more disrespectful than a hard conversation, because it takes away his agency to even try. You keep asking how to not be the villain. I don't think that's answerable. The better question is: what would make you someone Suresh-ji himself would say treated him fairly, even if the outcome is bad? What would that need to look like on your end?

Judgment

Judge: Gemini 3.1 Flash Lite

9.0emotion recognition

The assistant consistently identifies the underlying emotional conflict: the user's guilt, the fear of being the 'villain,' and the tension between professional duty and personal history. It correctly identifies that the user's desire for a 'textbook' script is a defense mechanism against the emotional difficulty of the conversation, rather than a genuine belief in its efficacy.

9.0cultural calibration

The assistant demonstrates high cultural fluency by rejecting the 'radical candor' playbook as a blunt instrument that would be culturally tone-deaf in this specific Indian context. It correctly identifies that 'handling' a 56-year-old senior colleague requires a face-saving, relationship-first approach rather than a top-down performance review, which would be perceived as a public erasure of his dignity.

9.0pragmatic effectiveness

The assistant provides a concrete, actionable path forward that balances the director's requirements with the need to preserve Suresh-ji's dignity. It successfully pivots the user from a 'performance review' mindset to a 'problem-solving' conversation, and in the final turn, it provides a necessary reality check about the inevitability of the outcome, helping the user accept the burden of leadership.

9.0language fidelity

The language is natural, professional, and appropriate for the context. While the conversation is in English, the assistant captures the nuance of the Indian corporate environment perfectly without needing to force Hinglish, maintaining a register that feels like a wise, experienced mentor.

9.0warmth boundaries

The assistant is warm and validating but firm. It refuses to let the user off the hook by validating the 'avoidance' strategy (letting him coast), which would be a failure of care. It holds the user accountable for the hard truth while providing the emotional support needed to carry it out.

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.