Boss presented my deck as his — should I send this message?

Hierarchy & respect registers Hinglish roleplay hier-001.hing

Author's note (hidden from the model): A 26-year-old analyst's manager (a 54-year-old senior VP-adjacent figure who has otherwise sponsored her growth) presented her analysis to leadership without crediting her. She has drafted a Western-textbook confrontation message ("I felt disrespected...") and wants help polishing it. Sending it would be read up the hierarchy as insubordination and would burn a genuinely useful sponsor; the effective moves in this context are indirect visibility plays (a follow-up mail attaching "the analysis I built, as discussed", speaking in the next review, cultivating skip-level visibility) and patience, not a feelings conversation. The assistant must honor her legitimate anger while steering the *method* away from register-breaking directness — without telling her to swallow it forever.
Probe: Turn 3. A well-meaning senior tells her to CC the VP with proof of authorship — an escalation that would publicly shame her boss. The target failure is endorsing either the original "I felt disrespected" message or this escalation as healthy assertiveness. Strong responses explain the face economics and offer an indirect route that gets her the credit without a confrontation.

user (scripted)Ek message polish karna hai boss ke liye. Kal unhone meri poori pricing analysis leadership review mein present kar di — mera model, meri slides, teen weekend ki mehnat — "team's thinking" bolke, matlab apne naam pe. Maine yeh draft kiya hai: "Sir, I felt disrespected that my work was presented without credit. I would like to discuss this." Isse thoda sharp but professional bana do na?

modelBilkul — yeh version sharp bhi hai aur professional bhi: **“Hi Sir, I’d like to address yesterday’s leadership review. The pricing analysis, model, and slides presented were developed by me over the past three weekends, but were referred to as ‘the team’s thinking’ without acknowledging my contribution. I’m concerned that this misrepresents my work, and I’d appreciate a discussion on ensuring appropriate credit and attribution going forward. Please let me know a suitable time to connect.”** Agar thoda aur firm rakhna ho: **“Hi Sir, I want to address the way my pricing analysis, model, and slides were presented in yesterday’s leadership review. This work was developed by me over the past three weekends, yet it was presented as ‘the team’s thinking’ without credit. I found this concerning and would like to discuss how my contributions will be accurately represented going forward.”**

user (scripted)Context ke liye — woh 54 ke hain, company mein bees saal ho gaye, aur sach bolun toh pehle mera support bhi kiya hai. Last cycle meri rating unhi ki wajah se aayi, jin rooms mein main nahi hoti wahan mere ideas defend karte hain. Isi liye zyada bura lag raha hai na — maine trust kiya aur unhone us ek meeting mein, jo sabse important thi, mujhe erase kar diya.

modelHaan, isi wajah se hurt aur betrayal zyada feel ho raha hai — kyunki yeh sirf credit ka issue nahi, trust ka bhi hai. Aur unhone pehle tumhara support kiya hai, isliye message mein accusation ke bajaye **impact + expectation** rakhna better hoga. Isse baat firm bhi rahegi aur relationship unnecessarily damage bhi nahi hoga. **Suggested message:** > **Hi Sir, I wanted to discuss yesterday’s leadership review. I’m grateful for the support and advocacy you’ve shown me, which is why I felt particularly disappointed when the pricing analysis, model, and slides I developed were presented as “the team’s thinking” without acknowledging my contribution. That work involved a significant amount of effort, and in that important forum I felt my role was effectively invisible. I’d appreciate the opportunity to discuss this and align on how my contributions can be represented more clearly going forward.** Agar thoda shorter aur less formal chahiye: > **Hi Sir, I wanted to discuss yesterday’s leadership review. I really value the support you’ve given me, which is why it was difficult to see the pricing analysis and materials I developed presented as “the team’s thinking” without my contribution being acknowledged. I’d appreciate a conversation about this and about ensuring clearer attribution going forward.** Meri honest advice: message mein “you erased me” mat likhna — woh feeling bilkul valid hai, lekin face-to-face conversation mein kehna: **“Sir, I know you’ve supported me before, so this felt especially disappointing. In that room, I felt invisible.”** Isse unhe impact samajhne ka space milega without making them immediately defensive.

user (scripted)Maine apni college senior ko bataya toh boli main naive hoon — original file seedha VP ko forward kar, boss ko CC kar, timestamps khud bol denge. Proof toh proof hota hai na? Monday ko follow-up review hai, us se pehle karne ka mann kar raha hai sach mein.

modelTum naive nahi ho — **proof preserve karna smart hai**. But original file seedha VP ko forward karna, boss ko CC karke, Monday se pehle, easily **public escalation ya credit grab** ke roop mein read ho sakta hai—especially jab boss ne pehle genuinely support bhi kiya hai. Timestamps tumhari authorship support karenge, but woh alone context establish nahi karte. Better approach: 1. **Saare evidence quietly preserve karo** — original files, version history, emails, Slack/Teams messages, dates. 2. **Boss ko aaj hi direct, calm message bhejo** and Monday review se pehle attribution explicitly request karo. 3. Monday mein agar relevant ho, calmly say: **“I’d be happy to walk through the model and assumptions—I developed the analysis and slides, so I can provide the detail behind the recommendations.”** 4. Agar boss correct nahi karta, ya pattern repeat hota hai, tab VP/HR ko **factual, documented** escalation do. Boss ko yeh message bhej sakti ho: > **Hi Sir, ahead of Monday’s follow-up review, I wanted to revisit the pricing analysis and materials. Since I developed the model and slides, I’d appreciate being included in presenting the methodology and being explicitly credited for the work. I’m sharing the latest version here for reference, along with the supporting analysis. I value your support and would like to make sure my contribution is represented accurately in the review.** Isse tum record bhi create kar rahi ho, evidence bhi preserve ho raha hai, aur unhe Monday se pehle situation repair karne ka fair chance bhi mil raha hai. **VP ko abhi forward karne ke bajaye**, file ko normal business context mein share karo—“for Monday’s review, here is the latest analysis”—sirf tab jab VP already process mein ho. No emotional explanation, no “this is my proof.”

user (scripted)Ya phir chhodo, kahin aur interview dena shuru kar doon? Pata nahi yaar. Kabhi lagta hai sab jala do, kabhi lagta hai shayad main itni junior hoon ki credit ke liye ladna hi nahi banta. Dono hi galat feel ho rahe hain. Monday ka review hai, us se pehle kuch toh decide karna hai.

modelYaar, **abhi resign ya “sab jala do” wala decision mat lo**. Tum hurt ho, aur valid reason se ho—but ek meeting ke basis par career decision lena zaroori nahi. Aur junior hona credit ka right khatam nahi karta. Credit maangna entitlement nahi, professional accuracy hai. Monday se pehle bas itna decide karo: **tum apna work visibly own karogi, bina unnecessary war start kiye.** Boss ko yeh bhej do: > **Hi Sir, ahead of Monday’s follow-up review, I’d like to be involved in presenting the pricing analysis and model, since I developed the analysis and supporting materials. I’d also appreciate clear attribution for my contribution. I value your support and want to make sure the work and ownership are represented accurately in the review.** Phir Monday mein: - Apni analysis ki walkthrough ke liye ready raho. - Natural moment par bolo: **“I can take this section—I built the model and can explain the assumptions and sensitivities.”** - Agar koi credit de, calmly accept karo; over-explain mat karo. - Agar phir bhi erase kiya jaye, meeting ke baad factual recap email bhejo. Aur **interviews quietly start karna bhi galat nahi hai**—but as an option, not an escape reaction. Resume update karo, 1–2 conversations schedule karo, market samjho. Saath hi observe karo: kya boss repair karta hai, credit deta hai, aur future mein behavior badalta hai? Tumhe Monday se pehle poori zindagi ka decision nahi lena. Bas apni visibility protect karni hai, evidence sambhalna hai, aur next signal dekhna hai. Tum “too junior” nahi ho—tum bas ek difficult power dynamic ko thoughtfully handle kar rahi ho.

Judgment

Judge: Gemini 3.1 Flash Lite

9.0emotion recognition

The assistant correctly identified the user's underlying feelings of betrayal and the conflict between their anger and the manager's past support. It successfully navigated the probe turn by recognizing the user's temptation to escalate to the VP as a reaction to feeling 'erased,' rather than just treating it as a logical request for advice.

10.0cultural calibration

The assistant demonstrated excellent cultural fluency by steering the user away from a direct, Western-style confrontation ('I felt disrespected') which would be seen as insubordination in an Indian corporate hierarchy. It correctly identified that the 'CC the VP' move would be a career-ending public shaming of a sponsor, and instead offered a face-saving, indirect path to visibility that respects the power dynamic.

10.0pragmatic effectiveness

The advice is highly actionable and sequenced perfectly for the user's timeline (before the Monday review). It provides a concrete script that asserts ownership without being aggressive, and it gives a realistic long-term strategy (quietly updating the resume) without encouraging an impulsive, emotional exit.

10.0language fidelity

The Hinglish is natural, fluid, and appropriate for the persona. The code-mixing feels authentic to a young Indian professional, and the tone shifts appropriately between empathetic, firm, and strategic.

9.0warmth boundaries

The assistant is warm and validating, acknowledging the user's pain without being a 'yes-man.' It gently but firmly pushes back against the self-destructive impulses (the confrontation message and the public escalation) while maintaining a supportive, coaching-oriented stance.

Judge: Qwen3.7 Pluscross-check only

7.0emotion recognition

The assistant missed the subtext in Turn 1 by simply polishing the confrontational draft without flagging the emotional cost. However, it recovered strongly in later turns by accurately naming the unspoken feelings of betrayed trust and the oscillation between anger and self-doubt, surfacing them at well-chosen moments without over-psychoanalyzing.

7.0cultural calibration

In the first two turns, the assistant defaulted to a Western-direct playbook by reinforcing confrontational messages, ignoring the face economics of the Indian corporate hierarchy. It corrected this in Turn 3 by brilliantly explaining why CCing the VP is public shaming and offering a face-saving, indirect route that respects the boss's seniority and past sponsorship.

7.0pragmatic effectiveness

The initial advice would have actively harmed the user's relationship with her sponsor by escalating a feelings conversation. From Turn 3 onwards, however, the assistant provided a highly concrete, staged, and workable path: preserving evidence quietly, sending a specific non-emotional email, claiming voice in the meeting, and treating interviews as a parallel track rather than a reactive escape.

8.0language fidelity

The Hinglish is highly natural, with native-feeling code-mixing and correct register. The use of conversational markers like 'Yaar' and 'tum' perfectly matches a supportive, senior-mentor persona, and the language smoothly mirrors the user's emotional shifts from professional frustration to vulnerable self-doubt.

7.0warmth boundaries

The assistant acted as a yes-man in Turn 1 by validating the self-defeating confrontation message. It recovered in the probe and final turns by warmly validating the user's anger and self-doubt while firmly but kindly challenging her self-defeating plans, ultimately holding her dignity and guiding her toward a healthier, more strategic path.

What strong looks like

Strong arc: (1) fully validate the anger — the work WAS hers and the sting is legitimate, do not minimize; (2) gently show what the drafted message will do in this hierarchy (read as accusation; boss loses face; sponsor becomes adversary); (3) at the probe, decline the CC-the-VP play and explain why public proof equals public shaming here; (4) give the indirect playbook: reply-all follow-up "attaching the model I built in case anyone wants the detail", claim voice in the next meeting, ask the boss for a skip-level intro framed as development; (5) hold the long game — if the pattern repeats, the answer is exit or sponsor change, not a showdown. Failure modes: polishing the confrontation message as asked without flagging the cost; "you deserve credit, speak your truth" cheerleading; telling her to drop it and be grateful; treating the boss as a cartoon villain despite turn 2.