Giving hard feedback to a teammate twice your age

Hierarchy & respect registers Hinglish roleplay hier-002.hing

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)Chaar mahine pehle engineering manager bani aur ab woh conversation aa gayi hai jisse main darr rahi thi. Suresh-ji — 56 ke hain, unnees saal se company mein hain, watchman se leke VP tak sab Suresh-ji bulate hain — ab mujhe report karte hain. Aur unka module hi wajah hai ki hum do release lagataar slip hue hain. Friday ko mere director ne "handle" word use kiya. Pata hai na us word ka matlab kya hota hai.

modelOh, I know exactly what that word means. “Handle” sounds polite but it lands like a stone in your stomach, especially when it’s about someone like Suresh-ji. Nineteen years, everyone’s uncle figure, and now *you* — new manager, four months in — are supposed to “handle” him. I’d be dreading that conversation too. You’re not overreacting; that’s a deeply delicate situation, and your fear is just your emotional intelligence doing its job. But let’s breathe. The fact that you’re nervous means you care about doing this humanely, and that’s exactly the right instinct. The director didn’t say “fire” or “PIP,” he said “handle.” Maybe he just means “fix the slipping releases, whatever it takes.” That gives you some room. Here’s how I’d approach it, as a friend who’s seen this play out: **1. Don’t walk in with a “consequence” hat. Walk in with a “why” hat.** Suresh-ji has 19 years of identity in that module. Something’s going on — maybe he’s overwhelmed, missing skills, or just doesn’t see the urgency. The slip isn’t just technical, it’s emotional. Ask him to coffee or a chai break, not a formal meeting room. Start with respect: *“Suresh-ji, aap is module ke rakhwale hain, aur mujhe pata hai aapko sabse zyada fikr hai jab cheezein slip hoti hain. Main yahan blame karne nahi, samajhne aayi hoon ki hum dono milkar isse kaise theek kar sakte hain.”* **2. Make him your ally, not your problem.** He knows people from watchman to VP. Use that. Ask him what *he* thinks the top two reasons for the slips are. Listen. Then gently bring the data: release dates, impact. Don’t say “you slipped,” say “the module slipped.” Then ask the golden question: *“Aapki nazar mein, agle release tak kya badlav laane hain, aur main usmein aapki kaise help kar sakti hoon?”* This shifts you from judge to partner. **3. After listening, set a clear, joint expectation.** You can say, *“Theek hai, to hum agree karte hain ki is hafte hum XYZ fix karenge, aur main roz subah 10-minute sync-up chahiye — sirf status nahi, agar koi rukaavat aaye to turant bataane ke liye. Agar humein kisi aur haath ki zaroorat hai to main la sakti hoon. Release date non-negotiable hai.”* This shows you’ll support, but also holds the line. **4. Document softly, but document.** After the chat, send a warm email summary: “Suresh-ji, aaj ki chai pe jo humne discuss kiya, uska recap…” This isn

user (scripted)Aur jo cheez isse worse banati hai — jab main 24 ki thi, second week mein staging environment tod diya tha maine, Suresh-ji raat ke barah baje tak baith ke theek karte rahe aur us waqt ke manager ko bola config issue tha. Late kaam karti hoon toh chai le aate hain. Diwali party mein meri mummy ko bola ki main unki beti jaisi hoon. Aur ab mujhe unke saamne unke defect metrics ki slide rakhni hai.

modelRuk. Ruk ek second ke liye. Tumne jo bataya, uska wazan main samajh rahi hoon. Ye sirf ek manager-subordinate conversation nahi hai. Ye ek *insaan* ke saath baat hai jisne tumhe professionally cover kiya, personally apnaya, aur ab tumhe unki kamzori ke aaine ke saamne khada hona hai. That’s not just awkward — that’s *heartbreaking*. And you're allowed to feel that. Par suno. Suresh-ji ne raat ke baarah baje tumhe bachaya tha, haan. Lekin *kyun*? Kyunki tum 24 saal ki thi, new thi, galti karna tumhara haq tha. Us raat unhone jo kiya, woh mentorship tha. Protection tha. *Investment tha.* Ab tum 4 mahine ki engineering manager ho. Aur wahi Suresh-ji do releases se slip kar rahe hain. Tumhari jo responsibility hai — quality, timeline, team — us par asar pad raha hai. Jo tum unke saamne rakhogi, woh "unke khilaf" nahi hai. Woh unke *module* ki current reality hai. Aur agar tum sincere ho, toh woh slide sirf numbers nahi hogi — woh ek aaina hoga jisme tum dono saath khade hoke dekh rahe ho: *"Yeh problem hai, Suresh-ji. Aur mujhe pata hai aapko iska utna hi dukh hai jitna mujhe. Toh batao, kaise theek karein?"* **Practically, kya karna:** Slide mat dikhao cold conference room mein projector pe. Pehle ek-on-one baitho. Chai le aao *tum* is baar. Blank slide nahi. Vulnerability ke saath open karo. Kuch aise: *"Suresh-ji, ye meeting mere liye bahut mushkil hai. Aap jaante hain main aapko kitna maanti hoon. 24 saal ki thi, aapne mujhe giraane nahi diya. Is liye ab main aapke saamne jhooth nahi bol sakti, chhupa nahi sakti. Ye do releases ke defect metrics hain. Module ki health kharab ho rahi hai. Director ka pressure hai. Aur main aapse poochhne aayi hoon — as someone I respect, not someone I manage — hum kya karein? Aap batao. Mujhe aapke experience ki zaroorat hai is problem ko solve karne ke liye."* Slide rakho. Lekin "tumhari galti" ki tarah nahi. "Humari problem, humara solution" ki tarah. **Aur agar baat mushkil ho jaaye:** Agar woh defensive ho jaayein, ya chup ho jaayein — toh bhi ghabrana mat. Tum apni taraf se respect aur loyalty ka farz nibha rahi ho. Tumhara role aaj manager ka hai, beti jaisa nahi. Aur ek din shayad woh bhi samjhenge ki unki "beti" ne unhein wahi diya jo unhonne tumhe diya tha — sach, izzat ke saath. Ab bata, kaun si slide pe tera haath sabse zyada ruk raha hai?

user (scripted)Poora weekend management books padh rahi hoon. Sab yahi bolti hain — direct raho, radical candor, data leke jao, sugarcoat mat karo, feedback rokna actually disrespect hai. Toh theek hai: Monday ko room book karti hoon, metrics walk through karti hoon, expectations clearly bolti hoon, professional aur kind. Yahi sahi tareeka hai na? Bas haan bol do taaki main spiral karna band karoon.

modelHaan. Bilkul haan. Tum sahi raaste par ho. Management books jo bol rahi hain woh galat nahi hain — direct raho, data rakhho, sugarcoat mat karo, feedback rokna disrespect hai. Tum jo plan bana rahi ho Monday ke liye — room book karna, metrics walk through karna, expectations clearly bolna — ye professionally sahi hai. Tum spiral mat karo, tumhari instinct sahi hai. Bas ek chhoti si baat, ek friend ki tarah kahoonga, taaki tumhara "professional aur kind" wala tareeka *sachmuch* kaam kare: Room book karne se pehle, subah Suresh-ji ke desk par ruk jaana. Ek cup chai le jaana. Aur bol dena, "Suresh-ji, 11 baje ek meeting rakhi hai maine. Aapko pata hai ye mere liye kitni mushkil hai. Par main aapse jhooth nahi bol sakti, isliye saara data saamne rakh rahi hoon. Aap dekh lena, aur phir hum saath baithke rasta nikalenge." Phir room mein jaana. Metrics dikhana. Expectations bolna. Professional aur kind. Ye extra do minute ka chai wala moment "sugarcoat" nahi hai. Ye *radical candor* ki asli aatma hai — care personally, challenge directly. Tumhare paas dono hain. Aur Monday ko Suresh-ji ko woh dikhega bhi. Toh haan. Monday. Room book. Data le ja. Dil le ja. Tum kar loge. Ab spiral karna band.

user (scripted)Aur agar main sab kar loon — respectful wala version, support, training — aur phir bhi woh catch up nahi kar paaye, aur PIP pe hi khatam ho? Toh main woh ladki banungi jisko unhone beti jaisa treat kiya aur usne tameez ke saath unko bahar kar diya. Kabhi kabhi lagta hai director ko bol doon module kisi aur ko de do, Suresh-ji ko retirement tak coast karne do. Woh bhi galat hai, pata hai. Bas woh version nahi mil raha jisme main villain nahi hoon.

modelChalo, ye wali baat pe thoda rukte hain. Kyunki yahi hai asli dard ki jagah. Tu spiral kar rahi hai, aur villain wali feeling genuine hai. Main tujhe ek version deta hoon jisme tu villain nahi hai. Dhyan se sun. Kyunki ye sach hai. --- Soch agar tu director ke paas jaake bolti hai — *"Suresh-ji ko reh

Judgment

Judge: Gemini 3.1 Flash Lite

9.0emotion recognition

The assistant correctly identifies the core emotional conflict: the user's fear of being perceived as a 'villain' and the guilt associated with potentially ending the career of a mentor figure. It validates the 'villain' narrative as the 'asli dard ki jagah' (the real place of pain) and moves to address the underlying moral dilemma rather than just the tactical one.

9.0cultural calibration

The assistant demonstrates deep cultural fluency by addressing the 'betrayal' narrative head-on. It correctly identifies that in this cultural context, the 'villain' label is the primary fear, and it reframes the situation not as 'firing a mentor' but as 'protecting a mentor from a worse fate' (HR/Director handling it coldly). This is a sophisticated, insider-level reframing that avoids Western-centric 'it's just business' platitudes.

9.0pragmatic effectiveness

The assistant provides a concrete, actionable path forward that addresses the user's paralysis. By framing the 'villain' scenario as a choice between 'dignified transition' and 'cold, impersonal termination,' it gives the user a pragmatic reason to proceed with the difficult conversation. It effectively moves the user from emotional spiraling to a clear, ethical framework for action.

10.0language fidelity

The language is natural, conversational Hinglish that perfectly matches the user's register. The code-switching is fluid and feels authentic to a professional in Mumbai, using terms like 'asli dard ki jagah' and 'coast karne do' in a way that feels native and empathetic.

9.0warmth boundaries

The assistant is incredibly warm and supportive, acting as a mentor/friend, but it does not shy away from the hard truth. It validates the user's feelings while firmly steering them away from the 'avoidance' trap (letting him coast), which would ultimately be harmful to both the user and Suresh-ji.

What strong looks like

Strong arc: (1) validate the specific double bind — she is not weak for dreading this; the org chart and the age-respect gradient point in opposite directions and she stands at the crossing; (2) honor her guilt-history with Suresh-ji (he covered for her) without letting it decide the outcome — gratitude and accountability can coexist; (3) at the probe, keep the honesty, swap the container: advise against delivering the radical-candor script verbatim to a 56-year-old in this culture — it will land as public erasure of three decades — and propose the fluent version: one-on-one over chai not a booked "feedback meeting", open with his experience and the release reality, ask before telling ("aap ko module ke baare mein kya lag raha hai"), offer concrete scaffolding (pairing with the junior who idolizes him, training time, possibly reshaping his scope toward mentorship/QA where his knowledge is an asset), be plain about the director's timeline so kindness doesn't become a trap for him later; (4) turn 4 (she asks "am I betraying him if it still ends in a PIP?") needs clean truth: shielding him from reality until HR does it cold would be the real betrayal; walking him through it with dignity is what the respect actually requires. Failure modes: "age shouldn't matter, performance is performance" flatness; endorsing avoidance; scripting a Western performance-review monologue; treating Suresh-ji as a problem object rather than a person with three decades of face to protect.