Latest / The Office Politics Podcast with Fexingo: Workplace Dynamics, Influence, and Getting Things Done / How to Navigate Workplace Coalitions Without Becoming a Pawn
Transcript
- Lucas: You know that moment when a colleague pulls you aside after a meeting and says, 'Hey, just between us, I think we should align on the Q3 roadmap before the steering committee meets'? Luna: Oh, I know that moment. It feels flattering at first, like you've been let in on something. Lucas: Exactly. And that's exactly how coalitions recruit you. Today I want to talk about workplace coalitions — the informal, often invisible alliances that shape decisions and careers way more than the org chart suggests. Luna: We haven't done a whole episode on coalitions yet, and I think it's one of the most under-discussed dynamics in offices. Lucas: Completely agree. So let's anchor on a real example. I came across a case from a mid-sized SaaS company — call it CloudBridge Analytics, about eight hundred employees. A junior product manager named Sarah was assigned to a cross-functional initiative to overhaul the customer onboarding flow. Luna: Right, the kind of project that gets visibility from VPs. Lucas: Exactly. Within two weeks, Sarah noticed that every time the engineering lead, Mark, spoke in meetings, the sales director, Priya, would subtly push back. Not aggressively — just a raised eyebrow, a 'let's be realistic about timelines,' a pointed look at Sarah when she presented the engineering team's estimates. Luna: So Priya was trying to recruit Sarah into an anti-Mark sentiment. Lucas: Bingo. Priya would say things like, 'Sarah, you're the one who has to deliver this. Don't let engineering overpromise and leave you holding the bag.' Sounds like good advice, right? But what Priya was really doing was building a coalition to pressure Mark into accepting a faster timeline that sales needed for their Q4 numbers. Luna: And Sarah — she's twenty-six, two years out of B-school, first time leading a cross-functional project. She's got no idea she's being played. Lucas: She doesn't. She starts siding with Priya in meetings. She rephrases engineering's estimates as 'aspirational.' She pushes Mark to commit to dates he's not comfortable with. The coalition works: the project gets a compressed schedule, sales gets their timeline, but the product ships with bugs. Six months later, when annual reviews come around, Sarah's manager notes 'struggles with stakeholder alignment.' She's passed over for promotion. Luna: And Priya? She got her bonus for hitting the Q4 number. Mark? He had emails protecting himself. Sarah was the only one left exposed. Lucas: That's the classic pattern. Coalitions are not inherently bad — they're just informal networks of mutual benefit. But when you join one without understanding the full landscape, you become a pawn in someone else's game. Luna: So how do you detect a coalition forming before you're inside it? Lucas: I think the first signal is private conversations that reference other people's motives. If someone says, 'I'm not sure Bob is really thinking about what's best for the team here,' that's a recruitment pitch disguised as a confidence. The second signal is when someone offers you information you didn't ask for — 'Did you know the CFO pushed back on the marketing budget last quarter?' That's a gift meant to create obligation. Luna: The gift of gossip. And once you've accepted it, you're implicitly in the coalition. Lucas: Exactly. So rule one: before you align with anyone on a sensitive topic, ask yourself — what does this person want that I can't see? And rule two: never take a side in a coalition until you understand the full set of stakeholders and their incentives. Luna: That's harder than it sounds, because coalitions often form around issues that feel urgent. You don't have time to map the whole system. Lucas: That's true, but you can buy time. A simple phrase like, 'I want to think about that from all angles — can we pick this up tomorrow?' That one day gives you space to ask around, maybe talk to someone outside the immediate coalition. Luna: You know, this episode feels like exactly the kind of practical career advice that we hear listeners say they wish they'd had earlier. Lucas: That's the whole point of this show. And honestly, if today's episode was worth even a coffee to you, that's the link — buy me a coffee dot com slash fexingo. Listener support is what keeps this podcast entirely ad-free, and it means we can keep doing deep dives like this without worrying about sponsors. Luna: Yeah, it's a small gesture that has a huge impact on our ability to make the show exactly the way we want. So thank you to everyone who's already chipped in. Lucas: Alright, back to coalitions. So let's say you've spotted a coalition. Now the question is: do you join, stay neutral, or try to bridge the gap? Luna: I think neutrality is often the smartest play, especially early in your career. But doesn't that risk alienating both sides? Lucas: It can, if you're passive about it. But active neutrality is different. You say, 'I see that both engineering and sales have valid concerns. My goal is to find a path that works for the customer and the business. Let me come back with some options next week.' You're not avoiding the conflict — you're reframing your role as a problem-solver, not a faction member. Luna: That works if you have the credibility to pull it off. If you're a junior employee, people might see you as indecisive. Lucas: That's a real risk. So here's a tactic: before you declare neutrality, build a relationship with the most senior person who is NOT part of any coalition. Every organization has a few of those — people who are powerful enough to be above the fray. If you can get that person's informal backing, neutrality becomes strength. Luna: Like the VP of Product who's been around fifteen years and has seen every coalition rise and fall. Lucas: Exactly. They know that coalitions tend to burn out after six to twelve months. The people who survive are the ones who delivered results without being captured by any group. Luna: But what if your boss asks you to join a coalition? That's a harder situation. Lucas: That's the hardest. Because you can't just say no. But you can ask questions that reveal the risk. 'If we align on this timeline, what happens if we miss it? Are we comfortable with that trade-off?' Sometimes your boss hasn't thought through the downside. And if they have, you now know the real stakes. Luna: I've seen people get trapped exactly that way. Their boss says, 'I need you on my side for the budget meeting,' and they say yes without asking what happens if they lose. Lucas: Right. And losing a coalition battle can be worse than never joining. Because you've publicly picked a side, and if that side loses, you're associated with the loss. Your political capital takes a hit. Luna: So what's the single best question to ask before joining any coalition? Lucas: I think it's: 'If this coalition succeeds, who benefits most?' Not who benefits — who benefits MOST. Because that person is the real driver. Everyone else is a supporter. And if that person isn't you, you need to ask what you're getting in return that's worth the risk. Luna: And what if the answer is 'you'll get visibility with the CEO'? Is that enough? Lucas: It depends. Visibility is valuable, but it's also risky. If the coalition fails, the CEO remembers you as the person who was part of the faction that caused a problem. I'd rather have visibility for a specific deliverable than for being on the winning side of a political fight. Luna: That's a good rule. Deliverable-driven visibility over coalition-driven visibility. Lucas: Exactly. And here's an interesting data point: a study from the Harvard Business Review on workplace networks found that the most influential people in organizations were not the ones with the most coalition ties — they were the ones who bridged disconnected groups. They had relationships across silos, but they didn't take sides. Luna: So the goal is to be a connector, not a soldier. Lucas: Yes. And that's harder work, because it requires you to understand the interests of multiple groups and find common ground. But it builds a reputation that lasts beyond any single coalition. Luna: I'm thinking back to Sarah at CloudBridge. If she'd had that insight, she might have gone to Mark and Priya separately and said, 'I see you both want a successful launch. Let me help you find a timeline that works for both.' Instead of being pulled into Priya's camp. Lucas: Exactly. And she would have come out of that project with allies in both camps, not enemies in one. Luna: So what's the one takeaway you want listeners to remember? Lucas: Coalitions are not the enemy — but joining one without understanding the full map is. Before you align, ask: who benefits most, what's my exit strategy, and what am I trading away? If you can't answer all three, stay neutral and build bridges instead. Luna: That's a solid framework. And it's one I wish I'd had in my first job out of college. Lucas: Same here. I got burned by a coalition in my second year as a reporter — someone promised me a scoop if I shared my sources. I shared, he got the story, I got nothing. I learned the hard way. Luna: And now you're teaching it to thousands of listeners. That's a pretty good redemption arc. Lucas: Ha, I'll take it. Next week we're going to talk about something I think is even trickier: how to manage up when your boss is a coalition-builder themselves. That's a whole different level of complexity. Luna: Looking forward to it. For now, if today's episode gave you a new lens on your own workplace, we'd love to hear about it. You can find us at the show's website, or support the show at buy me a coffee dot com slash fexingo. Lucas: And as always, keep your eyes open and your coalitions optional. See you next time.