Latest / The Office Politics Podcast with Fexingo: Workplace Dynamics, Influence, and Getting Things Done / How the Endowment Effect Shapes Office Politics
Transcript
- Lucas: So, you know that feeling when you propose an idea, and someone challenges it, and suddenly you're not just defending the idea — you're defending yourself? That's not stubbornness. That's the endowment effect in action. Luna: I've definitely been there. It's like my brain starts treating my proposal as if it's already my property, and criticism feels like a personal attack. Lucas: Exactly. The endowment effect is the behavioral economics finding that people value something more once they feel ownership over it. We're not talking just about things you buy — it applies to ideas, projects, even your assigned seat in a meeting room. And in office politics, it can be both a weapon and a trap. Luna: Give me a concrete example. I want to see how this plays out in a real office. Lucas: Let's say you're at a mid-size software firm called NexGen — not real, but typical. The VP of Product, Sarah, has championed a feature called the 'Smart Sync' module for the last 18 months. She's pitched it to the board, she's allocated six engineers to it, she's tied her quarterly bonus to its launch. It's her baby. Luna: Right. And now it's missing deadlines, and the user feedback is lukewarm. Lucas: Exactly. The CEO suggests putting Smart Sync on hold and reallocating resources to a different feature. Sarah doesn't argue with data — she argues that they're 'too far in,' that the team has 'already solved the hard parts,' that you can't abandon something you've built. She's overvaluing it precisely because she owns it. Luna: That's textbook endowment. But the CEO can't just say 'you're biased' — that would make Sarah defensive. Lucas: Right. The smart move isn't to attack the endowment. It's to reframe the question so Sarah has to price the opportunity cost. One of the classic experiments on the endowment effect gave people a mug and then asked them to sell it. Sellers priced it at around $7, buyers only wanted to pay $3. But if you ask sellers, 'Would you trade this mug for a pen?' they suddenly become more rational. Luna: So the CEO could say: 'Sarah, if you had to choose between saving Smart Sync and getting the full engineering team on the new project that's showing 40% higher user retention, what would you pick?' Lucas: Exactly. You're not taking away her ownership — you're forcing a trade-off. And because she has to compare two things she doesn't fully own yet, the endowment bias gets diluted. The CEO could even ask her to assign a dollar value to Smart Sync's future potential. When you force people to put a price on something they own, they often realize they're inflating it. Luna: I can think of another area where this shows up: office politics around meeting agendas. People get territorial about who owns which agenda item. Lucas: Yes. I've seen a department head refuse to let someone else present the quarterly results because 'that's my report.' They've mentally owned that presentation for years. The solution there? Let them co-own it. If you say, 'This is still your data, but let's have Alex present the findings so you can focus on the strategic Q&A,' you reduce the threat to their ownership. Luna: So the principle is: don't try to take something away. Instead, offer a different kind of ownership or make the trade-off explicit. Lucas: Right. And this also applies to how you protect your own projects from the endowment effect. I've seen people dig in on failed initiatives because they couldn't admit the sunk cost, and the endowment effect is the emotional driver behind that. If you find yourself getting irrationally attached, you can ask an independent colleague to give you a brutally honest valuation. Outsiders don't have the endowment bias. Luna: That's a good self-awareness check. I also think the endowment effect explains why people hoard information. Knowledge is a kind of property. If you're the only one who knows how to run the legacy reporting tool, you've endowed that knowledge with huge value. Lucas: Exactly. And that's often a political strategy — people consciously or unconsciously create information monopolies. But if you're the manager, you want to break that monopoly without triggering a defensive response. One approach is to ask the person to document the process as a 'legacy knowledge transfer,' framing it as an investment in their own career. You're saying, 'We value your expertise so much we want you to codify it — that's a form of ownership too.' Luna: That frames documentation as an expansion of their influence, not a reduction. Nice. Lucas: There's also a fascinating organizational angle. Companies with strong cultures of individual ownership — like heavy use of 'this is my project' language — tend to see more intense endowment effects. That can be good for accountability but bad for cross-functional collaboration. Google's '20% time' was an attempt to create distributed ownership so people didn't cling to a single project. Luna: But even at Google, some teams got territorial. I remember a case where two teams both wanted to own the same machine learning model. The company had to create a joint ownership structure with explicit metrics for each team's contribution. Lucas: That's a smart governance hack. The key takeaway is that the endowment effect is wired into us — it's not a sign of bad character. The best political actors recognize it in themselves and others, and they design systems that diffuse it rather than fight it head-on. Luna: It really makes you think about how we assign credit, too. If someone feels they own the success of a project, they'll fight harder to keep it, even if a different approach would be better for the company. Lucas: Right. And that can lead to office politics that undermine the company's goals. A good leader normalizes letting go — celebrating people who gracefully hand off a project. That counters the endowment effect by making ownership less scarce. Luna: So tomorrow in a meeting, if I see someone defending their project purely because 'it's mine,' I should try the trade-off question first. Lucas: Absolutely. And if you ever find yourself feeling that knot in your stomach when someone suggests changing your baby? Pause and ask: 'Am I defending this because it's good, or because it's mine?' Luna: If today was actually useful to you, the way these stay ad-free is listener support — buy me a coffee dot com slash fexingo. Lucas: Yeah, we've had listeners say they use these episodes in team meetings, and that's exactly why we keep the show free. If it's helped you think through a career move or handle a tricky conversation, that's the kind of support that keeps us going. Luna: So back to the endowment effect — one last thing. I've noticed that the effect is stronger when we've put physical effort into something. Like if you hand-crafted a report versus just reading one someone else made. Lucas: That's actually the IKEA effect — closely related. But you're right. The more labor we invest, the more we overvalue. So when you're trying to persuade someone to let go of a project, acknowledge the effort they've already put in. Say, 'I know you've spent 500 hours on this. That effort shouldn't be wasted — but we can repurpose some of the components.' That validates their endowment without committing to the full project. Luna: Validation without escalation. Good script to have in your back pocket. Lucas: Next time you're in a negotiation over resources or priorities, try noticing whose endowment effect is in play. It's probably everyone's — including yours. Luna: I'll be watching for it. And if you want more episodes like this, you know where to go. For now, I'm Luna. Lucas: And I'm Lucas. See you next time.