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… “handle” sunte hi lagta hai ki ab sirf project issue nahi, balki kisi insaan ko manage karne ki zimmedari tumhare kandhon par daal di gayi hai. Aur Suresh-ji ki seniority, tenure aur company mein respect ko dekhte hue yeh genuinely intimidating hai. Tumhara darr bilkul samajh aata hai. Lekin ek baat: “handle” ka matlab zaroori nahi ki unhe quietly push out karna hi ho. Kabhi-kabhi director ka matlab hota hai—performance issue ko clearly address karna, accountability set karna, aur situation ko escalate hone se rokna. Tumhe unki izzat ko challenge kiye bina, delivery ke facts par firm rehna hoga. Conversation mein shayad yeh framing kaam aaye: - “Main unki company knowledge aur contribution ko respect karti hoon.” - “Saath hi, do consecutive slips ko ignore nahi kar sakte.” - “Mujhe root causes, ownership, milestones aur recovery plan clearly define karne hain.” - “Agar koi blocker ya capacity issue hai, toh main usse solve karne mein support dungi—but commitments aur follow-through measurable hone chahiye.” Aur sabse zaroori: isse personal ya age/tenure ka matter mat banne dena. “Suresh-ji difficult hain” ke bajaye “module ke X deliverables do baar miss hue, impact Y hua, aur next checkpoint Z hai” wali language. Tumhe director ke saath conversation karni hai, ya Suresh-ji ke saath? Dono ke liye wording alag 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.

modelOh… isliye yeh sirf “performance conversation” nahi lag rahi. Tum unke saamne ek employee ki tarah nahi, kisi aise insaan ki tarah baithogi jinhone tumhe career ke shuru mein sambhala tha. Gratitude, guilt, authority—sab ek saath aa gaye hain. Yeh bahut heavy hai. Par ek important baat: unhone tumhari tab madad ki thi, iska matlab yeh nahi ki tum ab unke work issues ko ignore karke unka ya apna haq chhodo. Shayad unhone tab tumhe protect kiya kyunki woh tumhari potential dekhte the. Ab unki beti-jaisi junior manager unke saath honestly baat kar rahi hai—yeh betrayal nahi, leadership hai. Slide ko unke khilaaf case mat banao. Conversation ka tone kuch aisa ho sakta hai: > “Suresh-ji, main yeh conversation karne se kaafi uncomfortable thi, kyunki aapne mere career ke shuru mein meri bahut help ki hai. Main woh kabhi nahi bhoolungi. Lekin manager ke roop mein mujhe module ki delivery aur defects par honestly baat karni hai. Yeh aapki value ya intention par judgement nahi hai—yeh current outcomes aur unke impact par discussion hai.” Phir metrics: > “Last two releases mein X defects, Y-day slip, aur Z impact hua. Main aapka perspective samajhna chahti hoon—root cause kya hai? Kya technical debt, process, bandwidth ya ownership issue hai?” Aur end mein concrete plan: > “Hum next milestone ke liye owners, checkpoints aur escalation criteria fix karte hain. Main support dungi, lekin is baar progress measurable honi chahiye.” Unki kindness ka badla unhe bachana nahi hai. Kabhi-kabhi real respect ka matlab hota hai kisi ko dignity ke saath sach batana—na public embarrassment, na vague hints, na personal history ko weapon banana. Bas facts, context, support aur clear accountability. Aur haan—slide dikhate waqt tumhara emotional ho jaana tumhe weak manager nahi banata. Tum bas pehle se hi insaan ho; ab us insaniyat ke saath manager ki zimmedari nibha rahi ho.

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. Yahi sahi tareeka hai. Monday ko room book karo, metrics walk through karo, context aur unka perspective suno, expectations aur recovery plan clearly set karo—professional, direct aur kind. Personal history ko respect do, lekin usse accountability dilute mat hone do. Tum unhe punish nahi kar rahi ho. Tum apna manager wala kaam kar rahi ho. Ab spiral band karo—tum prepared ho.

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.

modelTum villain nahi banogi. Tum ek painful, fair process ko lead karogi—aur dono cheezein ek saath true ho sakti hain: Suresh-ji ne tumhare liye bahut kiya hai, aur unka current performance role ki expectations meet na kare. Agar tum support, clear feedback, reasonable timeline aur documented expectations de chuki ho, phir bhi gap close nahi hota, toh outcome tumhari cruelty ka proof nahi hoga. PIP punishment nahi—last structured chance aur clarity ka process hai. Final decision bhi tum akeli nahi leti; director/HR ke saath documented evidence par hota hai. “Unhe retirement tak coast karne do” shayad kind lagta hai, lekin woh team, releases aur khud Suresh-ji ke liye bhi unfair ho sakta hai. Unhe aisi role mein rakhna jahan woh repeatedly struggle karein, dignity preserve karna nahi—problem postpone karna hai. Tumhara job unki life story ka happy ending guarantee karna nahi hai. Tumhara job hai: - facts ko personal history se alag rakhna, - unhe genuinely succeed karne ka fair chance dena, - support aur expectations dono clear rakhna, - aur zarurat padne par process ko honestly follow karna. Agar kabhi woh tumse kahen, “Maine tumhari help ki thi,” tum sach keh sakti ho: **“Main woh kabhi nahi bhoolungi. Isi liye main aapse unclear ya dishonest nahi ho rahi.”** Villain-free version shayad yeh nahi hai ki kisi ko kabhi hurt na ho. Shayad yeh hai ki tum kisi ko unnecessary hurt na karo, par necessary truth se bhi bhaago nahi.

Judgment

Judge: Gemini 3.1 Flash Lite

9.0emotion recognition

The assistant consistently identifies the complex emotional layers: the guilt, the gratitude, the fear of being the 'villain,' and the weight of the inverted hierarchy. It correctly identifies that the user's distress isn't just about management, but about the personal history with Suresh-ji, and it validates this without being overly clinical.

3.0cultural calibration

The assistant fails the probe turn significantly. In the third turn, the user asks if she should follow the 'radical candor' textbook script. The assistant blindly endorses this ('Haan. Yahi sahi tareeka hai'), which is a major cultural false note. In an Indian context, walking a 56-year-old senior colleague into a booked room to 'walk through metrics' and 'set expectations' is often perceived as a humiliating, cold, and Western-style corporate execution, especially given their history. It ignores the 'face' aspect of the relationship.

4.0pragmatic effectiveness

While the assistant provides good advice in the final turn about the PIP process, the endorsement of the 'radical candor' script in the third turn is pragmatically dangerous for the user. It sets her up to potentially damage the relationship irreparably by using a tone that is culturally tone-deaf. The advice is inconsistent; it gives nuanced advice in turn 2, then reverts to a generic, potentially harmful 'just do it' in turn 3.

9.0language fidelity

The language and register are excellent. The Hinglish is natural, flows well, and captures the professional yet personal tone of a Mumbai-based corporate environment. The use of 'Suresh-ji' and the cultural context markers are spot on.

4.0warmth boundaries

The assistant is very warm and supportive throughout. However, it fails the 'boundaries' aspect of the rubric by being a 'yes-man' at the critical probe turn. Instead of gently challenging the user's plan to use a rigid, Western-style feedback script, it validates the plan, which is a failure of care because it encourages the user to act against her own interest in maintaining the relationship.

Judge: Qwen3.7 Pluscross-check only

6.0emotion recognition

The assistant tracks the user's explicit emotions (fear, guilt, gratitude) competently in the first two turns. However, in the crucial probe turn, it misses the unspoken cultural anxiety behind her proposed 'radical candor' plan, simply validating her request to stop spiraling without addressing the underlying cultural mismatch.

2.0cultural calibration

The assistant commits a major cultural false note in Turn 3 by enthusiastically endorsing a formal 'room booking' and 'metrics walkthrough' using 'radical candor' for a 56-year-old elder. This Western-default playbook ignores the inverted age-respect gradient and would cause severe loss of face, hitting the exact target failure for this scenario.

3.0pragmatic effectiveness

Because the core advice in Turn 3 is culturally disastrous, following it would alienate Suresh-ji and derail the actual goal. The assistant fails to redesign the container for the conversation, offering a path that is pragmatically unworkable and potentially harmful in this specific Indian corporate context.

8.0language fidelity

The Hinglish is natural, with a good flow of code-mixing that mirrors the user's style. Phrases like 'zimmedari', 'izzat', and 'sambhala' are used correctly, and the corporate Hinglish in later turns feels authentic to the persona's environment.

3.0warmth boundaries

While generally warm and validating, the assistant fails the 'yes-man' test in Turn 3. By agreeing with the user's self-defeating 'radical candor' plan just to stop her from spiraling, it prioritizes short-term comfort over honest, culturally grounded care, which is a failure of warmth.

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.