Latest / The Office Politics Podcast with Fexingo: Workplace Dynamics, Influence, and Getting Things Done / The Hidden Cost of Saying Yes Too Fast at Work
Transcript
- Lucas: Let me tell you about a woman named Priya. She was a marketing manager at a mid-sized tech company, solid reputation, up for a senior director role. Then she agreed to lead a cross-functional task force on data governance. Luna: Oh, that sounds like a death sentence for her promotion. Lucas: Exactly. It wasn't in her job description, it took fifty hours a month, and it had zero visibility with the VP who made promotion decisions. She said yes because she wanted to be seen as a team player. Luna: And the VP saw her as someone who could be distracted from core work. Classic trap. Lucas: This is what I want to talk about today — the hidden cost of saying yes too fast. We all know that no can be powerful, but most of us operate on a default of yes, especially when the ask comes from a peer or a senior stakeholder. We assume that yes builds political capital. Luna: But in Priya's case, it actually eroded it. She missed her own quarterly targets because she was in data governance meetings. Lucas: Right. And the irony is, the people who asked her to join the task force — they weren't going to advocate for her promotion. They just needed a warm body. So her yes cost her focus, and it cost her the narrative that she was a high-impact marketing leader. Luna: Where does this yes-default come from? I think a lot of us are trained to be helpful from day one. Performance reviews literally say 'collaboration' is a core competency. Lucas: Exactly. And Adam Grant has written about this — the 'giver burnout' curve. Givers who say yes indiscriminately end up at the bottom of the performance distribution. The ones who succeed are the ones who protect their time and say yes only to high-impact requests. Luna: So it's not about being selfish. It's about being strategic. Lucas: Right. And there's a specific framework I want to share. It's three questions you ask yourself before you even open your mouth. Question one: Does this request directly advance my core priorities or those of my team? Luna: So if it's data governance and you're in marketing, that's a no. Lucas: Unless your core priority is to build data governance skills for a future role. But for Priya, it wasn't. Question two: Who else could do this, and what would the political fallout be if I decline? Luna: That's the lens I think most people miss. You're not just evaluating the task, you're evaluating the asker. Lucas: Exactly. If the ask comes from a powerful sponsor, a strategic no might be a bad idea. But if it's from a peer with no influence over your career, you have more room. Question three: What is the opportunity cost of saying yes? Luna: That's the one that really gets at the hidden cost. Every yes is also a no to something else. Lucas: And for Priya, the opportunity cost was the time she could have spent on a high-visibility project that actually demonstrated her readiness for senior director. She had a clear choice, and she chose the task force. Luna: I want to push back a little. There's a real risk that saying no too often makes you look difficult. Especially if you're a woman or a person of color, the social penalty for saying no can be higher. Lucas: That's a really important point. The research does show that perceptions of assertiveness differ across demographics. So the framework has to be adapted to your context. But the solution isn't to say yes to everything — it's to have a better scripting toolkit for the no. Luna: Give me an example of a script that works for a high-risk ask. Lucas: Let's say your VP asks you to join a last-minute presentation for a client. You have a major deadline the next day. You could say, 'I can't give this the attention it deserves right now because I'm focused on deliverable X. But I can review your slides tonight or connect you with someone who has more bandwidth.' Luna: That's good — you're offering an alternative. It shows you're still helpful, just not available. Lucas: And you're framing it as protecting the quality of their request, not as rejecting them. That's the key. The no should be about the work, not the person. Luna: There's another scenario I've seen a lot — the meeting invitation that should have been an email. Someone wants '15 minutes to pick your brain.' Lucas: Oh, that's a classic. And the cost of that meeting isn't just the 15 minutes — it's the switching cost. You lose focus for 20 minutes before and 20 minutes after. So that one yes actually costs an hour of productivity. Luna: So what's the script there? Lucas: You could say, 'I'd love to help, but my calendar is tight. Could you send over your top three questions by email? I'll reply with a quick voice memo or a few bullet points.' That way you're still generous, but you control the time. Luna: That's smart. And honestly, if today was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. We keep the show ad-free, and listener support is what makes that possible. Lucas: Yeah, it's a small way to say this content matters to you. And we appreciate every single one. So, back to the framework — the third question about opportunity cost. I think most people underestimate how much their 'yes' reputation can actually hurt them. Luna: How so? Isn't being known as the person who always says yes a good thing? Lucas: Not if it means you're overloaded and delivering average work. I saw a study from a large tech company — they looked at internal mobility data. Employees who were rated as 'highly responsive' to cross-functional requests were actually less likely to get promoted than those who were selective. The high-responsiveness group had lower performance ratings because they were spread too thin. Luna: That's the data we need. So being selective isn't just about your own sanity — it's a career strategy. Lucas: Absolutely. And the key is to build a reputation as someone who says yes to the right things. You want to be known for a few high-impact contributions, not for being the office utility player. Luna: What about when you've already said yes and you realize it was a mistake? How do you unwind that without looking flaky? Lucas: That's a great question. First, don't wait too long. The longer you stay in, the harder it is to leave. Second, frame it as a reassessment of priorities, not as a failure. You can say, 'I've been reviewing my capacity, and I realize I can't do justice to this project while also meeting my commitments on X. I want to make sure this doesn't suffer, so I'd like to step back and help find a replacement.' Luna: That's honest and respectful. You're taking ownership of the mistake without blaming yourself. Lucas: Exactly. And people will respect you more for being honest than for overdelivering poorly. So the takeaway today is: before you say yes, pause. Run the three questions. And if the answer is no, have a script ready that protects the relationship. Luna: I think the hardest part is just giving yourself permission to say no. We're so conditioned to be helpful. Lucas: True. But remember — your most valuable resource at work isn't your skill or your connections. It's your attention. Guard it like a political asset. Luna: And if you need a script, we've given you a couple. Practice them. It gets easier. Lucas: Next time, we'll talk about how to read a room during a tense meeting — but for now, think about one request you can say no to tomorrow.