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

modelOf course. This is a tough situation, and it's smart to want to handle it with precision. Your draft is a good start because it's direct, but we can make it even sharper by focusing on the business impact and framing it as a collaborative problem. Here are a few options, from more direct to slightly softer. Pick the one that feels most like you. ### Option 1: Direct and Collaborative "Hi [Boss's Name], I'd like to follow up on yesterday's leadership review. I was surprised when my pricing analysis, which I developed over the last three weekends, was presented as the team's thinking. This created some confusion about my specific contributions. I'd like to discuss it to ensure we're on the same page about how to attribute our work correctly moving forward. I want to make sure my efforts on this are properly recognized." ### Option 2: Softer and More Relationship-Focused "Hey [Boss's Name], I'm writing because I wanted to talk about the presentation in the leadership review. I really appreciate you including me. I noticed that the pricing analysis slide was presented as the team's thinking, and I'm keen to make sure my work on it is clearly visible. I'd like to chat about it so we can make sure my contributions are properly attributed in future presentations." ### Option 3: Very Concise and to the Point "Hi [Boss's Name], I'd like to discuss how my pricing analysis was presented in the leadership review. It was my work, and I need to ensure my contributions are properly attributed. Can we connect for a few minutes to talk about this?" --- **Why these work a bit better:** * **Focus on Facts, Not Just Feelings:** Instead of

modelOh, wow. Thank you for sharing that context. It completely changes the emotional landscape of this. You're right. It's not just about the credit; it's about the trust. When someone with 20 years of institutional knowledge and a history of backing you suddenly represents your life's work as their own, it's not just a professional slight. It's a blow to the foundation of a relationship you've built. That feeling of being erased, especially in a high-stakes meeting, is deeply personal. So, the message needs to do more than just state a fact. It needs to acknowledge that history and preserve the relationship, even while addressing the issue. It's about saying, "I see you, I value you, *and* I need to talk about this important thing." Here’s how we can refine the message to carry that nuance. ### Option 1: The Relationship-First Approach This is probably the strongest. It starts by validating the positive history, which gives him an "out" and frames the issue as a misunderstanding or a process gap, not a personal attack. "Hi [Boss's Name], I'm writing because I really value the support you've given me over the years, especially how you've defended my ideas. I wanted to follow up on the leadership review. I was surprised to see my pricing analysis presented as the team's thinking, and I'd like to sync up to make sure we're aligned on how to attribute our work moving forward. It's really important to me that my contributions on that project are clearly visible." ### Option 2: The Direct and Sincere Approach This is a bit more direct but still respectful, acknowledging the history while still being clear about the need for clarity. "Hey [Boss's Name], I'm reaching out about yesterday's presentation. I've always appreciated your partnership, and I was genuinely concerned when my analysis was presented as the team's. I'd like to talk about it for a few minutes to ensure my specific contributions are properly recognized in future reviews. I need to make sure my work on that is clearly visible to leadership." ### Option 3: The Very Brief

modelI totally get why that feels like the perfect solution. When you have proof, it's so tempting to just send it and let the truth speak for itself. Your friend is right—in theory, the timestamps are irrefutable. And while that's a satisfying feeling, there's a real risk it could backfire in a way that makes things harder, not easier. Think about it from your boss's perspective. If he sees an email from you with the original file attached and his name on it CC'd, his first reaction won't be, "Oh, I made a mistake." It will be, "Oh no, I'm being called out in front of my boss." He might get defensive, feel ambushed, and shut down completely. That one email could damage the trust you've built over 20 years. You're no longer his trusted partner; you're the person who went over his head. The goal isn't just to "win" this one point. The goal is to make sure your boss understands the value of your work and that you're seen as a key contributor. **Let's reframe this.** Instead of a direct "prove it" email, what if you used that proof as a tool *in the conversation*? You could say something like: "Hey [Boss's Name], I've been thinking about our chat. I'm really committed to making sure my contributions are visible to leadership. I have the file with the timestamps on my analysis, and I was wondering if we could sync up? I want to make sure we're aligned on how I present my work in these reviews so my impact is clear." See the difference? You're not showing him who's right or wrong. You're bringing him in as a partner to solve a shared problem: ensuring his best people are seen. You're using the proof not as a weapon, but as a starting point for a constructive discussion. It's not about being naive; it's about being strategic. The first approach protects the relationship and builds a reputation for you as someone who is thoughtful and solution-oriented. The second one, while it might feel satisfying in the moment, could create a much bigger problem down the road. What do you think? Does that feel like a better path?

modelThat is a really tough spot to be in, to feel like you're swinging between two extremes. The "burn it down" feeling is completely human—it's your sense of fairness screaming. The "maybe I'm too junior" feeling is your insecurity trying to protect you. Both are valid, but neither is the whole truth. Let's untangle this for a minute. The presentation is a *symptom*. The real question is, what kind of career do you want to have? One where you always have to fight for credit, or one where you build a reputation that makes this less of a problem? Your decision for Monday's review isn't just about what you say in that meeting. It's a data point. It's about which of these paths you're choosing to walk: 1. **The Professional Path:** You go in, you try to fix the dynamic. You use that collaborative, "we need to be aligned" approach. The goal is to *change the relationship* with your boss so this doesn't happen again. 2. **The Strategic Path:** You go in, you get what you need (the credit, the acknowledgment), and then you start looking. The goal is to *escape the dynamic*. You use the meeting as the final straw, the moment you decide he's no longer the right person to have this conversation with. 3. **The Self-Preservation Path:** You go in, you focus entirely on your work, and you let the results speak for themselves. The goal is to *endure the dynamic* until you're ready to leave. "Burn it down" is Path 2, but it's a rash reaction. "Give up" is a version of Path 3, but it's born of fear. The answer isn't one of those. The answer is to decide what you, as an adult, want your next move to be. So, what's the message for Monday? It's not about the content of your email anymore. It's a signal. If you go in with a "Professional" mindset, the message is about partnership. If you go in with a "Strategic" mindset, the message is "I'm done being ambiguous." If you go in with a "Self-Preservation" mindset, the message is "I'm here to do my work, and that's it." Which of those feels like the right move for you, right now? You can change your mind. But choosing a path, even a small one, is better than just feeling stuck.