Latest / Office Hours with Fexingo: Daily Career Q&A, Workplace Questions, and Professional Advice / How to Decline a Project Without Looking Lazy
Transcript
- Lucas: So the question that came in for this episode is deceptively simple on the surface: 'How do I say no to a new project without looking like I am lazy or not a team player?' And I think that question lands differently in mid-2026 than it might have even two or three years ago, because we are seeing a lot of lean teams where everyone is already running at capacity. Luna: Right, the era of 'doing more with less' is still very much the reality for a lot of listeners. And the fear is real — if I say no, will I be the first one cut when the next reorg comes? Lucas: Exactly. And the instinct for a lot of people, especially high performers, is to just say yes and figure it out later. But there is actually some interesting research on this. A study in the Journal of Applied Psychology a few years back looked at what they call the 'helping penalty' — the idea that employees who say yes to every request actually end up with lower performance ratings because they spread themselves so thin that their core work suffers. Luna: That is counterintuitive, but it makes total sense. You end up doing ten things at 70 percent instead of five things at 95 percent. Lucas: Right. So the real skill here is not learning to say no — it is learning to say no to the project while saying yes to the person, and to the broader mission. And I want to anchor this in a specific example. Let us say there is a marketing coordinator named Priya. She already has three campaigns running, each with hard deadlines in the next four weeks. Her manager comes to her on a Tuesday and says, 'Hey, we just got a last-minute opportunity to sponsor a major industry event in three weeks. I need someone to lead the booth design, the collateral, and the lead-capture process. You are my best person for this.' What does Priya do? Luna: My first instinct is panic, honestly. Because she wants to be the person who steps up, but she also knows that adding a fourth project means something is going to slip. Lucas: Exactly. And the key move here is to separate the enthusiasm from the capacity. So the first sentence out of her mouth should be a genuine yes to the opportunity itself. Something like: 'Thank you for thinking of me for this — it sounds like a great opportunity and I can see why it matters for the team.' That alone signals she is not lazy and she is not disengaged. Luna: So you disarm the fear immediately. You are not rejecting the work, you are rejecting the timing. Lucas: Right. Then she has to name her current reality concretely. She says something like: 'Right now I am at capacity with the Q3 campaigns. I have the Smith launch, the Johnson renewal, and the Rivera webinar all hitting deliverables in the next three weeks. If I take this on, I am worried something will slip. Can we look at what I should deprioritize to make room?' Luna: I love that framing because it turns it from a 'no' into a prioritization conversation. Now the manager has to make a choice about what matters most, rather than just dumping a task. Lucas: Exactly. And the research backs this up — managers actually respect the employee who can articulate trade-offs more than the one who just says yes and then misses deadlines. There is a concept called 'strategic rejection' where you show you understand the business priorities by being willing to kill something else to make room for the new thing. Luna: But what if the manager says, 'Just figure it out, I need you to do both'? That happens a lot, especially in smaller teams. Lucas: It does. And at that point, you need to escalate the specificity. You say something like: 'I want to be transparent with you. If I take this on, I estimate the Smith launch will be delayed by a week and the Johnson renewal collateral will not be ready for the client meeting. I want to make sure you are comfortable with those trade-offs.' Now you are not saying no — you are giving the manager a clear picture of the cost. Luna: That is powerful because it makes the manager own the decision. If they still say yes to the new project, they are explicitly accepting the delay on Smith. And you have covered yourself. Lucas: Right. And a lot of times, when you lay out the trade-offs that clearly, the manager will back off or find another solution. They may not have realized the full picture. One thing I would add — do not use the word 'stress' or 'burnout' in the conversation. Frame it around business impact. 'My concern is that quality will drop on the existing projects' lands much better than 'I am overwhelmed.' Luna: That is a really good distinction. The moment you make it personal, you sound like you cannot handle the workload. But when you frame it around the work itself, you sound like a professional who cares about outcomes. Lucas: Exactly. And I want to add one more layer — the concept of the 'yes threshold.' Every person has a number of major projects they can handle at once before the marginal quality drops off a cliff. For Priya, it might be three. For a senior engineer, it might be two. Knowing your own threshold and being able to articulate it is a career superpower. Luna: So how does someone figure out their own threshold? Because I think a lot of people do not know until they are already underwater. Lucas: Great question. One practical method is to keep a simple time log for two weeks — just note how many hours each project actually takes, and then note your energy levels. If you find that after the third project you are making more errors or taking longer, that is your threshold. Or you can look back at past quarters and ask yourself: when was I producing my best work? How many projects was I juggling then? Luna: That is actionable. And it gives you data to bring to the conversation, not just a feeling. Lucas: Right. And here is another angle — sometimes the best way to decline a project is to suggest an alternative. 'I cannot take this on, but I know Jenna on the events team has capacity and she has done booth design before. Could I help her get up to speed in a quick handoff?' That shows you are still thinking about the team's success, not just your own workload. Luna: That is a great move. It turns you into a solution-oriented person, not a problem. Lucas: Exactly. And if the manager still insists, you have done everything you can. At that point, you say yes, but you document the trade-off in an email — 'Per our conversation, I am prioritizing the event sponsorship over the Smith launch, which will now be delayed. I will keep you updated.' That covers you if anyone asks why Smith slipped. Luna: So the whole approach is really about reframing the decline from a personal no to a strategic yes. I think a lot of listeners are going to find that useful, because the fear of looking lazy is so deeply ingrained. Lucas: It really is. And I think it ties into something we talk about a lot on this show — which is that a lot of career advice focuses on how to get more done, but very little focuses on how to decide what not to do. And that is actually a higher-leverage skill. Luna: Absolutely. And if listeners have gotten something out of episodes like this, or if we have helped you think through a career move or a difficult conversation, it genuinely makes a difference when people support the show. Even a couple of dollars a month helps keep these episodes coming — you can find us at buy me a coffee dot com slash fexingo. Lucas: Yeah, it really does. And it keeps the show ad-free, which is something we both care about. So thank you to anyone who has done that. Luna: Alright, back to the topic. One thing I want to ask — what about the reverse situation? What if you are the manager, and an employee comes to you and says they are at capacity? How should you respond? Lucas: That is a great follow-up. The worst thing a manager can do is penalize the employee for being honest. The best response is to thank them for the transparency, and then work with them on the prioritization. A good manager will say, 'Okay, let us look at your plate together and see what can move or what can be dropped.' And if nothing can move, then you respect their capacity and find someone else. Luna: So it is about building a culture where 'I am at capacity' is a respected answer, not a mark against someone. Lucas: Exactly. And that culture starts with the manager modeling it themselves. If the manager never says no, the team will feel like they cannot either. So it is a leadership responsibility as much as an individual one. Luna: That is a good note to end on. Lucas, as always, great conversation. Lucas: Thanks, Luna. And to our listeners — the next time someone asks you to take on something new, remember: the best professionals know their limits, and they communicate them clearly. See you next time.