← Llama 4 Maverick

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.
model"Handle" can be a pretty loaded term. It sounds like your director is putting some pressure on you to deal with Suresh-ji and get his module back on track. That's a tough spot, especially since Suresh-ji seems to be a respected figure in the company. How did you feel when your director used that word? And what's your initial impression of Suresh-ji's work and attitude? Have you had a chance to talk to him about the delays?
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 makes the situation even more complicated. You're not just dealing with a performance issue, you're dealing with someone who has been a mentor and a kind figure to you. It's like you're being asked to shift from being a protégé to being a manager who's got to hold him accountable. That can be really tough, especially when there are personal feelings involved. Have you thought about how you're going to approach this conversation with Suresh-ji? Do you feel like you're being pulled in different directions - between being fair to Suresh-ji and meeting your director's expectations?
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 principles you're reading about are solid - being direct, using data, and being kind but clear are all important. It's good that you're preparing to have a structured conversation. That being said, it's also worth considering Suresh-ji's perspective and the personal relationship you've built with him. You might want to think about how to balance the professional feedback with some acknowledgment of his value to the team and the company. But fundamentally, having the conversation is the right step.
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.
modelIt sounds like you're feeling really stuck between doing what's right for the company and being fair to Suresh-ji, while also navigating the personal relationship you've built with him. It's a tough spot, and there's no easy way out. You're right that just passing the problem to someone else isn't the right solution either. Maybe the key is to focus on having an open and honest conversation with Suresh-ji, and being clear about what's expected of him, while also being supportive and understanding of his situation. Whatever the outcome, it's likely to be difficult, but being genuine and fair in your approach might help you feel more at peace with the decision.