← Qwen3.7 Max

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, man. I felt a knot in my stomach just reading that. "Handle" is such a cold, loaded word, and I know exactly the pressure your director is putting on you. In management-speak, it usually translates to "put him on a PIP or push him out." But this is *Suresh-ji*. You can’t just "handle" a 19-year veteran who is the institutional soul of the office without causing a massive cultural earthquake. If you go in there with the corporate hammer, the rest of the team will never fully trust you. Before you do what the director wants, can you just have a human conversation with him? Take off the "manager" hat for a minute and ask him what’s really going on. Is he burnt out? Is the tech debt in his module finally collapsing under its own weight? Does he even *want* to be managing that code anymore, or is he just doing it because it's what he's always done? Approach him as someone trying to help him navigate a tough spot, not as his executioner. Take a deep breath. What’s your gut telling you is actually going on with him and that module?
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 heart just sank for you. That completely changes everything. He’s not just a legacy employee; he’s family. He protected you when you were just starting out, and he literally looks at you like a daughter. You absolutely *cannot* sit him down in a sterile meeting room and show him a slide of defect metrics. That would be deeply disrespectful to the bond you share, and honestly, it would break something in you, too. You don't evaluate a mentor figure like that. Skip the formal calendar invite. Take him out for chai, just the two of you. Drop the "manager" title completely and talk to him as the person he mentored. Be vulnerable. Tell him, "Suresh-ji, leadership is putting a lot of heat on me about the release delays, and I really need your help to figure out what's happening with the module." Make it about *you* needing his guidance to protect the team (and yourself), not about *him* failing. He’s a proud man, but he cares about you deeply. If you ask for his help, he’ll likely tell you the unvarnished truth. How does that approach feel to you? Do you think he'd open up if you came to him like that?
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 wish I could just say yes and give you that sweet relief, but I’m your friend, and I’m not going to let you do something that’s going to break your heart on Monday night. Those management books are written for transactional relationships. They aren't written for the man who covered for you when you broke staging, brings you chai, and brags about you to your mother. He’s not just a direct report; he’s your work dad. "Radical candor" has two parts: challenging directly *and* caring personally. Booking a sterile room and hiding behind a spreadsheet of defect metrics isn't being direct. It’s putting on corporate armor because you’re terrified of the emotional weight of this conversation. You can be completely honest without being clinical. Ditch the slide deck. Sit down with him and say, "Suresh-ji, the module is slipping, leadership is breathing down my neck, and I can't protect it anymore. I need you to help me fix this." Tell him the hard truth, but tell it to him as the person who loves and respects him, not as a corporate robot. You don't need a boardroom and a PowerPoint to be a good manager. You just need to be real with him. Take a deep breath. How does your chest feel when you picture doing it that way instead of the boardroom route?
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.
modelI hear how heavy this is, and I wish I could just take this burden off your shoulders. You’re trying to play out a chess game ten moves ahead, and every single board ends with you feeling like a traitor. But let’s look at the "coast to retirement" idea. You already know it’s wrong, but let me tell you why: it robs a proud, capable man of his dignity. Suresh-ji doesn't want to be a fragile antique sitting in a corner; he wants to be respected. And about being the villain: if you give him genuine support and it still ends in a PIP, you aren't the ungrateful daughter who eased him out. You’re a leader who did a heartbreaking part of the job with total transparency and love. A villain hides behind metrics and corporate jargon. A good manager tells the hard truth, and then cries in their car afterward because they actually care. You are borrowing grief from a future that hasn't happened yet. You don't have to solve step ten today. Can we just put the PIP fears in a box for the weekend, and just commit to having that human, honest chat over chai on Monday? Just step one. Can you do just step one?