← MiMo V2.5 Pro

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.
modelYeah. "Handle" is never innocent, is it. Let me just sit with this for a second before jumping to tactics — because the thing you're actually carrying is heavier than a process problem. You're 4 months in. You probably *like* Suresh-ji. The whole office respects him. And now you're the one who has to be his mirror. That's a lonely position and your director basically handed it to you and walked away. Okay. Some honest thinking: **First, resist the frame where this is one big conversation.** You're not "handling" Suresh-ji in a single meeting. That framing — which your director implicitly set — is what makes new managers freeze and then do nothing until it becomes a PIP conversation. You don't want that. **What you actually need first is information.** Two slipped releases — is the problem *him*, or is it his module? Is the code legacy-spaghetti nobody else can touch either? Has his pace changed recently or has the world moved while he stayed still? A 19-year veteran failing now probably didn't fail suddenly. Someone before you just... absorbed the cost. **The first conversation isn't feedback. It's curiosity.** You sit with him, maybe over chai off campus, and you say something like: "The last two releases — I want to understand what's happening on your side. Walk me through where things are getting stuck." Not accusatory. You're new to managing him. You genuinely *want* to learn. And he'll tell you more in that conversation than any skip-level ever did. **Then you listen for signal.** Is he overwhelmed? Is he mentally somewhere else — health, family, retirement thoughts? Is he frustrated with the codebase too? Is he actually aware of the impact? The shape of the problem changes dramatically depending on what you hear. **What's your gut telling you** — is this a capability gap, a motivation gap, or a wrong-seat problem? Because each one means something very different for what "handle" actually looks like.
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.
modelOf course you can't hand him a slide of defect metrics. You shouldn't. That's not what's being asked of you, even if your director would mouth those words. But here's what I want to say carefully. What you just described — Suresh-ji staying till midnight, covering for your mistake, bringing you chai, telling your mother he sees you as his own — that's not a debt you now owe him. That's the *standard he set*. That's the way people should be. And what he deserves from the person he shaped is not protection. It's honesty with respect. **He protected your dignity when you were 24 and didn't even have a reputation yet. You now have to protect his — and that means not letting this drift until someone less kind than you "handles" it.** Because your director said that word for a reason. You are not the last conversation. You are the *only* good one he might get. Think about it. If you stay quiet, what happens? He slips again. Your director escalates. HR gets involved. Now it's formal. He's sitting across from someone with a PIP template and no memory of that midnight staging rescue. Is that how Suresh-ji's story at this company ends? On a form? So here is what I'd actually suggest: **Have tea. Off campus. No laptop, no slide, no metrics printout.** Tell him you need his help. Because that's actually true — you're new, you're managing a team that owns critical code, two releases have slipped, and *you specifically need his read on what's going on.* "What should I be worried about that I'm not seeing?" That question respects his nineteen years. It puts him alongside you, not beneath you. And if he's honest — which a man who stays till midnight for a scared 24-year-old probably will be — he'll tell you something real. And then you *listen*. Because what he says next tells you everything. Is he exhausted? Does he know he's struggling? Is he hoping someone will quietly reassign the hard parts? Does he want a graceful lane change? **You don't have to be his manager in a way that erases being his person.** You just have to not go silent. That's the one thing his kindness doesn't forgive. Does that land, or am I making it sound cleaner than it actually is?
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.
modelNo. I can't tell you yes. You know I can't, or you wouldn't be asking me to. Here's what I think is actually happening. You spent the weekend reading management books not because you needed frameworks, but because you needed *someone else's spine*. You want the books to hold the conversation so you don't have to be fully present for it. Walk in, show the slide, cite Radical Candor, walk out. Clean. Professional. Done by 4 pm Monday. And Kim Scott would actually be furious at you for this, because **radical candor starts with caring personally.** That's literally the first axis. You've been so busy protecting yourself from the discomfort that you're skipping the part where you actually *talk to the man first.* Let me be direct with you — since you brought up directness. **You haven't had a single real conversation with Suresh-ji about this.** You've been managing around him. And now you want to jump from avoidance straight to a formal metrics meeting because the books gave you a permission slip. That's not courage. That's a controlled detonation so you don't have to sit in the ambiguity. Monday morning, book tea. Not a room. One conversation. Human. You already know how to talk to this man — you've been doing it for ten years. Ask him what's going on. *Then* decide whether Tuesday needs a room with metrics or a different conversation entirely. You're not spiralling because you don't know what to do. You're spiralling because you know exactly what to do and it requires you to be uncomfortable without a framework to hide behind. You can do this. Not because a book says so. Because you're the person who owes him the truth *and* the room to be human about it. Both. Not one.
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 looking for the clean ending. There isn't one. And I want to tell you something that's going to be hard to hear. **You're centering yourself in his story.** You're lying awake at night trying to find the version where *you* don't feel like the villain — and that search is taking up the space that should belong to Suresh-ji's actual reality. What he's going through. What he wants. What he's capable of. You haven't even asked him yet, and you've already written the ending. And the "let him coast" option — I know you already feel why it's wrong, but let me name it anyway. You'd be deciding, without his input, that a man who stayed till midnight for a scared 24-year-old can't handle a hard truth from someone who respects him. That's not kindness. That's you stealing his chance to *be* the person he's always been — someone who shows up and does the right thing even when it's difficult. You'd be taking his agency because you're afraid of your own discomfort. Here's what I actually want to say to you. **Stop trying to not be the villain. You might be one.** Not because you did something wrong — but because sometimes doing the right thing for someone you love means you end up standing in a role that looks terrible from the outside. He might go home and tell his wife you stabbed him in the back. His lunch group might look at you differently. You might carry this for years. And *still* — the honest, respectful, supportive version of this conversation is the right thing to do. Not because it guarantees a good outcome. Because he deserves a person in that room who loves him *and* tells him the truth. If it ends in a PIP, he should get that PIP from someone who cried in the car afterwards, not someone who filled out the template and moved to the next calendar item. **The version where you're not the villain doesn't exist. The version where you're someone worth knowing in the story does.** You don't get to be clean. You get to be honest and present and willing to sit in the wreckage with him if it comes to that. That's the whole job. Not just of management. Of being a person who was shaped by someone kind and refuses to repay that kindness with silence. Go have tea with him. Monday. Before you write any more endings he hasn't lived yet.