Latest / The Office Politics Podcast with Fexingo: Workplace Dynamics, Influence, and Getting Things Done / The Silent Career Killer No One Talks About
Transcript
- Lucas: There's a career killer that never gets a performance review mention. It's not poor results, it's not missing deadlines — it's being left out of the loop. And it's more common than most people realize. Luna: You mean like not getting invited to the meeting where the real decisions happen? Or the Slack channel where the project actually gets discussed? Lucas: Exactly. I'm talking about information withholding. Not the dramatic kind where someone hides a critical report. I mean the passive, almost deniable version: the email that never gets CC'd, the update that never reaches you, the 'oh, I thought someone told you' moment. Luna: Right — because if you point it out, you sound paranoid. The person can always say it was an oversight. Lucas: Exactly. And that's what makes it such an effective tool. There's a 2024 study from MIT Sloan that found 43 percent of managers admit to intentionally withholding information from colleagues they see as rivals. Not just competitors for a promotion — people they simply don't want to empower. Luna: Forty-three percent — that's huge. And it's managers admitting it, so the real number is probably higher. Lucas: Right. So let me give you a concrete case. I talked to a marketing manager at a major CPG company — let's call her Sarah. She was up for a senior director role. Her performance numbers were solid. But she noticed a pattern: her peer in a sister division would consistently 'forget' to include her on weekly status emails to the VP. Then when the VP asked about her project, she'd be caught off guard. Luna: So she looks unprepared in front of the decision maker. Classic. Did she ever confront the peer? Lucas: She tried. She sent a polite email asking to be added to the distribution. The peer apologized and said it was an automatic list issue. But nothing changed. Then she noticed she was also excluded from a secondary Slack channel where the team shared competitive intelligence. That channel had 12 people — everyone at her level in the division except her. Luna: That's deliberate. Twelve people — she's the only one missing. That's not a glitch. Lucas: Right. And what made it worse was that the peer was seen as collaborative and helpful by upper management. So if Sarah complained, she risked looking like the difficult one. This is the asymmetry of passive undermining — the person doing it maintains a positive reputation because their behavior is deniable. Luna: Did she get the promotion? Lucas: She did not. The VP told her in the feedback that her 'visibility' on cross-functional initiatives wasn't where it needed to be. Exactly the thing the information withholding was designed to create. Luna: Oof. So what can someone do? Because just working harder won't fix being invisible. Lucas: Right. There are three practical strategies. The first is building redundant information channels. Don't rely on one email list or one Slack group. Develop direct relationships with two or three people in every key function — people who will tell you things independently. Sarah eventually did this by scheduling biweekly one-on-ones with the peer's top analyst. Luna: So she created a human backup system. That's smart — the analyst isn't playing politics, she just shares what she's working on. Lucas: Exactly. The second strategy is what I call the 'pre-brief email.' Before any major cross-functional meeting, send a one-paragraph summary of what you plan to cover to all attendees, and explicitly ask if there's anything you've missed. CC the senior person. This does two things: it documents your proactive communication, and it forces the information hoarder to either share or reveal their silence. Luna: Because if they don't respond, and you present something incomplete, the paper trail shows you asked. That's protective. Lucas: Exactly. The third strategy is creating visible contribution markers — things that can't be omitted from the record. For example, volunteer to own the meeting notes and action items. Suddenly you're the one documenting decisions. Or take on the monthly dashboard update that goes to senior leadership. Those artifacts become your footprint. Luna: I actually saw this play out at a startup I worked at years ago. There was this quiet engineer — really talented — but he was being systematically excluded by the team lead from code review sessions. The lead would schedule them on a private calendar and then claim they were ad hoc. Lucas: Classic move. What happened? Luna: The engineer started a public 'design decisions' doc that he shared with the whole team and the CTO. Every time he had a question about an approach, he'd document his reasoning and ask for feedback in that doc. Suddenly, the lead couldn't exclude him from the discussion because it was all in writing and visible. Lucas: That's a perfect example of creating an artifact. He turned the game from 'who's in the room' to 'what's on the record.' Luna: Right. And it worked — the CTO noticed his contributions and he got promoted six months later. Lucas: So the through line here is: information withholding works only when the flow is opaque. The antidote is transparency — not just asking for information, but creating structures where information has to pass through you or be visible to others. Luna: It's almost like you have to build your own distribution list for your work. Don't rely on someone else to carry the message. Lucas: Exactly. And there's one more subtle layer. Sometimes the withholding isn't even malicious — it's just inertia. People default to the same five people they always talk to. If you're not one of those five, you get forgotten. Luna: So it's not always a villain. Sometimes it's just organizational gravity. Lucas: Right. And that's why the strategies work either way. Whether it's intentional or just lazy communication habits, building redundancy, pre-briefing, and creating artifacts all solve the problem. Luna: I want to go back to the MIT study. Forty-three percent of managers admitted to doing this. That's almost half. How do you even identify who's doing it to you? Lucas: Look for patterns over time. A single missed email is nothing. But if you consistently find out about decisions after they're made, if you're always the last to know about a deadline change, if your name is missing from project distribution lists — that's a pattern. Also pay attention to who controls the communication cadence. Luna: The gatekeeper of the weekly status report, the person who schedules the all-hands. Those are leverage points. Lucas: Exactly. And if you suspect you're being targeted, don't confront directly. Instead, start using the strategies we talked about. Create a shared project tracker. Propose a rotating note-taker role. The goal isn't to catch someone — it's to make yourself un-ignorable. Luna: What about when you're the manager? How do you prevent this from happening in your own team? Lucas: Great question. The single best thing a manager can do is mandate transparent communication tools. For example, require that all project updates go into a shared document, not email chains. Or use a team wiki where decisions are logged. And model it yourself — CC broadly, document your own reasoning publicly. Luna: So you set the norm. If the boss is open, it's harder for anyone to be closed. Lucas: Exactly. And hold people accountable when they say 'I thought you knew.' That phrase should trigger a conversation about process, not blame. Because the root cause is almost always a process failure, even when there's intent behind it. Luna: That's a good reframe. Instead of 'you didn't tell me,' it's 'how do we make sure information flows to everyone who needs it.' Lucas: Right. And that's the difference between playing the victim and playing the system. The people who get promoted aren't the ones who get offended by being left out — they're the ones who build mechanisms so they can't be left out. Luna: So the next time someone says 'I thought you were on that email,' instead of getting frustrated, I should just start writing a shared doc. Lucas: Exactly. Turn the moment of exclusion into a moment of system design. It's less dramatic, but it works.