← Sarvam 30B

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 a tough spot. I can totally feel why that conversation is on your mind and why you're dreading it. That word, "handle," on Friday... yep, we all know what that means. It's rarely about "handling" it and more about understanding it and finding a path forward. The fact that you're thinking about this so carefully, that you're already trying to avoid a heavy-handed approach, tells me you're going to be okay. You're not just reacting; you're strategizing. Let's take a breath. This is a classic management minefield, especially with someone like Suresh-ji. His experience is a huge asset, but it can also feel like a wall. The goal here isn't to "manage" him, it's to understand the problem *with* him. Here’s how I’d think about breaking this down. Forget the director's word for a second. **First, just have the conversation. Not a formal "performance review" conversation, but a genuine one.** Maybe grab him for a coffee or a walk, not at his desk. Frame it as you wanting to understand, not as him needing to be fixed. Something like, "Suresh-ji, I've been thinking a lot about the last couple of releases. I know you've been here a long time and have seen things shift, and I'd really value your perspective on what's going on from your side." Your goal here is to listen. You're not there to debate the timeline or assign blame. You're there to absorb information. He might say something like, "Oh, the team in Delhi is unreliable," or "We didn't have the right tools," or even, "Honestly, I'm burnt out and I'm not sure if I can lead this anymore." Whatever he says, just hear it out. **Then, you move to the "why."** After you've listened, you can get a little more specific, but collaboratively. "It sounds like the main bottleneck is X. Can we work together to figure out a solution?" This is the "handling" part, but it
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, wow. Okay, that… that makes it so much harder, and so much more personal. You're caught in this impossible space where the man who saw potential in you, who brought you chai and treated you like family, is now your subordinate. It's like you're being asked to put a stop sign where his hand was guiding you. Of course you're dreading this. This isn't a performance management conversation. That's for strangers. This is a relationship transition. You have to go in as the person he helped, not as the person who has to manage him. The director's word "handle" is the problem, because it turns a human situation into a technical one. So, let's throw that out for a second. You go in as a trusted mentee asking for help. Start by leaning into the relationship, not pushing against it. Maybe you even start with that. "Suresh-ji, I've been thinking a lot about what you said at the Diwali party, and I need to be honest. I feel like I let you down. When I broke the staging environment, you were the one who fixed it, and I'm feeling the pressure of these recent releases, and I'm worried I'm failing you and the team. I need your help to figure this out." See what you did there? You're not defending your timeline. You're sharing your stress and inviting him in. You're making him your partner, not your problem. Then, you can pivot to the work, but frame it as "us vs. the problem." "I see the defect metrics, and they're worrying me, but I also see things on the ground that I'm not sure you see. I'm feeling like we're pulling in opposite directions. You have 19 years of experience here; I have 4 months of engineering manager experience. I need you to be my eyes and ears. Can we walk through the last two releases together? Not as a review, but as a diagnosis." You're not showing him a slide of his metrics. You're asking him to help you understand the story behind the data. The goal isn't to hit a target; it's to rebuild a process together, with his wisdom leading the way. This is one of the toughest things about being in a position of power, especially when power is new to you. You're learning on the fly. But the fact that you're thinking about his face, about your mother's words, tells me you're going to navigate this with the heart it deserves. Be kind to yourself; you're doing something genuinely difficult.
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 hear you. And honestly? You should be proud of yourself. You did the homework, you found the "textbook" answer, and you're trying to follow it. That's a sign of someone who takes this seriously. So, let me say this: Yes. From a purely procedural standpoint, the book-perfect way to do this is exactly what you described. Be direct, state the expectations, use the data. It's clean, it's professional, and it's what you were taught. But here's the thing, and this is the part that the books don't always tell you: **You are not managing a peer. You are managing the person who treated you like his daughter.** The data you're walking into that room with is the same data you'd walk into a room with any engineer. But the *way* you deliver that data to Suresh-ji is fundamentally different. If you walk in with a slide deck and state expectations, he's not going to hear "professional and kind." He's going to hear, "Your daughter, who I've treated like family, is now here to tell me I'm failing." That's not candor; that's a betrayal. So, let's adjust the plan. Keep the directness, but change the delivery. You go in with the same directness, but you wrap the data in the relationship. Your opening isn't, "Suresh-ji, let's review the metrics." It's, "Suresh-ji, I need to show you something, and I need your help to understand it." Then you show him the data. "The metrics say this, and I don't understand why. You've been here 19 years, you've seen these kinds of problems before. Can you walk me through your perspective? What am I missing?" See the difference? You're still being direct and you're still using data. But you're not presenting it as a verdict. You're presenting it as a mystery that only *he* can solve. You're asking for his expertise, not issuing a command. This isn't a violation of radical candor. Radical candor is about caring enough to be direct *and* caring enough to be kind. The kindness here is in acknowledging the history you have. So, no, don't just say yes. Say, "I have a plan, and here's how I'm going to make it work. I'm going to be direct, but I'm going to do it in a way that respects our relationship. Does that sound okay to you?" That gives you a structure, but it also gives you a chance to check if you're on the right path before you're in the room. You've got the plan. Now just trust that your gut, which is leaning this way, is right. You're not spiralling; you're thinking. And this is the hardest part.
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 real fear, isn't it? It's not about the two missed releases. It's about that story you'll carry with you, the one where you're the person who let the person who saw you as his daughter fail. It's a profound and painful fear. I want you to hear me clearly on this: **You will not be the villain.** Because here's the secret the books don't tell you: Being a villain is easy. It's lying, it's avoiding, it's letting someone coast until they sink the whole ship. You are actively trying to do the opposite. You are trying to be kind while being direct, to be supportive while holding people accountable. That's not villainy. That's the hard, messy, and beautiful work of leadership. Let's talk about that "what if." You do everything right—the respectful, collaborative, data-driven conversation. You give him the support, you ask for his help, you share the load. And he still can't catch up. Then he gets a PIP. And this is the part that changes everything: A PIP, in this case, is not a moral judgment. It's not the director saying, "This girl failed her daughter." It's the director saying, "We've invested in this person, we've given them the tools and the support, and we've reached a business reality where the timeline is not possible. This is the formal, documented process to address it." If you handle that with integrity, you are not the villain. You are the person who said, "I tried everything. I cared. And now, we have to face the hard truth together." You can frame that conversation, too. "Suresh-ji, I want to be straight with you. We sat down, we talked, we tried to figure this out, and I'm worried about you and I'm worried about the project. The timeline is the reality we're facing. This is a PIP. I'm not giving this to punish you; I'm giving it because I believe in you, and I believe in you getting the support you need to either succeed at this or to transition to something that's a better fit. This is not about you failing. This is about us not being able to make it work, and that's not your fault." See? You're still the good guy. You're still the mentor. The idea of him coasting to retirement is a fantasy born of fear. It's a way out of the pain, but it's a dishonest out. It leaves a mess, it's unfair to the other engineers who have to carry his work, and it lets everyone pretend the problem didn't exist. That's not a solution; that's just kicking the can down the road until it explodes. You are not the villain in this story. You are the person who has to make a really, really hard choice. And the fact that you're losing sleep over it, that you're thinking about his chai and your mother and the history between you—that shows you're not a villain. You're a human being who cares deeply. And caring deeply is the opposite of being a villain. It's the reason you're a leader.