Latest / The Difficult Boss Podcast with Fexingo: Managing Up, Toxic Managers, and Workplace Survival / How to Push Back on a Boss Who Always Says Yes
Transcript
- Lucas: So Luna, I want to start with a question. Have you ever had a boss who says yes to everything? Every request, every new project, every 'quick favor' from another department — it's all 'sure, we can do that.' Luna: Oh, absolutely. My last manager was exactly like that. He'd agree to a new dashboard request in a meeting, and then we'd find out two days later that the deadline was 'as soon as possible.' Lucas: Right. And that's the thing — a boss who never says no might sound like a dream compared to the roadblock type, but it's actually one of the more corrosive dynamics in a workplace. Because every yes carries a hidden cost, and the boss isn't the one paying it. You and your team are. Luna: So this is kind of the flip side of the micromanager or the credit-stealer. This is the boss who overcommits you. Lucas: Exactly. And today I want to dig into how you actually push back on a boss who says yes to everything — without making them feel like you're the one being difficult. Luna: Because if they're agreeable, you'd think they'd be open to a conversation. But sometimes that agreeableness is just a way to avoid conflict with everyone else. Lucas: That's the key insight. The boss who says yes to you is the same person who says yes to their boss, to clients, to anyone with a request. They're conflict-averse, and that means they'll say yes to the last person who asked. So you need to become the person who makes it easy for them to say no. Luna: So how do you do that without just being another person pushing back? Lucas: Well, a few years back I covered a story about a mid-sized SaaS company, maybe two hundred people. The sales leader kept promising custom features to enterprise prospects, and the engineering manager was the one who had to deliver. Every sprint, the scope grew, and the team was burning out. The engineering manager tried the direct approach — 'we can't do this' — but the sales leader would just escalate to the CEO, and the CEO would say, 'figure it out.' Luna: Classic. So what did they do? Lucas: The engineering manager changed the frame. Instead of saying 'no,' she started saying 'I want to say yes, here's what I need.' She'd bring a list of every active project, the team's capacity, and the impact of adding one more thing. She'd say, 'We can absolutely tackle this, but it would push the Q3 platform upgrade to December. Is that the right priority?' Luna: So she made the trade-off explicit. Instead of just refusing, she forced the conversation about what gets dropped. Lucas: Exactly. And that's the core tactic I want to get into today. You're not saying 'no' to your boss. You're saying 'yes, but here's the cost.' And you're putting the decision back where it belongs — on them. Luna: Before we go deeper — a quick pause. If this conversation has helped you think through a tricky boss situation, it costs a couple of dollars a month to keep these episodes going. That's buy me a coffee dot com slash fexingo. Every little bit genuinely keeps us ad-free. Lucas: Yeah, and we appreciate anyone who's been able to chip in. It makes a real difference. Luna: So back to that engineering manager. She brought the list, but the sales leader still pushed back. What happened next? Lucas: She scheduled a weekly triage meeting with the sales leader and the CEO. Every Friday, thirty minutes, just to review the priority list. She'd start with, 'Here's what we committed to this week, here's what's asking for time, and here's what I think we should drop if we take on anything new.' Luna: That's a big time commitment. Did it actually work? Lucas: It did, because it made the cost of 'yes' visible on a regular basis. The CEO started to see that every new feature meant a delay on something else. And the sales leader had to justify why a client request was more important than a product roadmap item. It forced a conversation they'd been avoiding. Luna: So the key is to move from a reactive 'no' to a proactive 'here's the trade-off.' Lucas: Right. And there's a specific phrase that works really well. Instead of 'we can't do that,' you say, 'We can do that, and here's what we'd have to delay.' That simple reframe changes the whole dynamic. You're not being negative; you're being helpful. Luna: But what if your boss still says yes to everything, even after you present the trade-offs? Some bosses just can't say no, no matter what. Lucas: That's when you need to escalate the visibility. If your boss won't make the call, you bring the conflict to the surface. In that SaaS company, the engineering manager started sending a weekly one-pager to the CEO and the sales leader, summarizing the team's capacity and the list of requests. She didn't editorialize, just facts. After three weeks, the CEO started asking questions directly. Luna: So you're using transparency as a tool. The boss's yes becomes public, and they have to own the consequences. Lucas: Exactly. And that's often enough. When their own boss sees that they're overcommitting the team, they start to rein it in. But there's another layer to this — the emotional one. A boss who says yes to everything is often afraid of looking incompetent or unhelpful. They think saying no makes them look weak. Luna: So part of managing up is making it safe for them to say no. Lucas: Yes. You can say things like, 'I know you want to help them out, and I do too. Let's figure out how to do that without killing the team.' That acknowledges their good intentions, so they don't feel attacked. It's a subtle thing, but it changes the conversation from 'you're wrong' to 'we're on the same side.' Luna: That sounds like it requires a lot of emotional labor though. Is there a point where you just have to give up and look for a new job? Lucas: That's the honest question. If you've tried the trade-off conversation, you've made the costs visible, you've given them an easy out, and they still don't change — then yes, this might be a systemic issue. A boss who says yes because they're conflict-averse is unlikely to change unless there's a real consequence. Luna: So before you get to that point, what are the practical steps for someone listening right now? Lucas: First, start documenting. Write down every request, every deadline, every 'sure, we can do that.' Second, in your next one-on-one, bring that list and say, 'I want to help you make the best decisions about where we spend our time. Here's what we've got.' Third, use the phrase 'I want to say yes, here's what I need.' Luna: And what if they still brush it off and say 'just make it work'? Lucas: Then you escalate to a written summary after the meeting. Something like, 'Just to confirm, you're saying we should prioritize the client report over the marketing campaign. We'll shift our focus accordingly.' That puts the decision in writing, and if it comes back to bite them, they can't pretend they didn't know. Luna: That's a classic but it works. It forces accountability without being confrontational. Lucas: And one more thing — don't do this alone. If you have peers in the same situation, coordinate. When multiple people start pushing back consistently, the boss can't ignore it. They might have to confront their own behavior. Luna: So it's about building a movement, not just a one-off conversation. Lucas: Yeah, and the end goal isn't to make your boss look bad. It's to get the team to a sustainable pace. When you frame it as 'I want us to deliver high-quality work on time,' that's a goal your boss can't argue with. Luna: Let's say someone does all of this and their boss is still a yes-machine. How long do you wait before deciding it's a lost cause? Lucas: I'd say give it a couple of months of consistent effort. If you've held the line, made the trade-offs visible, and nothing changes, then you have to weigh whether the job is worth the stress. No one should have to be the bad cop for someone who can't say no. Luna: That's a good place to leave it. I think the takeaway is that you're not the one being difficult — you're the one being realistic. Lucas: Exactly. And remember, the goal is to protect your team's time, your sanity, and the quality of the work. That's never the wrong move.