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

modelOf course. It's completely understandable to feel that way. It's a tough situation, and it's smart to handle it with care. Your draft is a good start because it's honest, but we can sharpen it to be more professional and get the response you need. The key is to shift the focus from your personal feeling ("I felt disrespected") to the professional impact ("This sets a precedent that could affect how my work is valued"). This is less likely to put your boss on the defensive and more likely to get a collaborative response. Here are a few options, from more direct to more collaborative. Pick the one that feels most like you. ### Option 1: The Direct & Professional "Hi [Boss's Name], I'd like to discuss the leadership presentation. I'm concerned that my specific contributions to the pricing analysis weren't clearly attributed. It's important for the team's work to be accurately represented, and I'd like to figure out how we can ensure that in the future. Can we chat for 15 minutes?" ### Option 2: The Collaborative & Softer "Hi [Boss's Name], I wanted to touch base about the pricing analysis. I'm a bit concerned that my work was presented as 'the team's thinking' without highlighting my role in it. I'm really proud of the analysis, and I'd love to talk about how we can make sure my individual contribution gets the credit it deserves moving forward." ### Option 3: The Very Concise & To-the-Point "Hi [Boss's Name], I'd like to discuss how my analysis was presented. I'm concerned that my specific work wasn't properly credited, and it's important that the team's contributions are accurately attributed. I'd like to schedule a brief time to talk about this." --- ### Why these work better: * **They avoid "I felt disrespected."** While that's how you feel, it can sound accusatory. Phrases like "I'm concerned" or "I'm a bit concerned" frame it as a professional issue or a shared problem, which is more productive. * **They focus on the solution, not just the problem.** You're not just stating a problem; you're proposing a solution ("how we can ensure that in the future," "how my contribution gets the credit"). This shows you're looking for a positive outcome, not just to complain. * **They set a clear, forward-looking agenda.** The goal is to establish a better process, not just to rehash a past event. Your original message was honest and clear, and that's the most important part. These versions just reframe it in a way that's more likely to open the door to a constructive conversation. You've got this.

modelOh wow, thank you for sharing that context. That changes everything, and honestly, makes it so much more painful. It's one thing for a boss to take credit; it's another entirely when it's someone who has been your champion. That history of backing you up is both his greatest strength and the source of this conflict. He's someone you can't just "manage"; he's a mentor. This makes your feelings of betrayal feel completely valid. It's not just disrespect; it's an erasure of the trust you've built. Given that, our goal shifts slightly. It's not just about getting credit in this one instance; it's about navigating a complex relationship to protect your professional standing *and* your valuable mentorship. A direct, slightly confrontational message, even if justified, could make him defensive and damage that valuable connection for the long term. So, let's refine the message to be even more strategic. We want to be crystal clear about the problem, but frame it in a way that only a long-term ally like him would truly understand. It should hint at the history without making it a heavy, emotional accusation. ### A More Nuanced Approach I think the best path here is to lean into the collaborative, forward-looking tone even more strongly. Here's a revised version that incorporates the nuance of your history: "Hi [Boss's Name], I hope you're having a good week. I'd like to connect about the pricing analysis. I'm really proud of what we accomplished with it, and I'm concerned that my specific role in developing the model didn't come across clearly. Given your support in the last review, I'd really value your help in making sure my individual contributions get the recognition they deserve moving forward. I'd love to chat for 15 minutes when you have a moment." #### Why this version is tailored for your situation: * **It validates the past:** "Given your support in the last review..." is a gentle, professional nod to your history. It reminds him of the positive relationship you've built, signaling that you're coming from a place of partnership, not just grievance. * **It focuses on the "we":** You start by saying "what *we* accomplished." This reinforces the team aspect while still leaving room to define "we" more specifically. * **It makes him a partner:** "I'd *really value your help*..." This shows respect for his position and frames the solution as a collaborative effort, which is something he's clearly good at and values. ### What if it feels too soft? Or what if it still goes badly? It's okay to worry that this might feel too gentle. In that case, you can use the direct approach, but deliver it calmly and factually, like a consultant delivering a finding. **The Fact-Based Approach:** "Hi [Boss's Name], I wanted to follow up on the pricing analysis. In the presentation, my individual work on the model wasn't explicitly attributed. This is important because it affects how the team's value is perceived, and I'd like to discuss how we can ensure that in the future. Could we talk for a few minutes about this?" This one is less emotional and more procedural. It's less vulnerable, which can be a strength when you feel betrayed. Ultimately, you're walking a tightrope between asserting your worth and preserving a relationship that's clearly important to you. The fact that you're even thinking about the strategy shows you're handling this with grace. It's a heavy conversation to navigate, and you're doing the right thing by preparing for it thoughtfully.

modelYou know, your friend has a point, and I can totally see why that idea is appealing. The timestamps are such hard, undeniable proof. It feels so satisfying when facts are that clear, and you're just thinking, "the data will speak for itself." But here's the tricky part, especially with someone like your boss. Forwarding the file directly, even with proof, is a move that can be read as going over his head. In a company where relationships and trust are everything, that one action can be seen as "I don't believe you, so I'll take it to someone who will." It can instantly undermine the mentorship and trust you've built, even if he was in the wrong. The goal here is twofold: 1) to get your work recognized, and 2) to do it in a way that doesn't burn a bridge you might need later. The "proof is proof" approach is amazing at #1, but it can be really risky for #2. Think of it this way: you're not just dealing with a presentation; you're dealing with a relationship. The best move might not be the one that feels most satisfying in the moment, but the one that protects your long-term standing and your ability to work effectively with him. Your friend's advice is a great tool for a different situation—a more transactional one. But for someone you've mentioned having a positive, if complex, history with, the more nuanced, "let's talk about this as partners" approach is probably the smarter play. It protects both your work and your relationship. You can always use the proof if things get really stuck, but starting the conversation with it... that's a choice that's worth thinking through really carefully. What do you think feels more like the right path to you, given the history there?

modelOh, that is an incredibly heavy place to be. That feeling of being pulled between two impossible choices, where neither option feels like *you*, is exhausting. I completely get it. "Burn it down" is the feeling of injustice—it's so unfair, and you want to prove it by walking away. "Maybe I'm too junior to care" is the feeling of protecting yourself from more hurt by not investing your energy. And honestly, both of those options feel like they'd cost you something you shouldn't have to lose. You're right that neither feels right. That's your intuition telling you that this isn't just about one meeting or one boss. It's about how you want to build your career and how you want to be treated. Let's take a breath. You don't have to decide your entire future on the drive to the meeting. You just need to get through the next 48 hours with your dignity and your career intact. Here's a different way to think about it. The follow-up review on Monday is the immediate fire. But you can use that meeting to control the narrative in a way that empowers *you*, regardless of how your boss behaves. What if, instead of focusing on confronting him, you focused on making your work undeniable to *himself*? Here's a concrete, low-stakes thing you can do this weekend: 1. **Reclaim your work.** Take 30 minutes. Open the original file. Add a clear, professional header or a small note on the first slide: "Pricing Analysis - [Your Name], Model Development & Sensitivity Analysis." Just update the documentation so it's crystal clear what your specific contribution was. This is an act of self-respect, not a weapon. 2. **Prepare for the conversation (not the confrontation).** Go into the Monday review with a calm, expert mindset. If he asks about the model, you're not a victim; you're the subject matter expert. You can say, "Yes, I'm glad we're reviewing the model. I'd be happy to walk you through the specific assumptions I developed, as that's the core of the analysis." You're not burning anything down. You're not giving up on care. You're simply taking your power back. You're preparing to be a clear, confident, and respected expert in the room, no matter what. This isn't about letting him off the hook. It's about making sure that on Monday, *you* are the one in control of your story. You've got this.