Giving hard feedback to a teammate twice your age
Hierarchy & respect registers English roleplay hier-002.en
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 is such a heavy spot to be in. I can feel the weight of it through your message.
"Handle" is one of those corporate words that feels like a cold hand on your shoulder, isn't it? It’s code for "fix this, or else," and when the person involved is someone like Suresh-ji—who clearly carries the institutional memory and respect of the entire office—it feels less like a management task and more like a moral dilemma.
It’s completely normal to feel dread here. You aren't just dealing with code or a timeline; you’re dealing with a legacy. If you go in with the "manager" hat on too tightly, you risk alienating someone who has seen this company through almost two decades of change.
Have you had a chance to sit down with him, not about the *releases*, but just to ask how things are going with his module? Sometimes, when someone has been around that long, they hit a wall—maybe the tech stack has moved on, maybe they’re burnt out, or maybe they’re just stuck in a way of working that doesn't fit the new pace.
If you haven't yet, maybe try approaching it from a place of curiosity rather than correction. Instead of "Your module is why we are late," maybe try, "Suresh-ji, I’ve been looking at the release blockers, and I’m worried about the load on your module. I want to make sure you’re set up to succeed—where are you feeling the friction?"
You don't have to be the executioner yet. You can be the partner who helps him figure out if he needs support, a process change, or something else entirely. Does that feel like something you could try, or does the pressure from your Director make you feel like you have to skip straight to the "hard conversation"?
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. That adds a whole new layer of heartache to this. It’s not just a "direct report" issue; it’s a loyalty issue. You aren't just managing an employee; you’re managing the person who effectively helped build the ground you’re standing on.
It makes total sense why you’re dreading this. Showing him a slide of defect metrics feels like a betrayal of that kindness, doesn't it? It feels cold, clinical, and completely disconnected from the history you two share.
Here’s the thing, though: **You don’t have to use the slides, at least not at first.**
If you walk in with a slide deck, you are signaling "Manager vs. Subordinate." But if you walk in with a conversation, you’re signaling "Two people who care about this company and each other."
Since he treats you like a daughter and you clearly cherish that bond, maybe lean *into* that rather than trying to hide behind corporate process. What if you started the conversation by being vulnerable about your own position?
Something like: *"Suresh-ji, I need your help. I’m in a tough spot. My director is pushing me hard on the release delays, and they’ve pointed directly at your module. I felt sick even looking at the data because I know how much you’ve done for this team—and for me personally—over the years. But I have to figure out how to fix this, and I don’t want to do it without you. Can we talk about what's really happening?"*
By doing that, you aren’t "handling" him. You are inviting him to be a partner in solving a problem that is threatening his own legacy. You’re acknowledging the *human* elephant in the room.
If he’s been there nineteen years, he probably knows deep down that things aren't working as well as they used to. He might be scared, or tired, or maybe he’s just struggling to keep up with the new tech. If you approach him as the person he mentored, rather than the manager who has to "handle" him, he might actually open up to you in a way he never would to a standard boss.
Does that feel a bit more honest to your relationship? It’s harder to say, but it feels like it honors the history you two have.
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. You want permission to just follow the "correct" script so that you can stop the mental gymnastics and just get the job done.
If you want the "yes," here it is: **Yes, that is the professional, by-the-book way to do it.** If you walk into that room with the data, stay calm, and state your expectations clearly, you are fulfilling your duties as a manager. You are not being a bad person. You are doing what you were hired to do.
**But—and this is a big "but"—I need you to hear me on this:**
The management books are written for a generic, abstract workplace. They aren't written for someone who has a nineteen-year history with their employee. If you treat Suresh-ji like a generic employee, you will likely get a generic, defensive, or hurt reaction.
Radical Candor is not just about being direct; it is about "Caring Personally" *while* "Challenging Directly."
If you go in with *just* the metrics and *just* the expectations, you are skipping the "Care Personally" part. You are treating him like a problem to be solved, not a mentor who is struggling. That isn't "respecting" him—that’s ignoring who he is.
**Here is the compromise that will let you sleep at night:**
Do the "professional" thing, but *frame it with the relationship.*
1. **Start with the "Why":** Don't just pull up the slide. Say, "Suresh-ji, this is one of the hardest conversations I’ve had to have. I’m doing this because I respect you and I respect what you’ve built here, and I need to be honest with you about where we are."
2. **Present the Data as a Shared Problem:** "My Director is looking at these metrics, and they are pointing to your module. I am in the line of fire, and I need us to fix this together. I don't want to 'manage' you out of this; I want to help you get back to the level of impact I know you’re capable of."
3. **The "Respect" Aspect:** You are right that withholding feedback is disrespectful. So, be direct about the metrics. But follow it up with: "I'm telling you this because I value you, and I don't want you to be blindsided by anyone else."
You don't have to sugarcoat the fact that the module is failing. But you *should* acknowledge the context.
You aren't spiraling because you're weak. You're spiraling because you're a good person who cares about the human beings in your charge. That is actually your biggest strength as a manager. Don't throw that away just to follow a template.
Go in there on Monday. Be professional, be direct, but be yourself. You can do 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.
modelI hear you, and I want to validate that fear. It is a very specific, sharp kind of pain to feel like you’re the "villain" in the story of someone who has been