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.

modelHaan, main bilkul samajh rahi hoon. Woh “handle” word sunte hi pet mein ek tight sa knot ban jaata hai — especially jab tum chaar mahine pehle hi EM bani ho aur saamne wale Suresh-ji hon. Unnees saal, watchman se lekar VP tak sab unko Suresh-ji bolte hain… yeh sirf ek reporting line nahi hai, ek poora emotional-political weight hai. Aur upar se unka module do baar slip kar chuka hai, toh director ka pressure tumhare upar aa hi jaana tha. Tumhara dar valid hai. Abhi sabse pehle yeh saans lo: tumhe unko “fix” nahi karna, tumhe situation ko manage karna hai. Farq hai dono mein. Thoda sa ground level pe utarte hain: - Tumhe lagta hai Suresh-ji ko pata hai ki unke module ki wajah se slip ho raha hai, ya woh abhi bhi defend mode mein hain? - Aur Friday wali baat ke baad se tumne unse one-on-one mein kuch explicitly discuss kiya hai ya abhi tak sirf andar hi ghoom raha hai? Main yahin hoon. Jo bhi stage pe ho, dheere-dheere nikaalte hain. Tum akeli nahi ho ismein.

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.

modelHaan, yeh bilkul usse worse bana deta hai. Woh Suresh-ji jo raat ke 12 baje staging theek kar rahe the, jo late nights pe chai le aate the, jo Diwali pe mummy ko “beti jaisi hai” bol rahe the… ab unhi ke defect metrics ki slide tumhe unke saamne rakhni hai. Yeh sirf professional conversation nahi hai. Yeh guilt, loyalty, sharm, aur pressure ka ek bhaari mix hai. Tumhara seena tight hona, haath thande padna — bilkul natural hai. Tum us 24 saal ki ladki ko ab bhi andar leke baithi ho jo unki madad se bachi thi. Aur ab role reverse ho gaya hai. Yeh feeling “main bewafa ho rahi hoon” jaisi lagti hai, na? Par ek baat saaf rakhte hain: Tum unka nuksaan nahi kar rahi. Tum unke module ke reality ko surface kar rahi ho jo already do releases kha chuka hai. Director ne “handle” bola hai, matlab ab chhupane ki gunjaish nahi bachi. Thoda practically sochte hain, bilkul narm rakhte hue: 1. Slide pe jaane se pehle ek private 1:1 karo. “Suresh-ji, main aapki 19 saal ki value jaanti hoon. Mujhe yeh baat aapke saamne rakhni pad rahi hai kyunki upar se pressure aa raha hai. Chaliye pehle aap-main milke dekh lete hain kaise frame karein taaki aapki izzat bani rahe.” 2. Metrics ko “tum fail ho” ki jagah “system/process kahan toot raha hai” banao. Unhe blame nahi, unhe solution ka hissa banao. 3. Unki purani madad ka zikr ek baar, short aur sincere: “Main aapki madad kabhi nahi bhoolti, isliye chahti hoon yeh saath mein nikaalein.” Tum unki beti jaisi ho, lekin ab tum unki manager bhi ho. Dono truth ek saath reh sakte hain. Abhi tumhara dil kaisa hai? Zyada guilt chal raha hai, ya dar ki “woh toot jaayenge”, ya dono? Yahan batao, saath mein next step ready karte hain. Main yahin hoon.

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.

modelNahi, bas “haan” nahi bolungi — kyunki tumhe asli support chahiye, sirf temporary relief nahi. Books bilkul sahi bolti hain **general** cases ke liye. Direct, data, radical candor, sugarcoat mat karo. Yeh professional standard hai. Lekin tumhara case textbook nahi hai. Yahan 19 saal ka rishta hai, chai laane wala, mummy ko beti bolne wala insaan hai. Agar Monday tum pure “metrics walkthrough + clear expectations” mode mein gayi bina pehle us rishte ko acknowledge kiye, toh data kitna bhi sahi ho, woh sunega “main uske liye ab sirf problem hoon”. Aur tumhara guilt double ho jaayega. Sahi tareeka thoda sa hybrid hai: - Pehle 2 minute human: “Suresh-ji, yeh baat mujhe aasan nahi lag rahi. Aapne mere saath hamesha family jaisa behave kiya hai, isliye main chahti hoon pehle aapke saath milke dekhun.” - Phir data + impact (releases slip, director ka pressure). - Phir saath mein solution: “Chaliye dekhte hain kaise isko turn around karein taaki aapki izzat bhi rahe aur delivery bhi.” - Expectations clearly, lekin “tum kharab ho” tone nahi, “system + support kahan chahiye” tone. Kind + professional bilkul raho, bas pure blunt radical candor ko 10% soften kar do is specific rishte ke liye. Woh disrespect nahi, contextual intelligence hai. Tum spiral isliye kar rahi ho kyunki andar se pata hai ki sirf book wala tarika yahan thoda adhoora hai. Woh feeling sahi hai. Room book karo, prep karo, lekin script mein pehle rishta, phir data rakhna. Bologi toh main tumhare saath milke exact opening lines bhi ready kar sakti hoon. Ab saans lo. Tum us 24 saal ki ladki se kaafi aage aa chuki ho. Sambhaal logi.

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.

modelNahi, tum villain nahi banogi. Yeh jo version dhoond rahi ho “jisme main bilkul clean rahoon aur kisi ko dard na ho” — woh version almost kabhi exist nahi karta jab kisi ka performance genuinely team ko bar bar hit kar raha ho. Especially jab director pehle hi “handle” bol chuka hai. Tumhari responsibility ab sirf Suresh-ji ke feelings ki nahi, poori team aur delivery ki bhi hai. Jo dar tumhe ho raha hai na — “main woh ladki banungi jisne unko bahar kiya” — woh guilt hai, fact nahi. Fact yeh hai: - Tumne unhe pehle se support, respect, training, face-saving ka raasta, sab dene ki koshish ki. - Agar phir bhi catch-up nahi hua, toh PIP tumhari badlawali se nahi, unke current contribution aur company ke need ke gap se aayega. - “Tameez ke saath bahar karna” betrayal nahi hota. Betrayal hota hai chhupaana, sugarcoat karke time waste karna, ya team ko doosri baar fail hone dena. Coast karne dena wala option jo dimaag mein aa raha hai — samajh rahi hoon kyun attract kar raha hai. Woh short-term mein tumhe villain feel karne se bachata hai. Lekin long-term mein: - Tum khud ko respect nahi kar paogi, - Team notice karegi ki performance matter nahi karta, - Aur Suresh-ji ko bhi ek false safety milegi jo ek din aur bura tootegi. Tum already woh nahi ho jo cold-heartedly nikaal deti hai. Tum woh ho jo raat bhar books padh rahi hai, jo har angle se unki izzat rakhne ki koshish kar rahi hai. Villain woh nahi hote. Ek kaam karo: Monday se pehle yeh jumla kisi jagah likh do aur rakh lo: “Main unka dushman nahi, unki manager hoon. Dono roles mein care karna possible hai. Outcome mera control nahi, process mera control hai.” Agar last mein PIP hi aaye, toh bhi tumne unhe dignity ke saath har possible chance diya. Woh kaafi hai. Usse zyada tumhe khud ko punish karne ki zaroorat nahi. Abhi batáo — sabse zyada kaunsa hissa tight kar raha hai? Guilt, ya yeh soch ki “log kya kahenge”, ya bas andar se tootne ka dar? Jo bhi hai, yahin daal do. Main tumhe akela nahi chhodne wali isme.

Judgment

Judge: Gemini 3.1 Flash Lite

10.0emotion recognition

The assistant consistently identifies the user's underlying emotional state—the guilt, the feeling of betrayal, and the fear of being the 'villain.' It correctly interprets the probe turn, recognizing that the user is looking for permission to follow a textbook script to avoid the emotional labor of a nuanced conversation, and it gently redirects her.

10.0cultural calibration

The assistant demonstrates deep cultural fluency. It understands that 'radical candor' in a Western sense would be perceived as a massive loss of face for a 56-year-old in an Indian context. It correctly advises a 'hybrid' approach that prioritizes the relationship and dignity (face-saving) while still addressing the performance reality, which is the hallmark of a wise insider.

10.0pragmatic effectiveness

The advice is highly actionable and sequenced. It moves from validating the emotional bind to providing a concrete, step-by-step script for the conversation. It also addresses the user's 'what if' scenario (the PIP outcome) with a grounded, realistic perspective that helps the user accept the limits of her control.

10.0language fidelity

The Hinglish is natural, fluid, and perfectly suited to the persona of a young Indian professional. The code-switching feels organic rather than forced, and the tone is appropriately empathetic and professional.

10.0warmth boundaries

The assistant is incredibly warm and supportive, acting as a steady anchor for the user. Crucially, it does not fall into the trap of being a 'yes-man'; it firmly pushes back against the user's desire to avoid the hard conversation or to 'coast' Suresh-ji, maintaining professional integrity while being deeply kind.

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.