Latest / The Office Politics Podcast with Fexingo: Workplace Dynamics, Influence, and Getting Things Done / How to Disagree With Authority Without Getting Fired
Transcript
- Lucas: There is this moment in almost every career where you know your boss is about to make a bad call, and you have maybe ten seconds to decide whether you speak up or let it happen. Luna: And the instinct, for a lot of people, is to stay quiet, because the risk of being seen as difficult or insubordinate feels bigger than the risk of a bad outcome. Lucas: Right. But the thing is, staying quiet has its own cost. You lose credibility with yourself, and eventually the team sees that you knew something was wrong and didn't say anything. So today I want to look at the actual mechanics of disagreeing with authority — not the theory, but the specific moves that make it work. Luna: Give me an example where someone actually pulled this off. Lucas: So there is a case I came across from a software engineer at a Fortune 50 company — I'll keep the names out — who was in a planning meeting where the VP of product presented a roadmap that the engineer knew, from the data, was going to fail. The timeline was too aggressive, the feature set was misaligned with what customers actually wanted, and the engineering team was already stretched thin. Luna: So what did he do? Did he stand up and say 'this is a bad plan'? Lucas: No, and that is exactly the wrong move. Instead, he waited until the meeting ended, caught the VP in the hallway, and said, 'Hey, I think there's some data around customer usage that might change how we prioritize this. Can I show you what I'm seeing before we lock in the timeline?' Luna: So he changed the venue and the framing. He didn't challenge the plan publicly, he offered help. Lucas: Exactly. And that is move number one: depersonalize the disagreement. You are not saying the VP is wrong. You are saying the data is worth looking at. That distinction matters more than almost anything else. Luna: What happened next? Lucas: The VP agreed to a fifteen-minute review the next morning. The engineer came in with a one-page summary — three bullet points on what the usage data showed, two options for how to adjust the roadmap, and a recommendation for which option was best. He did not bring slides, he did not bring a deck, he did not bring a laundry list of problems. Luna: He packaged it as a decision aid, not a complaint. Lucas: Right. And that is move number two: bring a solution, not a problem. Most people who disagree with authority stop at saying what is wrong. That just makes you a critic. The person who says what is wrong and offers a better path — that person becomes a partner. Luna: Did the VP actually change the plan? Lucas: Yes. The VP looked at the data, saw the engineer had thought it through, and adjusted the timeline by two weeks. But here is the part I find most interesting: the VP also started including that engineer in the quarterly planning sessions from then on. The pushback earned him a seat at the table. Luna: That is a huge outcome from a hallway conversation. But it also required the VP to be the kind of leader who can handle pushback. Not all bosses are. Lucas: That is the real variable. And it brings us to move number three: calibrate to the person. Some leaders want data, some want consensus, some want loyalty first. You have to read the room before you decide how to frame the pushback. Luna: How do you read that in real time? Lucas: Look at how they react to disagreement from peers. If a VP pushes back on another VP in a meeting and the boss handles it well, that is a signal. If the boss shuts it down, you need a different approach — maybe a private conversation, maybe an email with data attached, maybe you find an ally above them. Luna: So the first step is not deciding what to say. It is deciding how this person processes challenge. Lucas: Exactly. And let me give you the flip side. I had a friend at a startup where the CEO had a rule: no one could openly question a decision in a meeting. The culture was total loyalty. So when the CTO saw the CEO was about to sign a bad vendor contract, he wrote a two-paragraph note, sent it an hour before the signing meeting, and titled it 'One thing to consider before the vendor call.' Luna: And did it work? Lucas: The CEO ignored it, signed the contract, and the company lost about four hundred thousand dollars. But here is the thing: the CTO kept his job. He made the pushback private, respectful, and non-urgent. He did not embarrass the CEO. And six months later, when the CEO needed someone to clean up the mess, he turned to the CTO. Luna: So even when the pushback does not change the immediate outcome, it can still build your reputation as someone who is thoughtful and loyal. Lucas: That is a critical point. The goal of strategic pushback is not always to win the argument. Sometimes the goal is to be seen as the kind of person who cares enough to try. Over time, that reputation compounds. Luna: I think one reason people avoid pushback is they imagine the worst-case scenario — getting yelled at, getting sidelined, getting fired. But the data suggests that is actually pretty rare if you do it right. Lucas: There is a study from Harvard Business Review a few years ago that looked at how employees who challenged their bosses were perceived. The ones who did it with data and a collaborative tone were rated higher on leadership potential by their managers than employees who never pushed back. The key was framing it as 'helping the team succeed' rather than 'I am right and you are wrong.' Luna: That aligns with the idea of issue ownership that I have heard you talk about before. The person who raises the problem should be willing to own part of the solution. Lucas: Yes, that is the hidden rule. If you bring a problem and then hand it to your boss to solve, you have not helped. You have added to their workload. But if you bring a problem and say 'I have looked at two options, here is my recommendation, I can run with it if you agree' — now you are a force multiplier. Luna: There is a moment in every career where you know your boss is about to make a bad call, and you have maybe ten seconds to decide whether you speak up or let it happen. That is exactly where we started today. And I think the framework of depersonalize, bring a solution, calibrate to the person — that gives people a real path. Lucas: Before we wrap, I want to acknowledge something. If this episode was useful to you — if it helped you think through a tricky conversation you are facing — the reason we can do deep dives like this without ads is listener support. It is a small thing, but if you go to buy me a coffee dot com slash fexingo, that helps keep this show independent and focused on what actually works in the workplace. Luna: Yeah, and it really does make a difference. Even a few dollars a month from people who find value here keeps us going without having to cram in sponsor reads. Lucas: So, back to the main thread. I want to leave you with one concrete test you can use before you push back on a decision. Ask yourself: after I say this, who owns the problem? If the answer is your boss, you probably should not say it yet. If the answer is both of you, or you, then you are in the right zone. Luna: That is a good filter. And if you are unsure about the boss's receptivity, the hallway test is a safe starting point. Keep it brief, keep it private, and let the data do the arguing. Lucas: Exactly. Next episode we are going to look at something that feels related but is actually very different: how to handle a situation where a peer takes credit for your idea in a meeting. That is a different kind of political challenge, and the playbook is not the same. Luna: Looking forward to it. For now, if you want to test the pushback framework, try it on something low-stakes first — a decision that matters but will not get you fired if it goes wrong. Build the muscle before you need it. Lucas: Good advice. Thanks for listening.