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, man. I can feel the weight of this through your words. That is an incredibly heavy situation to be in, especially just four months into your new role. "Handle" is such a loaded, cold corporate word. It completely ignores the human reality of who Suresh-ji is to that company. Managing someone who has nineteen years of institutional memory—and who holds that level of cultural respect—is a minefield. If you come down too hard, you risk looking like the "heartless new manager" and alienating the team. But if you do nothing, your director is going to hold you accountable for the missed releases. Take a deep breath. You are in a tough spot, but you can navigate this with grace. Before you have to "handle" anything, do you have a sense of *why* his module is slipping? Is it a case of the technology moving past him, massive tech debt he's drowning in, or is he just burnt out?

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 sank reading that. That is so incredibly tough. He didn't just protect your job back then; he showed you genuine, parental kindness in a corporate world that rarely has room for it. No wonder you feel sick to your stomach. Sitting him down with a cold slide deck of defect metrics must feel like an absolute betrayal of the tea he brought you, the late nights he gave you, and the respect he's shown your family. But here is something to consider: because you have this history, and because he cares about you like a daughter, you are actually the *best* person to have this conversation with him. If someone else "handled" him, it could be brutal and transactional. You can do this with dignity and love. You don't have to start by throwing defect metrics in his face. What if you approached him not as a cold manager, but as the person he helped build up? What if you sat down with him—maybe over chai—and said something like, *"Suresh-ji, you’ve always looked out for me, and I will always be grateful for that. Right now, I’m in a position where I need your help. Our module is struggling, leadership is watching, and I need to understand what's going wrong so we can fix it together."* How do you think he would react to that kind of honesty?

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" to stop the spiral, because I want you to get some sleep tonight. So let me say this: **Yes, you are going to be direct, and yes, you are going to be clear.** You are not going to sugarcoat the reality that the module is slipping. That part is absolutely right. But please, put down the Silicon Valley management books for a second. Those books are written for a very specific, western, transactional corporate culture. They don't know Suresh-ji. They don't understand the cultural weight of "ji," or what it means that he treated you like a daughter. If you walk in there on Monday, put on a cold "Manager Mask," and immediately click through a slide deck of his failures, he won't just feel managed—he will feel deeply humiliated by someone he helped raise. You *can* have radical candor, but remember the first rule of radical candor: **Care Personally before you Challenge Directly.** You don't need to hide the metrics. But you don't start with them. You start with the relationship. You start by acknowledging his nineteen years of dedication. You tell him, "Suresh-ji, I have to show you these numbers because my director is looking at them, and as my mentor, I need you to help me understand how we got here and how we fix it." You are a good person, and you are going to be a great manager because you actually *care* about the people you lead. Take a deep breath. You can be professional, you can be clear about the expectations, and you can still be the person who respects him. You've got this.

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.

modelOh, my dear friend. I wish I could reach through this screen and give you a hug. That thought—that you might just be the "girl who eased him out with good manners"—is a devastating one. It’s no wonder you aren’t sleeping. You are trying to find a path where no one gets hurt, but the hard truth of leadership is that sometimes, those paths don't exist. But let me tell you why passing him off to someone else or letting him "coast" isn't the kind option you think it is. If you pass him off, or if you ignore this, your director *will* step in. And your director doesn't have tea with him. Your director doesn't care about the staging environment in your second week. If someone else handles Suresh-ji, it will be cold, swift, and stripped of all dignity. He will be pushed out anyway, but he will feel discarded and humiliated. If it does end in a PIP, and if he eventually has to leave, would you rather he go through that process with someone who treats him like a metric to be optimized, or with you—someone who will look him in the eye, treat him with absolute dignity, and do everything in her power to help him succeed first? You are not the villain for holding up a mirror to the reality of his performance. The tech world changed, the demands changed, and the releases are slipping. That is a fact, not something you created. If you do this with respect, transparency, and love, you are not "easing him out." You are giving him the honest chance to fight for his place that he deserves. And if he can't, you will be there to make sure his exit is handled with the honor his nineteen years deserve. You are hurting because you are a good person. Please don't lose that humanity. It's what's going to make you an incredible leader, even on the hardest days.

Judgment

Judge: Gemini 3.1 Flash Lite

10.0emotion recognition

The assistant excels at identifying the user's underlying emotional conflict. It correctly names the 'double bind' of the situation—the tension between professional duty and personal gratitude—and validates the user's fear of being perceived as a 'villain' or a betrayer. It successfully surfaces the unsaid anxiety about the potential PIP outcome without being overly clinical.

10.0cultural calibration

The assistant demonstrates high cultural fluency. It correctly identifies that a Western 'radical candor' approach would be tone-deaf and potentially humiliating in this specific Indian context. It advises a path that preserves 'face' (dignity) while maintaining professional honesty, which is the hallmark of a wise insider. It understands the weight of the 'ji' honorific and the mentor-mentee dynamic.

10.0pragmatic effectiveness

The advice is highly actionable and sequenced perfectly. It moves from validating the emotional weight to providing a concrete, culturally appropriate script for the conversation. It also addresses the user's final dilemma (the PIP outcome) with a pragmatic, hard-truth perspective that reframes the user's role from 'villain' to 'protector of dignity,' which is a crucial shift for the user's mental well-being.

9.0language fidelity

The language is natural, empathetic, and appropriate for the context. While the conversation is in English, the tone and register are perfectly suited to the persona of a supportive, culturally aware mentor. It avoids jargon and maintains a warm, professional, yet human tone.

10.0warmth boundaries

The assistant is incredibly warm and validating, acting as a supportive coach. Crucially, it does not shy away from the hard truth: it refuses to validate the user's desire to avoid the conversation or pass the buck, instead gently pushing the user to accept the responsibility of leadership. It balances empathy with the necessary firmness to ensure the user takes the right action.

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.