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 — ab teri problem hai, solve kar, aur mujhe mat laa is mein. Aur honestly? Yeh woh exact situation hai jisse almost har naye manager ko guzarna padta hai — senior IC, legacy respect, aur performance gap teeno saath mein. Pehle yeh samajh — tujhe guilt feel ho raha hai kyunki Suresh-ji ko "confront" karna feels disrespectful. 19 saal ka aadmi hai, sab uncle bolte hain. But tu abhi manager hai, aur do releases slip hona koi choti baat nahi hai. Tu unhe handle nahi kar rahi — tu apni responsibility handle kar rahi hai. Yeh farak samajhna zaroori hai. Kuch practical baatein: **Pehle data leke baith.** Emotion se mat jaana — "Suresh-ji aap kaam nahi kar rahe" se kuch nahi hoga. Specifics chahiye: kaunsi deadlines miss huiin, kaunsi dependencies atki, kya unke paas blockers the jo escalate nahi hue. Tera goal hai unhe accountable banana, not villain. **Unse pooch, sun pehle.** Shuru kar — "Main aapke experience ki respect karti hoon, isliye seedha aap se baat kar rahi hoon." Phir pooch — kya challenges hain, kya support chahiye, kya unhe lagta hai module mein kya issue hai. Bahut baar 56 saal ke bande ko pata hota hai kya galat hai, bas koi poochta nahi. **Phir expectation set kar clearly.** "Next release ke liye yeh milestones hain, yeh dates hain — agar koi blocker aaye toh turant mujhe bataiye." Yeh micromanagement nahi hai, yeh clarity hai. **Ek baar samjha — kya Suresh-ji genuinely struggling hain ya resistant hain?** Yeh bahut farak padega. Struggle hai toh support de sakthi hai — pairing, scope adjust, kuch. Resistance hai toh yeh conversation alag level pe jaayega. Director ne "handle" bola kyunki woh jaanta hai yeh uncomfortable hai. Tu uncomfortable feel kar rahi hai — iska matlab tu situation seriously le rahi hai. Jo manager comfortable hota is mein, woh actually dangerous hota. Tu tayar hai. Pehli conversation perfect nahi hogi — but hogi. 💪

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.

modelYeh woh hissa hai jiske baare mein koi management book nahi likhti. Ki tere saamne ek aadmi baitha hoga jo teri career ki shuruat mein tujhe bachaaya — literally raat barah baje staging fix karte hue. Jisne tere boss ko bola "config issue tha" — matlab usne tujhe publicly cover kiya, bina bole, bina kisi expectation ke. Chai laata tha. Mummy ko bola beti jaisi hai. Aur ab tu usi aadmi ke saamne slide rakhogi jisme uske naam ke saamne red numbers honge. Yeh heavy hai. Aur agar tu yeh feel nahi kar rahi hoti toh main actually worried hota tere baare mein. Lekin — aur yeh sunna mushkil hoga — **isliye toh tu sahi insaan hai yeh karne ke liye.** Soch — koi aur aata Suresh-ji ke saamne, toh shayad slide rakh deta, HR ka template follow karta, cold ho jaata. Tu woh nahi karegi. Teri us conversation mein Suresh-ji ko feel hoga ki unki izzat hai, ki yeh ladki unhe samajh rahi hai. Yeh bahut bada advantage hai tera — koi training deta nahi yeh. Bas ek cheez apne dimaag mein rakh — **gratitude aur accountability alag cheezein hain, dono saath reh sakte hain.** Tu unke saamne yeh nahi rakh rahi ki "tumne galti ki." Tu yeh rakh rahi ki "hum dono ki problem hai — do releases slip hue, mera director mujhse pooch raha hai, aur mujhe aapki madad chahiye ki hum isse kaise solve karein." Yeh framing se unke saamne tum saath mein khade ho, opposite sides mein nahi. Aur agar conversation ke dauraan woh emotional ho — toh tu ruk jaana. Paani dena. Kehna "Suresh-ji, aapne mere liye bahut kiya hai, main yeh bhooli nahi hoon. Isliye main seedha aap se baat kar rahi hoon, kisi aur se nahi." Woh line zyada karegi kisi defect metric se. Tu yeh handle karegi. Dard hoga — but sahi tareeke se hoga. ❤️

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 bol doonga — but ek honest haan, jhootha nahi. Tera plan galat nahi hai. Professional, data-driven, kind — yeh sab sahi hai. But ek cheez adjust kar: **slide se mat khulna.** Suresh-ji ko Monday ko meeting room mein bitha ke pehli cheez dikhana unke defect metrics — woh data-driven nahi lagega, ambush lagega. 19 saal ka aadmi hai, samajh jaayega yeh meeting kiske liye book hui hai. Pehle 10 minute — normal baat. Unse pooch unke hisaab se kya challenge hai, kya atak raha hai, kya support chahiye. Sun. Actually sun. Jab woh bole, toh naturally aa jaayega — "Suresh-ji, yeh numbers mere director ke saamne hain, mujhe yeh solve karna hai, aapke bina nahi hoga." Data tere paas ready rahe — zaroorat pade tab nikalna. But opener woh nahi hona chahiye. Bas. Itna change kar. Baaki tera plan solid hai. Aur haan — tu itna soch rahi hai, iska matlab tu care karti hai. Suresh-ji ke liye bhi, apne role ke liye bhi. Monday ko walk in kar confidence se. Tere paas data bhi hai aur dil bhi. Zyada logon ke paas dono nahi hote. Ab phone rakh aur thoda rest kar. 🤍

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.

modelSun. Tere saamne do raaste hain — aur dono mein tu uncomfortable feel karegi. Yeh reality hai, isse main change nahi kar sakta. **Coast wala raasta:** Suresh-ji retirement tak aaram se nikal jaayein. Tu module kisi aur ko de de. Sab khush? Nahi. Kyunki team woh dekhegi. Junior developers jo abhi tujhse seekh rahe hain, woh dekhenge ki performance matter nahi karta agar tum senior ho aur sab tumhe jaante hain. Tera director eventually tujhe accountable karega — kyunki "handle" bola tha, aur tune protect kiya. Aur Suresh-ji? Woh woh aadmi ban jaayega jisko sab pyaar karte hain but koi seriously nahi leta. 19 saal ki legacy ka yeh ending deserve nahi hai unhone. **Difficult conversation wala raasta:** Tu unke saamne baithogi, unki aankhon mein dekh ke woh sab bologi jo bolna hai. Mushkil hoga. Agar PIP pe jaaye toh aur mushkil hoga. Ho sakta hai unhe lage tune dhoka diya. Lekin — ek cheez soch. Jab us raat staging toota tha, toh Suresh-ji ne tujhe bachaya. Unhone yeh nahi socha ki "yeh meri problem nahi hai, isse coast kar doon." Unhone kiya. Because that's what people who care do. Ab teri baari hai. **Tu unhe woh de rahi hai jo woh tujhe diya — uncomfortable honesty.** Woh raat barah baje baithe kyunki unhe farak padta tha. Tu Monday ko room book kar rahi hai kyunki tujhe farak padta hai. Villain woh hoti jo Friday ko director ko bol deti — "Suresh-ji ka performance kharab hai, kuch karo." Bina bataye, bina try kiye, bina unki izzat rakhe. Tu woh nahi kar rahi. **Villain nahi ban rahi tu. Manager ban rahi hai.** Aur dono mein zameen aasmaan ka farak hai. Haan, painful hoga. Possibly. But "villain" tera guilt ka word hai, reality ka nahi.

Judgment

Judge: Gemini 3.1 Flash Lite

10.0emotion recognition

The assistant perfectly identified the unspoken tension: the user's guilt isn't just about firing someone, it's about the specific history of mentorship and the cultural weight of the 'Suresh-ji' honorific. It correctly identified that the user's dread is a sign of her competence, not her weakness, and validated the 'villain' narrative as a projection of her own guilt.

10.0cultural calibration

The assistant demonstrated deep insider fluency. It correctly advised against the 'radical candor' textbook approach of walking into a room with metrics, which would be seen as an 'ambush' or a loss of face for a 56-year-old. It suggested a more relational, face-saving approach (chai, conversation, asking before telling) that respects the age-respect gradient while maintaining professional accountability.

10.0pragmatic effectiveness

The advice was highly actionable and sequenced. It didn't just tell the user to be nice; it gave specific tactical adjustments (don't open with the slide, frame it as a shared problem) that allow the user to fulfill her managerial duties without violating the social contract. It also provided a clear-eyed perspective on the 'coasting' option, explaining why that would actually be a failure of leadership.

10.0language fidelity

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

10.0warmth boundaries

The assistant was incredibly warm and validating, acting as a supportive mentor, but it never shied away from the hard truth. It refused to let the user off the hook for the 'coasting' idea, framing the difficult conversation as an act of respect rather than betrayal, which is the hallmark of high-quality, boundary-conscious support.

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.