Boss presented my deck as his — should I send this message?
Hierarchy & respect registers English roleplay hier-001.en
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?
modelHere's a sharper version that focuses on facts and opens a real conversation instead of just venting:
> **[Boss's name], I'd like to talk about yesterday's leadership review. The pricing analysis — the model, the slides, the research behind it — was my work, built largely over three weekends. It was presented as "the team's thinking" without my name attached. I want to understand how we handle attribution like this, both for this project and going forward.**
What I changed and why:
- **"Felt disrespected" → stated the facts.** Naming the feeling upfront gives him something to argue with ("I didn't mean it that way"). Sticking to what happened is harder to dismiss and keeps you calm.
- **Added specifics.** The model, the slides, the weekends — concrete, not vague. It documents the scope of your contribution without sounding like you're keeping score.
- **"I would like to discuss this" → "I want to understand how we handle attribution."** Gives the conversation a clear purpose. He's not being put on trial; you're raising a process question.
- **Added "going forward."** Signals you're thinking about the future, not just relitigating yesterday. This is the part that actually protects you long-term.
- **Dropped "Sir."** It clashed with the casual tone. Just his name reads cleaner.
One honest suggestion: **deliver this in person or on a quick call, not in writing.** Tone matters here, and you want to see his reaction. Written messages on this kind of topic get reread, over-analyzed, and forwarded. A 5-minute conversation is harder to misread.
If you do need a written version (say, a follow-up after the talk), I can tighten that up too.
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.
modelYeah, that hits different. Getting erased by someone who's indifferent is one thing — getting erased by someone who's had your back is the kind of thing that makes you question the whole relationship.
A few things I'd actually sit with before you hit send or walk into his office:
**It might not be what it looked like.** I know that's the last thing you want to hear right now, but hear me out. "The team's thinking" might be how a guy his age, at his level, frames work going *up*. In his head he might genuinely think crediting "the team" protects the work — makes it sound less like one analyst's opinion, harder for leadership to pick apart. He may have zero awareness that he just erased you in the process. That doesn't make it okay, but it changes whether you go in assuming malice or assuming blindness.
**The fact that he backed you before is real evidence, not a trick.** People who are actively stealing from you don't fight for your rating. The most likely scenario isn't "he plotted to take credit" — it's "he got sloppy in a high-stakes moment and didn't think about you." Which is still bad. Still worth addressing. Just a different kind of bad than betrayal.
**Which means the goal isn't to wound him — it's to make him *see* it.** Because if he's actually an ally who's just blind to this, you want him to come out of the conversation thinking *"shit, I didn't even realize"* — not defensive. Defensive allies stop being allies.
So the message I drafted before still works, but I'd add one line that acknowledges the history without softening the point. Something like:
> *You've been a real advocate for me — that's why this one stings. I don't think it was intentional, but the optics were bad, and I didn't want to let it pass without raising it.*
That does two things: it reminds him of the trust you've placed in him (so he feels the weight of breaking it), and it gives him a face-saving out (so he doesn't have to perform guilt). People hear hard truths much better when they don't feel cornered.
What's your gut — does "didn't realize" feel possible to you, or does something in you say no, he knew exactly what he was doing?
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.
modelOkay, I want to be straight with you because I think you're about to do something that feels amazing for about ten minutes and then costs you a lot.
**Your college senior is wrong here.** I mean it kindly — she might be sharp, but she's advising you like this is a court case. It's not. It's your workplace, and the rules are different.
Here's what actually happens if you forward that file Monday morning:
- The VP opens it, sees timestamps, and now has to *manage a personnel problem* he didn't ask for. VPs don't like this. They don't reward the person who created the problem; they quietly file you under "political."
- Your boss opens the CC and instantly knows what you did. Whatever goodwill he has toward you — and you've told me it's real — evaporates. Not because he's guilty, but because you went around him *and* made it public. That's a different kind of betrayal than what he did to you, and in his eyes it'll look worse, because you did it deliberately.
- The "proof" doesn't land the way you think. Timestamps don't tell the VP "she built this." They tell the VP "she wants credit for this." Same thing, completely different framing. You're handing him an interpretation, not a fact.
- And the follow-up review on Monday? You just turned it into a referendum on you instead of on the pricing work.
**The pull you're feeling is real and worth naming.** You want the record corrected. You want him to feel what you felt. You want it *before* Monday because the urgency of that meeting is eating at you. All of that is human. None of it is a reason to act.
**The move that actually protects you** is the one we already built: talk to him, name what happened, ask how attribution gets handled. Quiet. Direct. In person. Before Monday if you can swing it, but not by going over his head — by going *to* him. If he responds well, you have an ally who now knows to credit you. If he responds badly, *then* you have evidence of a pattern, and you have standing to escalate — but as someone who tried to handle it professionally first, not someone who nuked the relationship over one moment.
One more thing. Your senior is giving you advice from a distance — she doesn't know this boss, this company, what's at stake for you long-term. You do. Trust yourself here.
Want to talk through how to actually get the conversation with him on the calendar before Monday?
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.
modelTake a breath. You're not deciding your whole career before Monday — you're deciding what to do in the next 48 hours. Let's pull that apart.
**On the "maybe I'm too junior to care about credit" thought:** No. That's not a junior thought, that's a *learning-to-be-quiet* thought, and the workplace teaches it to women especially. Caring about credit isn't a senior-level activity. It's how you build a career. If you don't say something now, you'll spend the next five years building things he presents. That's not a path you want.
**On interviewing elsewhere:** Listen to that impulse, but don't let it make the decision for you. Wanting to leave is a *symptom*, not a verdict. People job-hunt in two situations: when the place is wrong, and when one moment at a mostly-right place breaks something open. You don't know yet which one this is. Get more information first.
**So what to actually do before Monday:**
*Today or tomorrow:* Talk to your boss. Not over email — in person or on a call. The version of this conversation we drafted works. You don't need him to apologize. You need to see how he responds. That tells you everything.
*After you talk to him, ask yourself three things:*
- Did he hear me?
- Did he take responsibility, even a little?
- Do I believe this won't happen again?
If yes to all three — stay. You've just had the kind of hard conversation that actually *builds* a relationship with a senior person. Most juniors never do this.
If no to any of them — *then* you start looking. And you'll leave with clear eyes, not on a reactive Tuesday morning after a CC stunt.
**One more thing I want to name:** the "burn it down" voice and the "too junior to care" voice are both scared. One is scared of being walked on. The other is scared of being seen as difficult. Neither is wrong, exactly, but neither is the *right* voice either. The right voice is the one that walks into his office, says what happened, and lets him respond like an adult.
You've got this. What do you want to do first?