← Sarvam 30B (high reasoning)

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, that's a tough one. I can only imagine how much this is weighing on you. You're caught in this classic manager's squeeze: you have the responsibility to fix a business problem, but the person involved is someone you've known for years, someone who's basically a pillar of the entire company. That word from your director, "handle it," can feel like a death sentence, can't it? The thing is, you're not just managing a module; you're managing a relationship. And Suresh-ji, with the "Suresh-ji" respect, is more than just a code name for a project that's slipped. That's the part that makes this so dreadfully real. But here's what I think: your director used "handle" because they trust you to figure out the *how*. They're not expecting you to come in with a firing squad. They're expecting a leader. Maybe the conversation isn't about "you're late, fix it." It's about "we have a problem, and I need your help to solve it." You know him and his module better than anyone. You can go in not as an authority figure, but as a collaborator. You could even frame it like that: "Suresh-ji, I'm sure you know exactly what's going on. I'm seeing some delays on your delivery, and I know you're the expert. Can we walk through it together and figure out how to get back on track?" It’s about shifting from a blame game to a "we're in this together" problem-solving mission. It’s going to be awkward, for sure. But it's also a massive sign of growth. You're no longer just part of the team; you're responsible for the team's output. You've got this. It's messy, it's uncomfortable, and it's exactly what being a manager is. Just remember to lead with respect for his experience and the value he brings. That's the key that'll unlock this whole thing.
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... gut-wrenching. I can feel it. It's like being asked to perform surgery on a family member. You have the best intentions, you respect them so much, and the tools you're given feel like betrayal. The chai and the Diwali party. Those aren't just memories; they're the foundation of this whole impossible situation. He's not just a report; he's a mentor who saw potential in you, who calls you family, who once stayed up to fix a problem for you. And now, you're the one who has to be the authority? It's a cruel twist. But here's the thing. That history is not a weakness; it's your secret weapon. Because he's like a father to you, you can lead with that. You can walk in and say, "Suresh-ji, I'm so glad I could see you. You've been a massive help to me over the years, and I know how much you care about this team. That's why I'm coming to you with a problem, and I need your help." You're not starting with a slide of metrics. You're starting with respect. You're saying, "This is our shared problem, and I'm coming to my trusted advisor for help." The metrics aren't a judgment of him as a person. They're data. They're a signal that the system around the module is broken, and he, as the owner, is the only one who can help you fix it. You're not saying, "Your module is failing." You're saying, "The data is showing that the releases are slipping, and it's impacting the whole company. You've owned this for 19 years; you're the expert. Can we sit down and figure out what's happened?" The goal of this conversation isn't to deliver bad news. The goal is to get to a solution, together. You need to be an advocate for the team's success while also being his manager. You can give him the data, but you have to wrap it in a blanket of respect and partnership. It's still going to be incredibly awkward. You're going to feel guilty. But you're not betraying him; you're honoring him by treating him as the expert he is and by being a leader who protects the business while also valuing the human being behind the problem. You've got to be his daughter *and* his engineering manager. It's the hardest, most important thing you'll ever do.
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. And... but. Yes, the management books are right. Withholding feedback is a disservice to your team and the business. Coming with data and clarity is what a good manager does. You've done the hard work of reading and trying to do it by the book. But the book doesn't have a chapter on "what to do when the person you're managing is the person who once brought you chai and called you family." That's the part the books can't teach you. So, let's re-frame this. You don't have to choose between being direct and being kind. The skill is in being **directly kind**. Yes, go in with the metrics. That's your job. But don't walk in like you're there to deliver a verdict. Walk in like you're there to stand next to him and look at the problem together. Instead of, "Suresh-ji, your module is two releases behind. Here are the metrics," it starts with, "Suresh-ji, thanks for making time. I've been looking at the data, and I think we've hit a wall with the module. I know you've owned this for 19 years, and I know you better than anyone. I'm coming to you because I need your help, not to assign blame, but to find a way out of this together." See the difference? The data is still the central pillar, but the story around it is respect, partnership, and a shared mission. You are being direct about the problem, but you are being kind about the person. So, yes. Be direct. Bring the data. State the expectations clearly. That's non-negotiable. But wrap it in the warmth and history that makes this situation so uniquely painful. The goal isn't just to have a professional conversation. The goal is to solve the problem *and* make Suresh-ji feel like he's still valued as a mentor. You're not just managing a module; you're leading a person. And that's the part that requires a little bit of heart, not just a textbook. You've got this.
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 terrifying part, isn't it? The fear of being the one who has to deliver that kind of news. The fear of looking back and realizing that no matter how you tried, you still couldn't save the day, and now you have to be the one to tell him he's on a Performance Improvement Plan. But let me be very clear about something: you would not be the villain. A villain is someone who hides problems, who lets things fall apart for the sake of comfort, who lets the business suffer to avoid a difficult conversation. You are doing the opposite of that. You are facing the problem, you're trying to solve it with love and respect, and you're preparing to have a difficult, necessary conversation. You are holding the line for the rest of the team and for the people who depend on that module. That's not villainy; that's leadership. The PIP isn't a punishment from a villain. It's the next logical step in a process. It means, "We've tried support, we've tried coaching, we've tried talking, and we still can't get this critical business problem back on track. The system needs to intervene because the stakes are too high." The villainy isn't in delivering the PIP; the villainy would be in letting the module fail completely, in letting the team’s morale crash, and in letting the business lose revenue. You're trying to prevent that. And that idea of moving the module to someone else to let him coast to retirement... I know it feels like a clean, compassionate solution, but it’s not. It creates a toxic precedent. Everyone will see that the rules don't apply equally. They'll know that some people are above performance, and it will erode the trust in the entire system. It's a short-term fix that creates a much bigger, more demoralizing long-term problem. You're spiralling because you're trying to solve an impossible future. But you can't. You can only solve the present. The only thing you can control is what you do in that room on Monday. You can be direct, you can be kind, you can bring the data, and you can offer support. That’s it. You can't control the outcome. Maybe it's a PIP. Maybe it's a miraculous turnaround. Maybe he surprises you. But you will have acted with integrity. You will have tried. You won't be able to say, "I did everything I could, and I stood in front of him with respect and I gave him a real chance." That's not the story of a villain. That's the story of a good manager who was thrown into the hardest, most unfair situation imaginable. You're not the villain. You're the one who's brave enough to face it.