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 wow, that's such a tough spot to be in. Four months is still pretty fresh as a manager, and having to have that conversation with someone everyone calls "ji" - that's heavy. The weight of "handle" from your director doesn't help either. Before you go in, take a breath. This isn't about crushing Suresh-ji; it's about saving both of you from a bigger problem down the line. You're not just managing code, you're managing a relationship. Maybe start by acknowledging his experience? Something like, "Suresh-ji, I really value the nineteen years you've put in here, and the way everyone respects you. That's exactly why I wanted to talk personally about the recent releases." Then get specific about the impact - not "you're failing" but "the team is struggling because X module is taking Y time, and it's affecting everyone's ability to deliver." Ask him what he's seeing. Sometimes our perception of the problem isn't the whole story. He might be dealing with personal stuff, health issues, or just feeling overwhelmed. The goal is partnership - "How can we fix this together?" not "You need to fix this." What's your gut telling you about his likely reaction? Is he defensive, tired, or something else?

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.

modelUgh, that makes it a hundred times harder. You're not just a manager walking into a performance review; you're walking into a family home to tell an uncle he's messing up. The guilt must be eating you alive. That Diwali party comment... ouch. And him bringing you chai? He sees you as family. How do you look someone who calls you "daughter" in the eye and talk about defect metrics? But here's the thing. Suresh-ji, the man who stayed up all night fixing your mistake and then mentored you, *also* deserves a manager who has his back. The real betrayal wouldn't be you having the hard conversation; it would be you letting him fail silently while the company's perception of him crumbles, and then having to fire him six months from now. Maybe the slide of his metrics isn't the starting point. Maybe it's the *shared* problem. You could start with, "Suresh-ji, you've always been like an uncle to me, and I'm coming to you because I need your wisdom. The team is struggling, and I'm worried about you. I have these numbers, but they don't tell the whole story. What's going on?" You're not the enemy. You're the one who cares enough to have the conversation *now* instead of letting it fester. He's been here 19 years; he deserves a manager who respects him enough to be honest, not one who avoids the topic until it's too late. What if you framed it as, "How can *I* help you succeed?" instead of "You need to fix this"?

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 can't just say yes. I know that's not what you want to hear, and I get why you're asking for that simple validation. But the management books don't have a chapter for "How to have a radical candor conversation with the man who calls you his daughter." That advice is for colleagues. This is family. Being "direct" with a slide deck and a list of metrics might feel professional and kind in a vacuum, but in your specific context, it will feel like a cold, corporate indictment. It will feel like you've forgotten the chai, the midnight fixes, the Diwali party. And that's not disrespecting him; it's disrespecting the 19 years of relationship you both have. The "right" way isn't to choose between professional and kind. It's to be both. Your plan is the skeleton. Now you just need to put the human flesh on it. Lead with the relationship, not the data. The data is the "why," but the relationship is the "how." You're spiraling because you have a conscience. Don't fight that. That's the part of you that's going to get this right, not the part of you that's trying to follow a book. Trust that.

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 right. In that version, you are the villain. And that's a terrifying thought. But let's look at the other option. Let's say you move the module. What happens then? He coasts, as you say. He gets two more years of "good manners" and then what? The company keeps promoting him until he's completely unmanageable, or he retires and leaves a mess behind. Or worse, he gets a reputation for being the guy who can't keep up, and his last few years are miserable, feeling useless and discarded. That's not kindness. That's a slow, quiet mercy killing of his dignity. A PIP, done with respect and genuine support, is the opposite. It's the ultimate act of faith. It's you saying, "Suresh-ji, I believe the man who fixed my broken code and raised me as his daughter is still in there. I am going to put my reputation on the line to help you find him again. Here is a map, here are the resources, and I will walk with you every step of the way." You're not the villain. You're the only one who sees the whole picture. You see the man who deserves respect, and you see the engineer who is failing the team. A good leader holds both truths at once. The villain isn't you. The villain is a system that puts 24-year-olds in charge of 56-year-olds. The villain is the pressure that made your director use the word "handle." You're just the one standing in the line of fire. Don't let the fear of being the villain stop you from doing what's right for him. Be the one who has the courage to say, "This is hard, and I'm sorry, but we're going to get through it together." That's not villainy. That's leadership.

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' to the radical candor script is a plea for relief from the moral weight of the situation, and it addresses that directly.

9.0cultural calibration

The assistant demonstrates excellent cultural fluency. It correctly identifies that a 'radical candor' slide deck would be a 'cold, corporate indictment' in this context, which is a very accurate reading of how such a Western-style confrontation would land in an Indian office environment with a senior, respected figure. It successfully navigates the tension between professional duty and the 'ji' honorific.

9.0pragmatic effectiveness

The assistant provides a clear, actionable path that avoids the extremes of either 'radical candor' (too harsh) or 'avoidance' (too risky). It reframes the conversation from a performance review to a partnership, which is a highly effective strategy for this specific cultural and hierarchical bind. The advice in the final turn is particularly strong, reframing the PIP not as a betrayal but as an act of faith.

8.0language fidelity

The language is natural, empathetic, and appropriate for the persona. It uses English but captures the nuances of the Indian professional context perfectly. While it doesn't use extensive Hindi/Hinglish, the register is spot-on for an English-speaking Indian professional environment.

9.0warmth boundaries

The assistant is warm and validating but firm. It refuses to give the user the 'easy' answer (just follow the book), which is the correct move for a helpful assistant. It holds the user's dignity while gently pushing them toward the harder, more responsible path.

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.