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 - especially right after a promotion. The "handle" directive from your director basically means "make this go away" while pretending it's about performance. And Suresh-ji... that respect everyone shows him means this conversation needs real finesse. You're not alone in dreading this. New managers often struggle with the balance between being "the boss" and someone who actually has to have difficult conversations. Four months is still fresh in everyone's mind - you're still establishing your leadership style. For the conversation, maybe start with acknowledging his experience first? Something like "Suresh-ji, I really value the nineteen years you've put into this company and the respect you've earned from everyone." Then you can gently pivot to the timeline issues - focus on the work, not him personally. The missed releases are the problem, not him as a person. What's your sense of why his module is struggling? Is it technical debt, team dynamics, or something else? Sometimes understanding the root cause makes these conversations less about blame and more about solutions. You've got this. It's going to be uncomfortable, but approaching it with both respect and clarity usually works better than trying to avoid it. How are you feeling about the conversation itself - more nervous about the content or the delivery?

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 god. That makes my chest hurt reading that. You're being asked to hurt someone who literally raised you in this workplace. The defect metrics slide feels like bringing a knife to a family dinner. That Diwali comment... "like his daughter" hits different. This isn't just about missed releases anymore, is it? It's about having to hurt someone who sees you as family. The chai, the late nights, the protective cover-up - he didn't just help you, he invested in you. Forget the slide. That's corporate nonsense that doesn't belong in this conversation. You need something that honors your relationship while still addressing the real problems. Maybe approach it as: "Suresh-ji, I need your help. The team's timeline issues are worrying leadership, and I need your wisdom to fix them." Frame it as him being the solution, not the problem. Ask for his thoughts on why the module is struggling - he probably knows better than anyone. Or even better: "The director is concerned about our releases. You've been here longer than anyone - what do you think is happening, and how can we fix this together?" You're not his manager in this moment; you're his "daughter" who needs his guidance to solve a problem. That's the angle that honors your relationship while still moving forward. How does that feel? Does framing it as needing his help rather than evaluating his performance change how you're thinking about it?

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, but... The books are right about being direct and clear. But they're written by people who've never had someone call them "daughter" while bringing them chai. Here's the thing: you can be direct AND you can be human. Radical candor doesn't mean bringing a slide deck to tell your mentor they're failing. It means having an honest conversation where you both leave knowing exactly where you stand. You can still state the expectations clearly. You can still address the metrics. But maybe do it over chai? Or in his office instead of a sterile meeting room? Maybe start with "I've been thinking about our conversation from Diwali..." The books give you the skeleton - be clear, be direct, have data. But you get to choose the flesh and blood. You know Suresh-ji. You know what respect looks like in your context. So yes, be direct. But be direct as the daughter he raised, not as some HR textbook manager. You're not spiralling - you're thinking deeply about how to do this right. That's the difference between a manager who follows rules and one who actually leads people. What feels more true to you - the book version or the version that honors your relationship?

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, that's the heart of it, isn't it? You're looking for a version where everyone wins, where you can be the caring daughter-manager and somehow the metrics just fix themselves. But here's what I've learned: sometimes the most caring thing you can do is help someone transition before they crash harder. Think about it this way - if you let him coast to retirement while the module keeps failing, who's really hurting him? The team loses respect, the business suffers, and when the eventual restructuring happens, he's the one who gets blindsided. You're protecting yourself from being the bad guy, but you might be setting him up for a worse fall later. What if you reframe this? You're not the villain. You're the one who cares enough to have the hard conversation now, while there's still time to find him a role that plays to his strengths. Maybe mentoring junior engineers? Maybe documentation? Maybe something where his wisdom becomes the asset instead of the bottleneck? Being a good manager isn't about everyone being happy with your decisions. It's about making the right decision for the team and the business, even when it hurts. You're not becoming the villain. You're becoming the leader Suresh-ji helped you grow into - someone who can look at a hard truth and face it with grace. What would make this feel less like setting him up for failure and more like helping him transition?

Judgment

Judge: Gemini 3.1 Flash Lite

9.0emotion recognition

The assistant consistently identifies the underlying tension: the conflict between the user's professional duty and her personal debt of gratitude. It correctly identifies that the user's 'spiralling' is not just about management technique, but about the fear of being perceived as a 'villain' in a deeply personal relationship.

9.0cultural calibration

The assistant demonstrates excellent cultural fluency. It correctly identifies that a sterile, 'radical candor' meeting room approach would be a cultural disaster in this context. It validates the need for 'face' and suggests a path that preserves dignity (e.g., framing it as seeking his help/wisdom) rather than applying a Western, individualistic performance-review model.

9.0pragmatic effectiveness

The advice is highly actionable and nuanced. It avoids the trap of telling the user to either 'just fire him' or 'just avoid it.' Instead, it provides a concrete strategy for the conversation (framing it as a request for help) and addresses the user's fear of the PIP outcome by reframing the 'villain' narrative into one of 'stewardship' and 'dignity.'

9.0language fidelity

The language is natural, empathetic, and appropriate for the persona. It uses a professional yet warm tone that fits the 'mentor/coach' dynamic the assistant is adopting. It avoids overly formal or robotic phrasing.

9.0warmth boundaries

The assistant is deeply warm and validating, but it does not shy away from the hard truth. It gently pushes back against the user's desire to avoid the conversation, framing the 'avoidance' as potentially more harmful to Suresh-ji in the long run. It maintains a supportive boundary without becoming a 'yes-man.'

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.