Latest / The Office Politics Podcast with Fexingo: Workplace Dynamics, Influence, and Getting Things Done / How to Say No Without Sabotaging Your Career
Transcript
- Lucas: There's this moment every ambitious professional knows — your manager slides into your DMs or stops by your desk with that look, and before they've even finished the sentence, you feel your calendar screaming at you. But you nod and say yes anyway. Luna: Right — because saying no feels like career sabotage. Like you're signalling you can't handle it. Lucas: Exactly. And that instinct is so deeply wired that most of us treat 'no' like a four-letter word. But here's the thing — there's actually strong data that the people who learn to say no strategically end up with better performance ratings and more influence than the people who say yes to everything. Luna: Wait — better ratings? I thought the whole point of being a team player was to be the person who always steps up. Lucas: That's the conventional wisdom, and it's what gets burned into us early in our careers. But a Harvard Business Review study from a couple of years ago tracked employees over several performance cycles and found that those who selectively declined requests — especially low-visibility, high-effort work — received 11 percent higher performance ratings on average than peers who never said no. Luna: Eleven percent — that's meaningful. But I have to imagine the 'how' matters as much as the 'whether.' You can't just say 'no' and walk away. Lucas: You cannot. And that's the real skill. There's a product manager I've followed — let's call him James — who works at a mid-size SaaS company. Last year, in a single quarter, he was asked to take on four separate projects that were outside his core scope. He turned down all four. Luna: Four? In one quarter? That sounds like a fast track to being seen as difficult. Lucas: It would be, except James used a framework I'd call the 'decision tree for refusal.' Every request, he ran through three filters before responding. First: what is the visibility of this work to the people who matter for my growth? Second: what is the cognitive load relative to my existing commitments? Third: who is actually accountable for the outcome? Luna: Okay — the accountability filter is interesting. Because if you're just helping someone else's project, you get the work but not the credit. Lucas: Exactly. James's third filter really is about ownership. If the project succeeds, will you be recognized? If it fails, will you be blamed? If neither — that's a pure favor, and favors should be rare. So in his case, three of the four requests were low-visibility, high-cognitive-load, and he'd be a supporting player with no real accountability. He said no to those. Luna: What about the fourth one? Lucas: The fourth was actually high-visibility — it came from a VP who had a pet project. But James realized the cognitive load would crater his main deliverable, which was already behind. So he said no to the full request, but he offered an alternative: I can give you two hours of structured feedback on your spec, and I'll recommend someone from my team who can contribute without sacrificing our roadmap. Luna: That's a 'no' that sounds like a 'yes' — he offered value, but on his terms. Lucas: Exactly. And that's the template that works. The research backs this up — when you say no and immediately offer a smaller, bounded alternative, you're seen as helpful and strategic, not obstructionist. The VP in this case appreciated it, because it was more useful than a flat refusal or a reluctant yes that would have led to half-baked work. Luna: So what about the soft no? You know, the 'I'd love to, but I'm so swamped' approach. I've used that myself, but I always feel like it's transparent. Lucas: The soft no often backfires for exactly that reason. Managers can smell it. And it doesn't give them a path forward. A better approach is what I call the 'data-backed tradeoff.' You say: 'I can take this on, but here's what will slip — your timeline on Project X moves from Friday to the following Wednesday. Is that acceptable?' Luna: That's brilliant — it puts the choice on them. You're not refusing; you're making the tradeoff explicit. Lucas: Right. I once worked with a software engineer who used this constantly. He'd say, 'If I attend this meeting, I lose three hours of coding time. That means the release is delayed by a day. Are you okay with that?' And nine times out of ten, the requester would say, 'Never mind, I'll send you a recap.' He was respected for his honesty, not punished. Luna: But there's a risk, isn't there? If you do this too often, you might be seen as inflexible or not a team player. Where's the line? Lucas: The line is about frequency and relationship. If you're saying no to everything, you have a different problem — you're probably in the wrong role or you're hoarding your time. But the data shows that selective refusal, when done with transparency and an alternative, actually increases your standing. One study from Columbia Business School found that people who say no to requests that are outside their expertise are rated as more competent, not less. Luna: So it's about being known for what you say yes to, not what you say no to. Your brand becomes quality over quantity. Lucas: That is exactly it. Your 'yes' should mean something. If you say yes to everything, your yes is worthless. But if you're known as someone who only takes on work that you can do exceptionally well, then when you say yes, people know it's going to be great. Luna: James, the product manager — did he face any pushback after turning down those four projects? Lucas: He did get some initial resistance from one stakeholder who felt brushed off. But James followed up with a one-page document explaining his current capacity and prioritization — and he offered to revisit the request the following quarter. That stakeholder later told him it was the most transparent interaction he'd had with anyone on the product team. Luna: So the documentation piece matters too. It makes the no feel data-driven rather than personal. Lucas: Absolutely. When you can point to concrete numbers — 'I'm currently working on three projects totaling 40 hours a week' — it's not about you being difficult. It's about math. And nobody can argue with math. Luna: I want to bring up something I've seen — the person who says yes to everything often ends up burning out and producing mediocre work across the board. That can't be good for their reputation either. Lucas: It's worse. There's an academic concept called 'the dilution effect' — when you spread your effort across too many tasks, the quality of each one drops. And people remember the one thing you dropped the ball on more than the ten things you delivered okay. So the yes-everywhere strategy actually amplifies your surface area for failure. Luna: That's a great way to frame it. So for someone listening who's a chronic yes-er, what's the first step tomorrow morning? Lucas: Start with one sentence. When a new request comes in, say: 'Let me check my priorities and get back to you in an hour.' That buys you time to run the three filters we talked about — visibility, cognitive load, accountability. Then come back with either a yes, a no with an alternative, or a tradeoff question. Don't answer on the spot. Luna: The pause changes the power dynamic. You're not a vending machine that dispenses 'yes' when someone pushes a button. Lucas: Exactly. You're a strategic partner. And that's how you get things done — by doing fewer things better. It's counterintuitive, but in a world of constant requests, the most valuable skill might be knowing what to decline. Luna: Alright, I'm going to try that 'let me check my priorities' line tomorrow. But I'm curious — do you have a personal rule for when you absolutely say yes no matter what? Lucas: I do. Two conditions have to be met: the work is visible to people I want to impress, and I can do it at a level that reinforces my reputation. If either is missing, I'm inclined to say no. And I always try to leave room for the occasional pure favor — but those are rare, and they should feel generous, not obligatory. Luna: So maybe the real office politics play isn't about maneuvering — it's about being deliberate with your yes. Lucas: I think that's the most underrated career advice there is. Be known for the quality of your yes, not the quantity.