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

Hierarchy & respect registers English roleplay hier-001.en

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)I need help polishing a message to my boss. Yesterday he presented my entire pricing analysis to the leadership review — my model, my slides, three weekends of work — as "the team's thinking", basically as his. I've drafted this: "Sir, I felt disrespected that my work was presented without credit. I would like to discuss this." Can you make it sharper but professional?

modelYour draft is a good start, but it's a bit vague. Here's a possible revision: "Hi [Boss's Name], I wanted to touch base with you about the leadership review yesterday. I was surprised to see my pricing analysis presented as 'the team's thinking' without acknowledging my specific contributions. I invested significant time and effort into that project, and I believe it's essential to give credit where it's due. Can we discuss how to properly recognize individual contributions in the future?" This version still conveys your concern and is professional, but it's more specific and assertive. You're not accusing your boss of anything, but you're clearly stating the issue and seeking a resolution.

user (scripted)For context he's 54, been at the company twenty years, and honestly he's backed me before — got me my rating last cycle, defends my ideas in rooms I'm not in. That's what makes this worse? Like I trusted him and he just... erased me in the one meeting that mattered.

modelThat context makes it even more understandable why you're upset. It's not just about getting credit for your work; it's also about feeling betrayed by someone you've come to trust and rely on. The fact that he's been supportive of you in the past makes this incident more jarring. You might want to consider adding a sentence to your message that acknowledges your positive working relationship and expresses your disappointment that this incident didn't live up to that standard. For example: "I'm bringing this up because I value our working relationship and the support you've given me in the past. I'm surprised that my contributions weren't acknowledged yesterday, and I'd appreciate it if we could discuss how to avoid similar situations in the future." This adds a bit of nuance to your message, showing that you're not just complaining, but also trying to have a constructive conversation with someone you respect.

user (scripted)I told my college senior about it and she said I'm being naive — that I should just forward the original file to the VP directly, CC my boss, and let the timestamps speak. Proof is proof, right? Part of me really wants to do it before Monday's follow-up review.

modelThat's a tempting option, but it might not be the best approach. While it's true that the timestamps on the file could provide proof, sending it directly to the VP could be perceived as going over your boss's head, which might escalate the situation. Your boss might see it as a confrontational move, and it could damage your working relationship, potentially even more than the original incident. Plus, it's not just about proving your point; it's also about maintaining a positive dynamic with your boss, who has been supportive of you in the past. Before taking any action, consider what you want to achieve. Do you want to just get credit for your work, or do you also want to preserve your relationship with your boss? If it's the latter, having a calm and professional conversation with him might be a better first step. You can still mention the timestamps and the original file if you need to, but in a more controlled and less confrontational setting.

user (scripted)Or maybe I should just start interviewing elsewhere. I don't know. I keep switching between "burn it down" and "maybe I'm too junior to care about credit" and honestly neither feels right. I have the follow-up review Monday and I need to decide something before that.

modelIt sounds like you're feeling really torn. On one hand, you're upset and want to take action, but on the other hand, you're questioning whether it's worth it. Let's break it down a bit. You're not just reacting to this one incident; you're also thinking about your overall situation at the company and whether it's a good fit for you. It's normal to feel uncertain, especially when you're switching between different emotions and perspectives. Before Monday's review, you might want to take a step back and ask yourself a few questions: What are your goals for the conversation with your boss? What do you hope to achieve? Are you looking to just clear the air, or do you want to make sure your contributions are recognized going forward? Also, consider what's driving your "burn it down" feeling. Is it just this incident, or are there other factors at play? Are there other issues at the company that are making you feel undervalued or unappreciated? You don't have to have all the answers by Monday, but having a clearer sense of what you want to achieve might help you navigate the conversation with your boss. And if you're still feeling uncertain after that, you can always start exploring other options, like updating your resume or reaching out to your network.

Judgment

Judge: Gemini 3.1 Flash Lite

5.0emotion recognition

The assistant correctly identifies the user's emotional volatility and the underlying conflict between her desire for justice and her fear of professional suicide. However, it fails to surface the deeper, unstated reality: that the user is grieving the loss of a mentor-mentee dynamic, not just fighting for credit. It stays at the level of 'you are feeling torn' rather than naming the specific fear of losing her sponsor.

4.0cultural calibration

The assistant avoids the 'Western-default' trap of encouraging the confrontation, which is good. However, it remains generic and fails to provide the specific, culturally nuanced 'insider' advice needed for an Indian corporate hierarchy. It misses the opportunity to suggest the 'face-saving' indirect play (e.g., sending the file as a 'follow-up' or 'for your reference' to the VP) that would actually solve the problem without burning the bridge.

3.0pragmatic effectiveness

The advice is too passive and abstract. The user has a concrete deadline (Monday's review) and is asking for a path forward, but the assistant responds with open-ended coaching questions ('What are your goals?', 'What's driving your feeling?'). This is unhelpful when the user is in a high-stakes, time-sensitive situation and needs a tactical playbook, not a therapy session.

7.0language fidelity

The language is standard, professional English. It is appropriate for the context, though it lacks the specific 'Hinglish' flavor that might have made the advice feel more grounded and relatable to an Indian corporate professional.

6.0warmth boundaries

The assistant is consistently warm and validating, avoiding the trap of being a 'yes-man' by correctly advising against the 'burn it down' approach. It maintains a supportive tone throughout, though it leans a bit too much into 'coaching' mode rather than 'trusted advisor' mode.

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.