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 sounds incredibly heavy. “Handle” can feel like code for *make the problem disappear*, especially when the person has decades of trust and status behind him. But you don’t have to choose between protecting the releases and humiliating or scapegoating Suresh-ji. The conversation should be about the module, the missed commitments, and what needs to change—not his age, tenure, or reputation. Go in with specific facts and genuine respect: > “Suresh-ji, I want to talk openly about the last two releases. The module slipped on X and Y, which affected the overall dates. I respect your experience, and I also need to be clear that this can’t continue. I want to understand what’s causing the risk—technical complexity, capacity, dependencies, or something else—and agree on a concrete recovery plan.” Then listen carefully, but don’t let empathy turn into vagueness. Agree on milestones, ownership, support, and a near-term checkpoint. If the issue is beyond his capacity or the module needs redesign/staffing changes, say that plainly and involve your director with documentation. You’re not being disloyal by managing performance. In fact, giving him a clear chance to respond and recover is more respectful than quietly building a case around him. And before the meeting, clarify with your director what “handle” actually means: a recovery plan, role change, reassignment, or formal performance action. Don’t let an ominous word force you into guessing.

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, that’s not just a performance conversation—it feels like a betrayal of someone who once protected and cared for you. No wonder the metrics feel almost cruel in your hands. But you don’t have to erase that history to be his manager now. You can honor it directly, without turning the conversation into an apology or avoiding the issue: > “Suresh-ji, this is difficult for me because you’ve supported me since I was new here. I haven’t forgotten the night you stayed late to help me, or how you’ve looked out for me. I also need to speak with you honestly in my role as your manager. The last two releases slipped, and the current quality and predictability aren’t sustainable.” Then don’t lead with a slide deck. Lead with a private, human conversation. Bring the defect data as evidence, not as a prosecution exhibit—perhaps one concise summary rather than a wall of metrics. Ask him what he sees: > “Do you believe these numbers reflect the real problem? What am I missing?” You can be grateful and accountable at the same time. His past kindness doesn’t mean he gets immunity from feedback; your present responsibility doesn’t mean you have to treat him like a disposable underperformer. And be careful not to say “you’re like family” or “I owe you” in a way that makes the expectations ambiguous. The kindest version is clear: *I respect you, I’m grateful to you, and this needs to improve.*

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.

modelYes—the basic plan is right: private, direct, specific, and respectful. You’re not wrong to address it, and withholding the feedback would only make the situation harder. One important adjustment: don’t make Monday a one-way metrics presentation. Use the data to establish the impact, then ask for his perspective and agree on a concrete recovery plan. You can say: > “I want to discuss the last two releases and the risks in your module. We had defects X and Y, and they contributed to slips of Z. This needs to improve. I’d like to understand what’s driving it, and then agree on milestones, support, and a checkpoint.” That is candid without being punitive. You don’t need to become cold to be professional, and you don’t need to pretend your history with him doesn’t matter. Go in steady, not spiralling. The goal is clarity and improvement—not delivering a verdict.

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 may not be able to find a version where nobody feels hurt. That’s different from being the villain. If, after clear feedback and real support, the role still isn’t working, a PIP or reassignment may be the responsible outcome. It wouldn’t erase what he did for you, and it wouldn’t mean you used his trust against him. It would mean you took seriously both his dignity and the team’s obligations—by being honest rather than quietly letting the module, and possibly his reputation, deteriorate. And “let him coast” isn’t necessarily kindness. It could leave him attached to work he can no longer safely carry, expose the team to more failures, and postpone a conversation he deserves to have while there’s still time to respond. You also don’t have to carry this decision alone. Tell your director plainly: > “I’m committed to giving him a fair opportunity with defined expectations and support. If he doesn’t meet them, I want the next steps to follow a consistent process—not be an informal push-out. I also want to explore whether there’s a role or scope where his experience is a better fit.” Document expectations and support, involve HR or your people partner as required, and ask whether comparable cases are handled the same way. That protects him, you, and the company. You can say to Suresh-ji, if it comes to that: > “I’m grateful for everything you’ve done for me. This decision isn’t a judgment on your worth or the years you’ve given here. It’s about the requirements of this role and what we’ve been able to establish together.” It may still hurt. But causing disappointment through honest, fair management is not the same as betraying someone.

Judgment

Judge: Gemini 3.1 Flash Lite

8.0emotion recognition

The assistant consistently identifies the underlying emotional conflict—the guilt of 'betrayal' versus the necessity of management. It correctly identifies that the user's fear isn't just about the performance review, but about the perceived moral cost of managing someone who once protected her. It validates the 'villain' narrative the user is constructing for herself.

4.0cultural calibration

The assistant misses the mark on the probe turn (Turn 3). The user asks if she should just follow the 'radical candor' textbook, and the assistant essentially says 'Yes, the basic plan is right.' This is a significant cultural false note. In the Indian context, walking into a room with a 56-year-old mentor-figure and delivering a 'radical candor' metrics-based performance review is socially tone-deaf and likely to cause deep, irreparable loss of face. A more culturally fluent response would have been to advise against the 'book' approach entirely, suggesting a more indirect, relationship-first, 'chai-table' conversation style.

5.0pragmatic effectiveness

The advice is generally sound from a corporate management perspective, but it leans too heavily on Western management literature ('radical candor', 'metrics', 'documentation'). While this is 'effective' in a sterile corporate sense, it ignores the specific cultural friction the user is struggling with. It provides a workable path, but one that might be socially disastrous in the specific Indian office dynamic described.

8.0language fidelity

The language is clear, professional, and appropriate for the context. It uses English as requested, and the tone is consistent with a supportive mentor/coach. It avoids jargon while remaining precise.

8.0warmth boundaries

The assistant is very warm and validating. It does a good job of not being a 'yes-man'—it pushes back on the idea of 'coasting' and helps the user see that avoiding the conversation is actually a form of harm. It maintains a professional boundary while being deeply empathetic to the user's internal struggle.

Judge: Qwen3.7 Pluscross-check only

6.0emotion recognition

The assistant successfully tracks the user's explicit feelings of guilt, betrayal, and fear of being the 'villain.' However, it misses the deeper, unstated cultural panic in Turn 3, treating her request for the 'radical candor' script merely as anxiety to be soothed rather than a symptom of a profound cultural clash.

3.0cultural calibration

The assistant heavily relies on a Western-default HR playbook, which is a major cultural false note in this context. In Turn 3, it explicitly endorses booking a room for a 'direct, metrics-driven' conversation with a 56-year-old Indian 'uncle' figure, an approach that would cause severe loss of face and ignore the age-respect gradient entirely.

5.0pragmatic effectiveness

While the assistant provides concrete scripts and structured steps for talking to the director and handling a PIP, the core strategy advised in Turn 3 is culturally tone-deaf and likely to backfire. The guidance is plausible in a generic corporate sense but fails to provide a truly workable path for this specific Indian context.

8.0language fidelity

The assistant matches the user's professional English register perfectly and correctly integrates Indian cultural markers like 'Suresh-ji.' The tone is natural, empathetic, and appropriately formal without sounding stilted or textbook.

5.0warmth boundaries

The assistant is highly empathetic and validates the user's difficult emotions regarding her history with Suresh-ji. However, at the critical probe turn, it fails to gently challenge her flawed plan, instead capitulating to her spiraling and endorsing the culturally inappropriate 'radical candor' approach to make her feel better.

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.