Latest / Office Hours with Fexingo: Daily Career Q&A, Workplace Questions, and Professional Advice / How to Get Your Boss to Say No More Often
Transcript
- Luna: Lucas, I want to pitch you a paradox. The boss everybody wishes they had is the one who says yes to everything. Open door, supportive, never shoots down an idea. But if you actually work for that boss, you're probably drowning in low-priority work. Lucas: That's the exact tension. We glorify the 'yes' leader, but the data suggests it's not serving anyone. Microsoft's 2024 Work Trend Index found that the average knowledge worker spends 57 percent of their time on activities that feel low-impact. A lot of that comes from managers who can't triage. Luna: Fifty-seven percent. So more than half your week could be stuff that doesn't move the needle, and your boss greenlit it. How do you even start a conversation like that without seeming like you're trying to do less work? Lucas: That's the skill. You're not asking your boss to do less. You're asking them to help you focus on what matters most to them. And the framing matters a lot. I've seen people use what I call the '50 percent rule.' You go into a one-on-one and say, 'I want to make sure the top half of my priorities gets 80 percent of my energy. Can we identify the bottom 50 percent you'd be okay with me deprioritizing or deferring?' Luna: So you're not naming any project as unimportant. You're letting your boss decide which ones are less urgent. That's smart. It's a collaborative reframe, not a complaint. Lucas: Exactly. And most bosses will actually feel relieved. They're often overwhelmed themselves and just handing down everything because they can't filter. When you give them permission to say no, they'll take it. I once had a manager who, after I used that framing, literally said, 'Oh thank god, I was going to suggest that but didn't want you to think I didn't trust you.' Luna: But not every boss is that self-aware. What about the manager who sees every request as a growth opportunity? The 'stretch' boss who loads you up because they think it builds your resume. Lucas: That's a trickier dynamic. With that type, you need to reframe the risk. Instead of saying 'I'm too busy,' you say, 'I want to make sure I can deliver excellence on the projects you care about most. If I take on X, I'm worried Y will slip to a B-minus effort. Is that acceptable?' Now you're not complaining about workload — you're protecting quality, which is a value they share. Luna: So you're making it about their reputation. 'I want this thing you care about to be excellent.' That's a strong move. I've also heard of people using a 'stop doing' list in one-on-ones. Instead of just adding tasks, you agree to drop something first. Lucas: The stop-doing list is a classic. I'd pair it with a weekly 'capacity check.' Every Monday, you send your boss a short list of your top three priorities for the week and say, 'If anything else comes up, what should I deprioritize to make room?' That turns the 'no' into a recurring conversation instead of a once a quarter confrontation. Luna: That's a good habit. And it builds trust over time. Your boss starts to see you as someone who thinks strategically about their own time. Which, honestly, is a leadership quality. Lucas: Speaking of building trust — it's worth noting that this whole approach only works if you've already delivered on the things you said were priorities. You can't ask your boss to help you focus if you haven't shown you can execute. The credibility has to come first. Luna: Right. So the sequence is: prove you can deliver, then start negotiating the pipeline. That makes sense. And if you're early in a new role, maybe you just absorb for the first 90 days before having this conversation. Lucas: I would say 90 days minimum. In your first quarter, you're still learning what's actually important. If you start pushing back too early, you look like you're not a team player. But after you've shipped a couple of wins, you've earned the right to be selective. Luna: I want to push back on one thing though. Isn't there a risk that by constantly asking your boss to say no, you're basically volunteering to be the person who never gets the stretch assignment? The safe person, not the high-potential one? Lucas: That's a legitimate concern. And it can happen if you frame it wrong. The key is to differentiate between 'no, I can't do this' and 'no, I can't do this AND maintain excellence on the thing you told me was your top priority.' If you always tie it back to a shared goal, you're not seen as less ambitious — you're seen as someone who understands trade-offs. That's a senior skill. Luna: So the script matters as much as the ask. Let's give listeners a concrete example. Say your boss asks you to take on a new reporting project that'll take about five hours a week. You're already at capacity. Lucas: I'd say something like, 'I can absolutely do that. Let me just check my current commitments. I've got the quarterly review presentation and the client onboarding this month, both of which you said were critical. If I add this reporting project, I'll have about two hours a week for each of those. Is that acceptable, or would you like me to shift something else off my plate?' Luna: That's perfect. You're not saying no. You're presenting a menu. The boss gets to choose which item to remove. Most of the time, they'll say, 'Okay, let's put the reporting on hold until next quarter.' Lucas: And if they say, 'No, I need all of it,' then you have a different conversation. But at least you've surfaced the trade-off explicitly. The worst case is you end up doing everything, but now your boss knows you're overloaded. That awareness often leads to adjustments down the line. Luna: That's a good point. Even a 'no' that doesn't stick can be valuable because it documents the constraint. Six weeks later, when something slips, your boss remembers you flagged it. Lucas: Exactly. And look — honestly, if today's conversation was worth a coffee to you, there's a link in the show notes. Buy me a coffee dot com slash fexingo. It's a small way to keep the show ad-free and independent. But no pressure — we're glad you're here. Luna: Yeah, it really does help. Even a few bucks goes toward covering hosting costs and our research time. So if you've gotten value from any of these episodes, consider it. Lucas: Alright, back to the 'no' question. One more tactic I want to mention — the 'not now, not never' approach. You can say, 'I can't take this on in July, but if we revisit in September after the quarterly close, I'd love to own it.' That turns a no into a future yes, which most bosses find easier to accept. Luna: That's especially useful if the project is genuinely interesting but poorly timed. You're signaling ambition without overcommitting. I've used that myself — 'I'd love to lead that initiative in Q4, but right now I'm deep in the audit. Can we circle back in October?' Lucas: Right. And the beauty of that is, by October, the project might have changed or even been canceled. You dodged a bullet without ever actually saying no. That's the art of it. Luna: Let's talk about one more scenario: what if your boss is the type who piles on work in the moment, in hallway conversations or at the end of a meeting? You can't exactly pull out the 50 percent rule then. Lucas: That's where a follow-up email is your friend. You say, 'Hey, just to confirm, I heard you say you'd like me to lead the vendor review. I want to make sure that's the top priority. I currently have the budget analysis and the team training on my plate. Which of those should I pause to make room?' You're giving them a chance to reflect and adjust after the fact. Luna: So you're not refusing in the moment. You're buying time and then framing it as a prioritization question. That's a really practical takeaway. Lucas: One last thing — and this is counterintuitive. Sometimes the best way to get your boss to say no is to say yes with enthusiasm, and then underpromise on delivery. If you say 'I can do that, but it'll take three weeks instead of one,' you're effectively forcing a prioritization choice. The boss either accepts the timeline or pulls the project. Luna: That's risky though. If you do that too often, you get a reputation for being slow. Lucas: Agreed. Use it sparingly, and only when you genuinely know the work will take that long. But it's a legitimate tool in the toolkit. The broader point is: asking your boss to say no is a career skill, not a sign of weakness. It shows you understand strategy, capacity, and delivery. Managers who can do it themselves are the ones who get promoted. Luna: Well said. So to recap: use the 50 percent rule, tie your capacity to shared priorities, document trade-offs, and never make it about laziness. Make it about excellence. Lucas: That's the whole episode. Go try it in your next one-on-one and let us know how it goes. We'll be back tomorrow with another question.