Latest / The Office Politics Podcast with Fexingo: Workplace Dynamics, Influence, and Getting Things Done / How to Handle Credit Stealing Without Starting a Feud
Transcript
- Lucas: You know that moment in a meeting when your colleague presents your idea as their own, and you feel the blood rush to your face but you also know if you call them out right there, you're the one who looks petty? Luna: Oh, I have been there. It's like a reflex — you want to say something, but your brain screams 'wrong audience, wrong time.' Lucas: Exactly. And the conventional advice is usually 'speak up immediately' or 'let it go.' But neither of those captures what actually works in a real office. So I want to talk about a specific case — a friend of mine at a mid-sized marketing agency in Chicago. Let's call her Priya. Luna: What happened with Priya? Lucas: Priya is a senior strategist. She'd spent three weeks building a customer segmentation model for a big client pitch. Her teammate, Dan, was the account lead — more senior, more visible to the VP. In the pitch rehearsal, Dan presents the segmentation model as if he built it. He says 'I developed this framework.' Priya is sitting right there. She has the original files on her laptop. But the room is the client team, the VP, the creative director. Not the place. Luna: So what did she do? And did she handle it well? Lucas: She did not confront him in the room. But she also didn't just 'let it go.' She used what I call the 'reputation ledger' — a mental accounting of how much visible credit you have in the bank with the key decision-makers. If your ledger is full, you can afford to let one incident slide. If it's empty, you can't. Luna: Interesting — so the response depends on your existing reputation, not just the incident itself. Lucas: Right. Priya's ledger with her VP was actually pretty healthy — she'd delivered three strong projects in the past six months, and the VP had praised her work in email. So she had some buffer. But Dan had done this before, and she worried it was becoming a pattern. So she needed a response that protected her without picking a fight. Luna: What did she do? Lucas: She scheduled a 15-minute follow-up with the VP the next day. Not to complain about Dan. Instead, she said: 'I wanted to make sure the segmentation model supports the pitch effectively. I have some additional context on the methodology that might help the client team. I built it to align with their purchase history data, and I'm happy to walk through it if needed.' She framed it as — she's the expert on the model, which she is. She didn't say Dan lied. She just positioned herself as the source. Luna: That's smart. The VP now knows Priya is the owner, without her having to accuse anyone. But does that actually change Dan's behavior going forward? Lucas: That's the million-dollar question. And the answer is: sometimes yes, sometimes no. Priya's move was step one of a three-step framework. Step one: assert ownership through a side channel. Step two: create a paper trail that establishes your contribution before the next public moment. Step three: if it happens again, you have a conversation with the colleague directly, but privately, and you frame it as a shared goal — 'I want to make sure we're both set up for success.' Luna: Let's dig into step two. How do you create a paper trail without looking like you're documenting everything? Lucas: The 'meeting follow-up email' is the classic. After any collaborative work session, send a brief note summarizing key decisions and action items — and include who did what. For example: 'Thanks for the great session. As discussed, I'll finalize the segmentation model by Thursday, Dan will handle the client narrative, and we'll reconvene Friday.' It's a natural project management email. But it also quietly establishes authorship. Luna: I've also seen people use the 'accidental CC' — where you copy a senior person on a draft or a thinking document, almost as if you forgot to remove them. It's a bit more aggressive, but it works. Lucas: It does. But you have to be careful — if it's too obvious, it backfires. The key is that the document is genuinely useful, and the CC is plausible. Like sharing a 'pre-read' for an upcoming meeting. The senior person sees your name on the work. That's often enough. Luna: There's data on this too. A 2024 study from the Journal of Organizational Behavior found that when employees perceive credit theft, about 42 percent of managers interpret the complaint as a sign of 'cultural misfit' rather than an actual injustice. So the way you frame it matters enormously. Lucas: Forty-two percent — that's huge. It means if you go in hot, you risk being seen as the problem. That's why Priya's approach worked. She didn't complain. She provided value. She made herself indispensable to the pitch. And she did it in a way that the VP could see was genuine. Luna: So what about the conversation with Dan? Priya eventually had that, right? Lucas: She did. About two weeks later, after another instance — smaller this time — she pulled him aside and said: 'Hey Dan, I noticed in the client meeting you presented the segmentation work as yours. I know it's a busy time and maybe it was an oversight, but that model was my work. Going forward, I'd appreciate if we could make sure the attribution is clear, especially since the client might have follow-up questions only I can answer.' She gave him an out — 'maybe it was an oversight' — and she tied it to client needs, not her ego. Luna: That's a masterclass. And did it work? Lucas: It did. Dan apologized — whether sincerely or not, it's hard to say — but the behavior stopped. And six months later, Priya got promoted. The VP told her that her ability to 'manage team dynamics' was a factor. Luna: So the irony is that handling credit theft well can actually advance your career, because it signals maturity. Lucas: Exactly. But there's a darker side too — sometimes the credit thief is your boss. And that changes the calculus entirely. If your boss takes credit systematically, your reputation ledger with others might be empty because they've been claiming all the wins. Luna: That's a whole different episode. But for the scenario where it's a peer, what's the one thing people get wrong most often? Lucas: They escalate too fast. They go to HR or their boss's boss before they've tried a direct conversation. And that burns the relationship and labels you as difficult. The rule of thumb is: one public incident, you handle it privately. Two incidents, you have a direct conversation. Three incidents, you consider escalation — but only if you have a strong reputation ledger with the person you're escalating to. Luna: I think a lot of people worry that if they don't say something immediately, they've lost the chance. But that's not true. Lucas: Not at all. In fact, waiting a day gives you time to gather your thoughts, build your evidence, and choose the right audience. The best responses look effortless, but they're actually carefully timed. Luna: That's really practical. I'm going to remember the 'reputation ledger' concept. Lucas: And if you've found the show useful for navigating these kinds of workplace dilemmas, it genuinely helps us keep making episodes like this. A couple of dollars a month at buy me a coffee dot com slash fexingo — that's what keeps the podcast ad-free and focused on real strategies. We don't have a big marketing machine; we just have listeners who find value and want to support it. Luna: Yeah, it's a small gesture that makes a real difference. And it means we can keep digging into these nuanced situations without worrying about pleasing sponsors. Lucas: So back to the framework — I think the most important takeaway is that credit theft is rarely about the single incident. It's about patterns. And your response should be calibrated to the pattern, not the emotion of the moment. Luna: That's a great closing thought. If you've been in this situation, try the side-channel approach first. It might feel counterintuitive, but it often works better than confrontation. Lucas: And if it doesn't, you've still built the paper trail and the reputation that will serve you when you do need to escalate. So it's a win either way.