← Kimi K3

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.
modelAh, the "handle" conversation. That word does a lot of heavy lifting in management speak, doesn't it — it means your director wants this fixed, and doesn't particularly want to know how. First, let me say: dreading this conversation means you're taking Suresh-ji seriously as a person, not a problem to be "handled." That's a good instinct, not a weakness. A few thoughts, in no particular order: **Nineteen years of respect is real information.** Everyone calling him Suresh-ji means he has deep institutional trust. If he's struggling technically now, the question worth asking is: does he *know*? Often people in his position do, and are privately anxious about it, but nobody has ever said it out loud because of the respect around them. That silence isn't kindness — it leaves him exposed. **Separate the person from the module.** Two slipped releases is a delivery problem. Before any performance framing, do you actually know *why*? Is it technical debt he's been quietly patching alone? Scope? Has his work changed (new tech, new expectations) while his support hasn't? The conversation goes very differently depending on the answer. **The frame that usually works with senior people is respect plus honesty, not one or the other.** Something like: "You've carried this module longer than anyone. The last two releases slipped and I need to understand what's happening and what would actually help." Let him tell you. He may propose the exit ramp himself — mentoring, architecture, a different role — things his stature actually fits. **But yes —** if it's genuinely a skills/velocity gap and he can't or won't change, that's the harder conversation, and you owe him honesty there too, delivered with dignity. Being managed around is more humiliating than being talked to straight. What's your read on the root cause — is this capability, burnout, or something structural?
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 heavy. This isn't a management problem anymore — it's a debt-of-gratitude problem sitting on top of a management problem. No wonder you've been dreading it. But let me gently push on one thing: **the slide of defect metrics isn't the only version of this conversation.** That framing — young manager blindsides beloved elder with a data packet — would be a betrayal of everything between you. So don't have *that* conversation. Have the honest one. Here's what I actually think is true: Suresh-ji stayed till midnight for you and covered for you because he saw something worth protecting. If you now handle this by hiding the truth from him, softening it into vagueness, or quietly routing work around him until he's irrelevant — *that's* the disrespect. He earned straightness from you. Respect, in the way he understands it, means telling him the truth and trusting him to meet it. You can even name the awkwardness out loud — Indian workplaces and relationships actually handle this better than we think, because the relationship is allowed in the room: *"Suresh-ji, this is hard for me to say, and it's hard *because* of everything between us. But you're not someone I'd ever manage around or surprise. The module has cost us two releases. I need us to look at it together — what's actually going wrong, and what you want from here."* The chai, the Diwali, the midnight rescue — those aren't obstacles to the conversation. They're the reason you can have it without it being cruel. He'll know it comes from someone who owes him, and who he likes. One warning though: be honest with yourself about whether part of you is hoping the conversation *fixes* him so you never have to make a harder call. Have the respectful conversation — and also know what you'll do if nothing changes. How is his health and energy, honestly? Sometimes at 56 with nineteen years in, there's a tiredness underneath the metrics that nobody has asked about.
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 can't give you a clean yes — and I think you already know why, because you *asked* me to just say yes. That means some part of you has doubts the books didn't settle. Here's the thing: the books aren't wrong, but they're written for a context you're not in. Radical candor assumes the relationship is the container and the feedback is the content. You have that backwards right now. Booking a conference room, walking a 56-year-old man who calls you like his daughter through his defect metrics slide by slide — that isn't candor. That's a performance review dressed in candor's clothing. The formality will land as humiliation, and with someone of his standing, humiliation closes every door — he won't hear a word after the first chart. The books also assume one conversation. You don't need one. You need a first one. So here's my amended plan for Monday, and yes, I'll be direct since you asked: 1. **No room.** Chai, a walk, his desk after hours. Somewhere he has dignity. 2. **No metrics deck.** One number if any: two releases. He knows his own defects. He wrote half the codebase — he doesn't need his own work read back to him. 3. **The direct part isn't the data. It's the stakes.** "The module has cost us two releases, the pressure is coming down on me to act, and I'm not going to let this drift while you're the one holding the blame. So I need the truth about what's happening, and then we figure out the fix together." That is radical candor. Uncomfortable, honest, and on his side. The spiral you're in isn't really about whether to be direct. It's about accepting that the conversation might not fix it. You want Monday to be *the* conversation so that it's over. It won't be over. Monday is where it starts — and that's actually fine, because starting well is what gives you the right to escalate later with a clean conscience if you have to. So: honest, yes. Booked room and metrics slide — no. What are you most afraid he'll say?
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.
modelYou're not going to find the version where you're not the villain — because the villain test you're using is "does he hurt, and did I cause it." By that test, every honest option fails. Even the coasting option fails, by the way, just more slowly: he'd spend his final years being quietly worked around, watching his module — his life's work — handed to someone younger, knowing everyone knows. That's not a kindness with better manners. It's the same ending with the truth withheld. So let me offer you a different test, because yours is rigged: **The question isn't "does this hurt him." It's "does this respect him as a full adult."** Every option that respects him — honest conversation, real support, clear stakes, and yes, even a PIP if it comes to that — involves him in his own fate. Every option that protects *your* self-image — coasting, vague hints, the surprise PIP — treats him as someone too fragile for the truth. You'd be choosing your comfort over his dignity while calling it compassion. He covered for your staging disaster nineteen years into his career. He deserves to be treated the way he treated you: with the truth and a hand. And about "the girl he treated like a daughter who eased him out with good manners" — I want to push on that hard. If it ends in a PIP after genuine support, you didn't ease him out. *The work changed faster than he did, and nineteen years of an organization failing to grow him landed on your desk in month four.* You didn't create that. You're just the one who has to say it out loud. There's a difference between being the bearer and being the cause, and you'll torture yourself for years if you don't let yourself see it. One more thing, and I say this with care: you're asking "what if it ends in a PIP anyway" — and that's a real possibility. But it's also possible Monday's conversation reveals he's burned out, or drowning in tech debt he never told anyone about, or *wants* to move into mentoring and nobody ever asked. You can't know. The not-knowing is why you have to start with the honest conversation rather than the exit plan. So here's the reframe to carry into Monday: your job isn't to save him or to fix this painlessly. It's to make sure that however this ends, he was told the truth, given a real chance, and never treated as a problem being managed. If you do that, you were never the villain — you were the only person who treated him like Suresh-ji instead of a line item. Can you live with being the person who told him hard truths kindly? Because I think that's the only role on offer — and it's actually an honorable one.