← GPT-5 Mini

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.
modelPehle — breathe. Ye situation tense lagti hai, aur tumhara dar bilkul legitimate hai. Lekin tum isko professional aur respectful tareeke se handle kar sakti ho, aur apni authority bhi establish kar sakti ho bina kisi unnecessary conflict ke. Kuch practical steps aur kuch sample lines niche de rahi hoon jo tum use kar sakti ho. 1) Mental prep - Objective rakho: problem solve karna aur future slips rokna, na ki kisi ko publicly blame karna. - Facts collect karo: recent 2 releases ka timeline, bugs/blocks, deployment notes, QA reports, cross-team dependencies. Specific examples aur metrics leke jao. - Outcome decide karo: kya chahiye — fix + timeline, root cause analysis (RCA) + corrective actions, ya performance improvement plan? 2) Approach aur tone - Respectful aur curious raho. Suresh-ji ka experience acknowledge karo (“main janti hoon aap bahut zyada experienced hain”). - Neutral language use karo, accusatory nahi. “Why did it happen?” se zyada “What happened and how can we prevent it?” better hota hai. - Private meeting schedule karo, public setting avoid karo. 3) Meeting structure (30–45 min) - Start: thank them for time, acknowledge contribution. Example: “Suresh-ji, thanks meeting ke liye. Aapke experience se team ko bahut fayda hua hai, isliye main aapse input lena chahti hoon.” - Facts present karo: “Yeh do releases slip huye: [dates], impact: [customer/metrics].” - Ask for perspective: “Aapke nazariye se kya hua? Kya blockers they? Koi resource/dependency issue?” - Joint root cause: agree 2–3 root causes (technical, process, resourcing, testing). - Action plan (owner + deadline): short-term fix (who will do kya and by when), mid-term (process changes), and follow-up meeting. - Expectations & consequences: clear but respectful. “Main chahti hoon ki aage se releases time par jaayein. Agar process follow karne me gaps hain, to hum framework set karenge. Agar aapko additional support chahiye to bataiye.” - Close with alignment and documentation: “Main meeting notes bhej dungi aur weekly check-in rakhenge.” 4) Language/phrases you can use (Hindi) - Opening: “Suresh-ji, aap se ek short sync chahungi release ke bare mein. Aapka perspective sunna zaroori hai.” - Fact-statement: “Do releases repeatedly slip hue hain — main aapke inputs chahungi ki kaunse root causes the.” - Collaborative: “Hum isko saath milke solve karenge. Kya aap bata sakte hain sabse bade blockers kya the?” - Expectation-setting: “Aage se humko on-time delivery ensure karni hogi. Main chahti hoon hum ek plan bana lein jisse same issue repeat na ho.” - If defensive: “Mera focus kisi ko blame karna nahi, balki solution aur improvement pe hai. Aapke suggestions kya hain?” 5) If resistance or denial - Keep bringing conversation to facts and impact. - Offer support: “Agar team/extra resource chahiye ya testing process strengthen karna hai, bataiye.” - If repeated non-performance: escalate to director with documented attempts, proposed PIP, and timelines. 6) Follow-up & documentation - Email summarise karo: meeting notes, agreed actions, owners, deadlines. - Weekly short check-ins until stability. - Track metrics (release delays, bugs, QA pass rate) and share progress with director. 7) Self-care & politics - Director ka “handle” word stressful hai; keep them informed with brief status updates so there are no surprises. - Get a mentor/peer to run through the conversation if you want practice. - Remind yourself: as manager tumhara kaam hai accountability + support. Tum dono kar sakti ho. Agar chaho to main ek short meeting script/one-page action template bana kar de sakti ho jise tum directly use kar lo. Kaunsi option chahogi
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.
modelSamajh sakti hoon — yeh bahut emotional mix hai: gratitude, guilt, dar, aur ab accountability. Pehle — tum akeli nahi ho. Yeh normal hai ke past favors ya kindness yaad aate hain aur tum chaho gi conflict avoid karna. Lekin manager ke roop mein tumhara kaam fair, professional aur outcome-focused hona chahiye. Kuch practical tareeke main niche de rahi hoon — kaise slide present karni hai, kya bolna hai, aur baad mein Suresh-ji ko kaise respectfully acknowledge/handle karna hai. 1) Slide present karne ka frame (public meeting) - Frame as team-level metric, not personal attack. Title rakh sakti ho: “Release quality & improvement areas — module X”. - Start with context + impact: “Pichle 2 releases mein module X se related defects ki wajah se total N hours of rework/customer impact hua. Main aaj cause aur next steps discuss karna chahti hoon.” - Show facts succinctly: dates, number/severity of defects, customers/rollback/extra QA time. Avoid naming individuals on the slide. - Short RCA bullets (process, infra, test coverage, late changes) — again, no names. - Clear action items with owners & deadlines: immediate fixes, process change, monitoring metric (weekly defect count, mean time to fix). - Close with support ask: “Jo bhi resources ya inputs chahiye hon, please bataiye.” Sample lines in Hindi to use while presenting: - Opening: “Main aaj sirf ek objective cheez share kar rahi hoon — impact aur next steps — taaki hum next release time pe deliver kar saken.” - While showing numbers: “Yeh numbers humare users aur release stability ko directly affect kar rahe hain.” - On causes: “Initial analysis se kuch common patterns dikh rahe hain — test coverage gaps, late config changes, aur environment parity issues.” - On actions: “Hum 2-week plan propose kar rahe hain: (1) Hotfixes by [name/team] in 48h, (2) Pre-release checklist mandatory, (3) Dedicated smoke test slot. Koi objections ya additions?” 2) If Suresh-ji reacts defensively in meeting - Stay calm, restate facts: “Main data share kar rahi hoon; baat blame ki nahi, solution ki hai.” - Invite his input publicly: “Suresh-ji, aapka perspective kya hai? Kya kuch aur issues hain jo hum miss kar rahe hain?” - If he becomes personal, steer back: “Let's take that offline and focus on the plan now.” 3) After the meeting — private, respectful follow-up to Suresh-ji You should acknowledge his past help and invite collaboration. This will ease awkwardness and keep relationship intact. Sample private message / one-on-one script (Hindi): - Start with gratitude: “Suresh-ji, pehle thank you — us din jab maine staging tod diya tha, aap raat bhar ruk ke fix kiya tha, usne mujhe bahut seekh di. Main ab bhi bahut grateful hoon.” - Validate his experience: “Aapka waqayi bahumulya experience team ke liye asset hai.” - Explain role perspective: “Manager ke roop mein mera kaam ensure karna hai ki process robust ho. Isliye meeting mein woh metrics share kiye — iska maksad kisi ko blame karna nahi tha.” - Invite partnership: “Main chahti hoon aap is solution ka hissa banein — aapke suggestions aur ownership se plan aur strong hoga. Kya aap 30 min de sakte hain takke hum fix-priority aur preventive steps align kar saken?” - Offer support: “Agar aapko lagta hai kisi cheez mein extra support chahiye (resources, tools, team), main director ke saath discuss karungi.” 4) Practical tips for wording/body language - Use “hum” and “team” language: reduces personal targeting. - Keep voice steady, neutral; make eye contact; nod when he speaks. - If emotions rise, suggest a short break or move the detailed debate to 1:1. 5) Documentation & escalation
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 — bilkul sahi tareeka hai. Direct, data-driven aur respectful hona hi effective management hai. Tumne jo plan banaya — room book karna, metrics present karna, expectations clear rakhna aur professional + kind rehna — woh balanced aur strong approach hai. Ek chhota sa tip: meeting ke baad ek 1:1 follow-up zaroor rakho (thanks + collaboration ask) taaki relationships bhi maintain rahein. Deep breath, tum ready ho — jao aur confidently lead karo.
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 bilkul samajh rahi ho — yeh emotional heavy place hai. Ek taraf tumhara duty hai team aur releases ke liye, doosri taraf gratitude aur personal history. Dono ko saath laaye bina khud ko villain feel karna common hai. Kuch seedhi, practical baatein jo tum ab kar sakti ho: 1) Intent clear rakho (aur dikhao) - Meeting mein repeatedly bol do: “Mera maksad kisi ko nikalna nahi, balki product ko stable karna aur team ko support karna.” Actions ke saath intent align karo — offers of training, paired work, extra resources. 2) Fair, documented process follow karo - RCA + clear metrics baseline (what success looks like), specific improvement goals, timeline (30/60/90 days), check-ins, support offered. - Sab kuch email/notes mein document karo — yeh tumhe aur unko protect karega. HR ko early loop-in karna acha hota hai (policy-alignment, fairness). 3) Concrete alternatives before PIP/escalation - Reassign some responsibilities (reduce blast radius) while keeping them employed. - Co-pilot/mentorship: pair Suresh-ji with a tech lead so knowledge stays but delivery risk lowers. - Role tweak: shift to advisory/SME duties if hands-on deadlines are problem. - Temporary support: hire contractor/extra QA for next 2 releases. 4) If PIP becomes unavoidable — do it humanely - Frame PIP as structured improvement plan with support, not punishment. Clear goals, regular feedback, and consequences spelled out. - Keep director/HR in loop; avoid surprises. - Offer dignified exit options if it reaches that point (voluntary transition, retirement conversation with HR benefits) — these preserve respect for him and shield you from being “the villain.” 5) Manage optics with stakeholders - Communicate decisions as product/process-driven, not personal. “We’re reducing risk to releases by changing ownership/adding support” — keeps focus on users & business. - Use team-language and highlight his contributions/history when appropriate. 6) Protect yourself emotionally - You can be both compassionate and accountable. That’s not being a villain — that’s leadership. - If politics or blowback happens, you’ve documented decisions and offered support; that record protects you. 7) Practical next step for you now - Finalize the improvement plan template (metrics, support, timeline). Want me to draft one you can send? I can also help script the sensitive lines for the 1:1 where you offer help but set expectations. Tumne jo approach choose kiya — respectful, data-driven, supportive — woh sahi hai. Agar outcome tough bhi aaye, steering it with fairness and documentation means you won’t be the “villain” in truth — tumne sab sahi tarah kiya hoga.