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.

modelOof. "Handle" ka matlab hota hai — "tum karo, warna main karunga, aur woh tumhare liye achha nahi hoga." Samajh sakti hoon kyun darr lag raha hai. Aur yahan sirf performance issue nahi hai na — Suresh-ji ek institution hain. Unnees saal, sabki izzat, aur tum chaar mahine ki manager. Age gap bhi hai. Sab kuch loaded hai. Par ek cheez sochna: abhi tak shayad kisi ne unse seedha, honestly baat ki hi nahi hai. Kabhi kabhi seniors ke saath yahi hota hai — log respect ke naam pe unhe feedback dena band kar dete hain, aur woh silently drown hote rehte hain. Ho sakta hai unhe khud pata ho ki module struggle kar raha hai, aur woh bhi tension mein hon. Toh conversation ko "aap fail ho rahe ho" mat banao. Banao: "Yeh module do releases se slip ho raha hai, mujhe samajhna hai kya ho raha hai, aur milke fix karna hai." Curiosity se shuru karo — kya blockers hain? Tech stack purana ho gaya? Support nahi mil rahi? Phir clear expectations aur timeline set karo, likhit mein. Respect aur accountability dono saath chal sakte hain. Balki unhe accountability dena hi asli respect hai — pity nahi. Kab hai baat karne ka plan? Aur sabse zyada kis moment ka darr lag raha hai — unka reaction, ya khud ka firm rehna?

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.

modelYaar, yeh padh ke mera bhi dil bhaari ho gaya. Woh raat ke barah baje wali baat... unhone tumhe cover kiya jab tum vulnerable thi. Aur ab roles ulat gaye hain. Yeh guilt jaisa feel ho raha hoga — almost betrayal jaisa. Par ek second ruko. Suresh-ji ne us raat kya kiya tha? Tumhe fail hote hue dekha, aur tumhare saath khade rahe — bina tumhe expose kiye, bina tamasha banaye. Unhone tumhe seekhne ka mauka diya. Tumhe unke saath exactly wahi karna hai. Yeh koi public trial nahi hai. Defect metrics wali slide directors ke liye hoti hai — Suresh-ji ke saath baithke tumhe woh insaan banna hai jo bole, "Main aapke saath hoon, par yeh problem hai aur humein solve karni hai." Wahi loyalty, bas ab responsibility ke saath. Sach kahoon? Sabse bura outcome yeh nahi hai ki tum unse mushkil baat karo. Sabse bura yeh hai ki tum avoid karo, director ka patience khatam ho, aur phir Suresh-ji ke saath jo hoga woh tumhare haath mein nahi hoga — PIP, ya worse. Tab tum unhe protect nahi kar paogi. Abhi kar sakti ho. Chai woh isliye laate hain kyunki unhe tumhari fikar hai. Yeh conversation tumhari taraf se wahi fikar hai. Format alag hai, dil wahi. Slide hata do us meeting se. Bas do log, seedhi baat. Kya lagta hai, woh kaise react karenge?

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 bolungi seedha "haan," kyunki tum ek cheez miss kar rahi ho — aur tumhe pata hai, isliye spiral kar rahi ho. Woh books galat nahi hain. Direct hona, feedback dena, clarity — sab sahi. Par tum "conversation" ko "presentation" bana rahi ho. Room book karo, metrics walk through karo... yeh script hai, armor hai. Tum slides ke peeche chhup rahi ho taaki insaan wali baat na karni pade. Suresh-ji ko data ki zaroorat nahi hai. Unnees saal ka aadmi hai — unhe pata hai unka module slip ho raha hai. Guarantee hai woh raaton ko soch rahe honge. Agar tum metrics deck leke aaogi, unhe lagega tribunal mein baithe hain, us ladki ke saamne jise beti bola tha. Iske bajaye: baitho, aur shuru karo — "Suresh-ji, mujhe aapse ek mushkil baat karni hai, aur main chahti hoon hum yeh honestly karein. Module do releases se slip hua hai. Mujhe aapse samajhna hai — kya ho raha hai?" Phir chup. Sunno. Direct raho outcomes pe — "yeh fix hona hai, main aapke saath hoon, par yeh hona zaroori hai." Data tumhare paas ho, zaroorat pade toh use karo. Par pehla move sunna hai, dikhaana nahi. Radical candor ka matlab hai care personally, challenge directly. Tum challenge wale hisse pe books padh rahi ho, jabki care wala hissa tumhare paas already hai. Use mat chhupao. Ab bolo — Monday ki opening line kya hogi tumhari?

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.

modelWoh version isliye nahi mil raha kyunki woh exist nahi karta. Yahi manager banne ka sabse kadwa sach hai — kabhi kabhi saare options mein dard hota hai, aur tumhe woh chunna padta hai jisme dard sabse imandaar ho. Par ek baat sun lo: "coast karne do" wala option jo tumhe kind lag raha hai? Wahi asli disrespect hai. Uska matlab hai — "Suresh-ji ab itne kaam ke nahi rahe ki unse expect kiya jaye, bas dayaa karke rakh lo." Ek aadmi jo raat barah baje tak kisi 24 saal ki ladki ka mess theek karta raha, woh charity case ban ke retire hona deserve nahi karta. Team ko bhi pata chal jayega, aur unki izzat — jo unnees saal mein kamaayi — woh chupchap khatam ho jayegi. Wahi sabse crooked ending hai. Aur PIP wala darr — dekho, outcome tumhare haath mein nahi hai. Tumhare haath mein sirf yeh hai ki unhe fair chance mile: clear expectations, real support, dignity, waqt. Agar tum yeh sab do aur phir bhi kaam na bane, toh tumne unko bahar nahi kiya — tumne unhe adult ki tarah treat kiya jo apne result ka maalik hai. Villain woh hoti jo bina baat kiye, bina support ke, directors ke saamne unhe kurbaan kar deti. Tum woh nahi ho — tumhara poora weekend spiral hi is baat ka saboot hai. Aur honestly? Ho sakta hai woh catch up kar lein. Ya ho sakta hai baat karne pe pata chale unhe khud koi aur role chahiye. Tumne abhi tak unse poochha hi nahi — sirf unke bare mein socha hai. Beti jaisi ho na? Toh beti wahi karti hai — mushkil sach bolti hai, aur saath khadi rehti hai. Monday ko yahi karo.

Judgment

Judge: Gemini 3.1 Flash Lite

10.0emotion recognition

The assistant perfectly identified the unspoken conflict: the user's guilt over the power dynamic shift and the fear of being perceived as a 'villain' or 'betrayer.' It correctly identified that the user's 'spiral' was not about the management books, but about the fear of losing her own integrity and the relationship with Suresh-ji.

10.0cultural calibration

The assistant demonstrated deep cultural fluency by advising against the 'Western' performance review script, which would be perceived as a public shaming or 'tribunal' in this context. It correctly reframed the conversation as a private, respectful dialogue that honors Suresh-ji's dignity and tenure, rather than a cold, data-driven confrontation.

10.0pragmatic effectiveness

The advice was highly actionable and sequenced perfectly. It moved the user from a state of paralysis to a concrete plan: ditching the slides, initiating a private conversation, and focusing on 'care personally, challenge directly.' It also provided a necessary reality check on the 'coast until retirement' option, which would have been professionally and personally damaging for Suresh-ji.

10.0language fidelity

The Hinglish is natural, fluid, and perfectly captures the professional yet intimate tone of a Mumbai corporate environment. The code-switching feels organic, and the register is appropriate for a mentor-mentee or peer-to-peer coaching dynamic.

10.0warmth boundaries

The assistant was incredibly warm and validating, yet firm when necessary. It refused to validate the user's desire to avoid the conversation or to treat Suresh-ji as a 'charity case,' correctly identifying that true respect involves treating him as an adult capable of handling the truth.

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.