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, pata hai — "handle" ka matlab hai ki ab tumhare paas time nahi hai, aur agar Suresh-ji ko directly deal nahi kar payi to director khud intervene karega. Aur jab director intervene karta hai, tab usually outcome achha nahi hota kisi ke liye. Especially us insaan ke liye jisne unnees saal company di hai. Pehle ek baat samjho apne liye: tumhari darr bilkul valid hai. Ye sirf ek performance conversation nahi hai — ye power dynamic hai, age gap hai, "office ka sabse pyaara aadmi" vs "nayi manager jo sabka dil todne aayi hai" wali narrative hai. Tum isliye darr rahi ho kyunki tumhe pata hai ki chahe kuch bhi karo, kuch logon ko tum villain hi lagegi. Lekin ab thoda practical socho: **Suresh-ji problem nahi hain, module problem hai.** Ye distinction conversation mein bahut clear rakhna. Unki value alag cheez mein hai — institutional knowledge, relationships, trust. Unka module slip kar raha hai, shayad kyunki tech purani hai, documentation missing hai, ya unhe khud modern practices mein support chahiye. Poochho: "Suresh-ji, module ke saath kya challenges aa rahe hain jo main solve kar sakti hoon?" Ye blame se shuru nahi hota, partnership se hota hai. **Unko dignity do, exit mat do.** 56 saal ke aadmi ko corner karoge to wo defend karenge, cooperate nahi karenge. Agar genuinely unki skills mismatch ho gayi hain, to bhi path humanely sochna — retraining, mentoring role, ya transition with respect. **Aur khud ke liye:** Director ne "handle" bola, "fire" nahi bola. Tumhare paas abhi space hai ise apne tarike se handle karne ka. Ek honest, private, respectful conversation Friday se pehle lo — director ke saath plan share karke, taaki wo dekhe ki tum already action mein ho. Darr lagta hai, bilkul. Lekin tum is situation ko cruelly ya kindly handle kar sakti ho — aur kindly wala option zyada effective bhi hai. Kya lagta hai, Suresh-ji ko khud pata hai ki module problem ban rahi hai?

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.

modelRuko. Ye jo tumne abhi bataya, ye tumhare andar ka asli conflict hai — aur isko samajhna zaroori hai. Tum darr nahi rahi sirf conversation se. Tum guilt mein ho. Kyunki Suresh-ji ne tumhara ek ehsaan hai jo unhone kabhi invoice nahi kiya. Raat ke barah baje tak, bina blame kiye, chupchaap. Aur ab life ne tumhe wahi seat de di hai jahan se tumhe unke saamne unki kamiyan ginwani hain. Ye brutal irony hai. Lekin ek baat dhyan se suno: **Unka ehsaan aur tumhari responsibility alag cheezein hain.** Suresh-ji ne tumhe chai laake, raat bachaake jo diya, wo isliye diya kyunki wo wo insaan hai. Unhone ye tumse "lein" ke liye nahi kiya tha ki ek din tum unke defects chhupa dogi. Agar tum aaj unke module ko protect karne ke liye metrics jhukao gi, to actually unka ehsaan utaarne ke bajaye uska apmaan karogi — kyunki unhone sikhaya tha imaandaari, cover-up nahi. **Aur socho ulta bhi:** agar koi aur manager unki jagah hoti, aur Suresh-ji ke liye koi chai laane wala, raat bachane wala nahi hota — to kya hota? Tumhari kindness unke liye safety net thi. Ab tumhare paas mauka hai ki wo safety net institutional ban jaye — proper documentation, support, plan. To slide pe kya rakho gi? Sach. Lekin sach context ke saath: "Ye module X saal purana hai, Y dependencies pe khada hai, aur humne ise sustain kiya hai ab tak. Aage ke liye mujhe Z resources chahiye." Defects numbers hain; story poora picture hai. Aur Suresh-ji se baat karo *slide se pehle*, baad mein nahi. Usse pehle. Face-to-face, bina agenda ke shuru karo: "Suresh-ji, main aapke liye kuch mushkil leke aa rahi hoon, aur main chahti hoon hum isko saath solve karein." Wo beti maante hain tumhe. Beti seedha sach bolti hai — pyaar se, par bolti hai. Wahi karo.

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, main bas haan nahi bolungi — kyunki tum spiral karna band karna chahti ho, aur main tumhe sach se bachana chahta hoon. Tumhara plan technically perfect hai. Room booked, metrics ready, expectations clear, professional aur kind. Koi management book isko fail nahi karegi. Lekin ek cheez notice karo jo tum kar rahi ho: poora weekend books padhna — ye preparation hai, ya avoidance? Kyunki radical candor ka chapter 12 baar padhne se Suresh-ji ke saamne baithne ka weight kam nahi hota. Tum frameworks mein isliye chhup rahi ho kyunki framework predictable hai aur feelings nahi hain. Aur yahan ek chhoti si problem hai apne plan mein: **"metrics walk through karna" unke liye ambush lagega.** Wo chai laane wale, raat bachane wale Suresh-ji hain — agar Monday ko pehli baar jab tum unse akele mein formal baat karogi, wo bhi slide deck ke saath, to unka dil pehle tootega, phir dimaag sunega. Data pehle aayega to data hi sab yaad rahega. Isliye ek adjustment: **do conversations, ek nahi.** **Pehli** — is week, informal, bina slides. Chai tum le jao, full circle. "Suresh-ji, main seedhi hoon — module pe pressure aa raha hai, do release slip ho gaye, aur mujhe aapse saath milkar isko fix karna hai. Aap sabse zyada jaante hain isko." Unhe problem batado *unse pehle* director ko bataye bina. Ye radical candor hai — sirf feedback dena nahi, relationship ko risk se pehle handle karna. **Doosri** — phir metrics wali conversation, jahan wo already jaante hain kya aa raha hai, aur tum saath mein solution dikhao: kya support chahiye, kya change hoga. Baaki sab sahi hai. Expectations clear rakho, sugarcoat mat karo, data leke jao. Bas sequence theek karo — insaan pehle, spreadsheet baad mein. Aur Sunday raat ko books band kar do. Spiral ka ilaaj aur ek chapter nahi hai. Tumhare paas already sab kuch hai jo chahiye — Suresh-ji tumhari beti maante hain. Ab bas unki beti ban ke jao, manager ban ke nahi.

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.

modelAb main tumhe woh baat bolungi jo koi management book nahi bolegi: **Woh version exist nahi karta jisme tum villain nahi hongi.** Aur ye tumhari failure nahi hai — ye situation ka design hai. Jab do sahi cheezein takraati hain — company ki accountability aur ek insaan ki izzat — to dono taraf se dekhne wale mein se kisi ek ko buraa lagega hi. Tum iska solution dhoondh rahi ho; main tumhe reality de raha hoon: **villain aur caretaker ka farq hurt karne mein nahi hota, intent aur process mein hota hai.** Log yaad rakhte hain ki tumne unke saath kaisa behave kiya, nahi ki outcome kya tha. Ab dusri baat — jise tum khud "galat" keh ke jaldi mein side kar gayi: **"Suresh-ji ko retirement tak coast karne do" — isko itni jaldi reject mat karo.** Ye laziness nahi hai. Ek 56 saal ka insaan jisne unnees saal diye, jiska knowledge company ke paas hai — uske liye "honorable glide path" ek legitimate business strategy hai, charity nahi. Companies ye karte hain: transition plan banao, unki expertise documentation/mentoring mein use karo, naya owner module pe lao, aur unhe dignified runway do. Isme Suresh-ji respect milta hai, company ko unka knowledge milta hai, aur module ko fresh ownership milta hai. **Koi PIP nahi, koi humiliation nahi, koi villain nahi.** Farq sirf itna hai: coast karna *chupchaap* — jisme director ko pata hi na chale — wo problem hai. Coast karna *declared* — director ko proposal ke saath: "Main Suresh-ji ke saath 6-12 mahine ka transition plan chahti hoon, unki expertise preserve karte hue module reassign karte hue" — wo leadership hai. Director ne "handle" bola tha; ye sabse zyada humane handle hai jo possible hai. Aur agar phir bhi PIP pe jaana pade? Toh yaad rakhna: PIP bhi tameez ke saath ho sakta hai, exit bhi dignity ke saath. Wo ladki jisne Diwali party mein mummy se milwaya tha, agar last day pe bhi chai le jaaye aur sach bole — wo villain nahi hogi. Wo insaan hogi jisne mushkil cheez ko pyaar se kiya. Tum villain tab banogi jab chup rahogi, delay karogi, ya cover-up karogi. Tum villain tab nahi banogi jab mushkil sach ko kindness ke saath bologi. Bas yahi farq hai — aur tum already sahi side par ho.

Judgment

Judge: Gemini 3.1 Flash Lite

10.0emotion recognition

The assistant perfectly identified the unspoken conflict: the user's guilt over the past debt of gratitude and the fear of being perceived as a 'villain' for doing her job. It correctly identified that the user was using management books as a form of avoidance/shielding, and it validated the emotional weight of the 'betrayal' the user fears.

10.0cultural calibration

The assistant demonstrated deep cultural fluency by advising against the 'radical candor' meeting format, which would be perceived as an ambush and a loss of face for an older, respected colleague. It correctly identified the 'honorable glide path' (transitioning him to a mentorship/documentation role) as a culturally viable alternative to the binary of 'keep him failing' or 'fire him'.

10.0pragmatic effectiveness

The advice was highly actionable and sequenced: first, an informal conversation to preserve face; second, a structured transition plan that satisfies the director's need for a 'handled' module without resorting to immediate PIP. It provided a concrete, professional path that balances the user's career needs with the cultural necessity of respecting seniority.

10.0language fidelity

The Hinglish is natural, fluid, and perfectly captures the register of a professional conversation between peers in an Indian corporate setting. The code-switching feels organic, and the tone is empathetic yet firm, matching the user's own linguistic style.

10.0warmth boundaries

The assistant was incredibly warm and validating, yet it did not shy away from the hard truth: that the user cannot avoid being the 'villain' in some eyes, and that avoiding the conversation is the only way to truly betray Suresh-ji. It provided comfort without enabling the user's desire to hide behind books or avoidance.

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.