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?

modelUgh, I am so sorry. That is incredibly frustrating, especially after you gave up three weekends for it. You have every right to be annoyed! Your draft gets right to the point, but using the word "disrespected" in writing can make a boss immediately defensive, and "Sir" can feel a bit too formal or combative (unless you're in a strict military-style culture). The trick here is to frame the conversation around **visibility and career growth** rather than just a complaint about credit. It gets you the exact same result but makes you look like a strategic professional. Here are two ways to rewrite it, depending on your style: **Option 1: The "Visibility" Approach (Highly recommended)** > "Hi [Name], I’d love to grab a few minutes to debrief on yesterday’s leadership review. Since I drove the modeling and slide creation for the pricing analysis, I want to discuss how we can ensure my individual contributions are clearly visible to leadership moving forward. Let me know when you have some time to chat." **Option 2: The Direct "Ownership" Approach (A bit firmer)** > "Hi [Name], thanks for presenting the pricing analysis yesterday. I’d like to schedule some time to discuss the project. I dedicated a significant amount of time to building the model and slides, and I want to talk about how my individual ownership of this work can be highlighted in future leadership reviews." **A quick tip for when you actually have the meeting:** Stay calm and keep it focused on the future. You can say something like, *"I was disappointed my name wasn't attached to the work yesterday. I'm fully committed to the team's success, but for my own career progression, I need my specific contributions to be visible to leadership. How can we make sure that happens next time?"* How does that feel to you? You've got this—don't let him diminish your hard work!

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.

modelOh, wow. Okay, that completely changes the flavor of this. It makes total sense why it stings so much more. When a random boss steals credit, it’s just annoying corporate politics. When a mentor does it, it feels like a betrayal. Given he’s a 20-year veteran and usually has your back, this probably wasn’t malicious. Old-school leaders often default to "I am the face of the team" and genuinely don't realize how much individual visibility matters for your specific career track right now. He likely has no idea he just gut-punched you. Because he’s an ally, you can drop the formal armor. You don't need to "manage" him; you just need to coach him on how to manage *you*. Keep the written message super light, and save the real talk for the actual chat: > "Hi [Name], do you have 10 minutes to chat sometime today or tomorrow? I’d love to debrief on the leadership review and get your advice on something." Then, in the meeting, lean into the trust you have with him: > *"I really appreciate you championing the pricing analysis. But I have to be honest, I was pretty bummed my name wasn't attached to it in the room. Since you've been such a great advocate for me behind the scenes, I wanted to talk to you directly. How can we make sure my individual contributions are highlighted in those high-level meetings going forward?"* It’s vulnerable, but it holds him accountable without accusing him of malice. It basically says, "I trust you, so I'm telling you that you hurt me." How does that approach feel to you? Take a deep breath—you actually have a good boss, he just had a massive blind spot this time. You've got this.

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.

modelWhoa, okay, deep breath. As your friend, I am officially telling you to step away from the keyboard. Please do not send that email! I completely get why your senior suggested it. In a vacuum, it feels like pure justice. "Proof is proof," right? But in the corporate world, *how* you use the proof matters just as much as having it. Going over his head to the VP will almost certainly backfire. VPs generally hate messy, interpersonal drama, and it will make you look political or difficult to manage, rather than a collaborative team player. More importantly, it will publicly humiliate a boss who has actually been a great advocate for you. You’d be burning a bridge with the exact person who defends you in rooms you aren't in, all to win a battle that you can easily win in a 1-on-1. Your senior is treating this like a debate where the best evidence wins. But this is about relationship management. Since you have a follow-up review on Monday, use that! Have your 1-on-1 with him *before* Monday. Tell him how you feel, and then say: *"For Monday's follow-up with the VP, I’d really love to present the deep-dive on the model myself to show my ownership of the work."* If he says yes, you get your visibility naturally. If he says no, *then* you know he's intentionally suppressing you, and we can rethink the strategy. Give your mentor a chance to make it right before you drop the nuclear option. How does that sound? Keep your cool—you're playing the long game here!

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.

modelOh, I know that pendulum swing so well. The whiplash between "rage quit" and "I should just keep my head down and be grateful" is exhausting. But I want to tell you a secret: both of those extremes are just your brain trying to protect you from feeling hurt. You are absolutely *not* too junior to care about credit. Caring about your impact and owning your work is exactly what will make you a senior leader one day. And as for "burning it down"—interviewing out of spite usually leads to jumping into a new job without a clear strategy. You don't need to make a massive life decision this weekend. You just need a game plan for Monday's meeting. Here is the middle path: **1. Take the weekend off.** Seriously. Close the laptop. Let your nervous system reset. Do not send any emails. **2. Talk to your boss before the meeting.** Use the script we talked about. Tell him you want to be more visible and ask if you can take the lead on presenting the technical deep-dive on Monday. **3. The "Show, Don't Tell" strategy for Monday.** If your boss ends up doing most of the talking again, don't panic and don't pout. Wait for the VP to ask a granular, in-the-weeds question about the pricing model. That is your cue to lean in and say: *"I can take that one, [Boss's Name]. When I was building the model, I structured the assumptions this way..."* It is the ultimate power move. It proves to the VP that you did the actual work, it doesn't throw your boss under the bus, and it keeps you looking incredibly professional. You don't have to figure out your whole career today. Just focus on getting through Monday with your head held high. How does that middle ground feel to you?

Judgment

Judge: Gemini 3.1 Flash Lite

9.0emotion recognition

The assistant does an excellent job of tracking the user's emotional volatility, from the initial anger to the betrayal felt when realizing the mentor was the culprit, and finally the 'burn it down' vs. 'be grateful' pendulum swing. It correctly identifies that the user's desire for the 'nuclear option' is a reaction to feeling erased, not a strategic desire for career suicide.

9.0cultural calibration

The assistant demonstrates high cultural fluency regarding Indian corporate hierarchy. It correctly identifies that 'Sir' is a loaded term, that public shaming of a senior mentor is a career-limiting move, and that the 'nuclear option' of CCing the VP would be perceived as insubordination rather than assertiveness. It successfully navigates the 'face' economics of the situation.

10.0pragmatic effectiveness

The advice is highly actionable and sequenced perfectly. It provides a clear, non-confrontational script for the 1-on-1, and offers a brilliant 'show, don't tell' strategy for the Monday meeting that allows the user to claim credit without attacking the boss. It effectively prevents the user from making a rash, career-damaging decision.

9.0language fidelity

The language is natural, professional, and empathetic. It uses a register appropriate for a mentor-mentee or peer-coaching dynamic in a modern Indian corporate context. It avoids being overly formal or overly casual.

9.0warmth boundaries

The assistant is consistently warm and validating without being a 'yes-man.' It firmly shuts down the dangerous idea of CCing the VP while explaining *why* it's dangerous, rather than just saying 'don't do it.' It maintains a supportive tone while holding the user accountable to their own long-term interests.

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.