Last year, one of my colleagues who was renowned for pleasing people said yes to everything. Every project request, every last-minute meeting, every “quick favour” that landed on her desk. She thought she was being the perfect team player. Instead, she ended up missing a critical deadline on her biggest client project, costing her team a massive contract renewal. The irony? She was too busy with tasks that weren’t even in her job description.

This story isn’t unique. Many of us struggle with saying no at work, fearing we will be seen as uncooperative or lazy. But here’s the truth: strategic boundary-setting isn’t selfish—it’s essential for your career and your team’s success.

When Your Plate Is Already Full

The first time you should say no is when taking on additional work would compromise your existing commitments. This isn’t about being difficult; it’s about being realistic.

One person I know, a manager who was already juggling three major projects when his boss asked him to lead a fourth. Instead of automatically saying yes, he responded: “I’d love to help with this project. Right now I’m focused on the Q4 campaigns that are due next week. Could we discuss which of these projects are the most important, or would it be better to bring someone else onto this new initiative?”

The result? His boss appreciated his honesty and reassigned the project to someone with more bandwidth. The Manager delivered his original campaigns on time and exceeded targets.

How to say it: “I want to make sure I can give this the attention it deserves. With my current workload, I wouldn’t be able to deliver my best work on this until [specific date]. Would that timeline work, or should we explore other options?”

When It’s Not Your Job (And Shouldn’t Be)

The second crucial time to decline is when requests fall outside your role and expertise, especially if accepting them regularly would derail your career growth.

This should’nt happen simply because you are good with people. While flattering, these requests eat into your core time and preventing you from building the technical skills needed for your next promotion. You can learn to redirect these requests: “I appreciate you thinking of me for this, but I think the customer service team would be better equipped to handle this properly. Let me connect you with them.”

How to say it: “This sounds like it would be better handled by someone in [relevant department]. I want to make sure the customer/project gets the expertise it needs. Let me introduce you to [appropriate person].”

When the Request Lacks Clarity or Resources

Finally, say no when you’re being asked to take on work without clear expectations, adequate resources, or realistic timelines. These situations are setup for failure.

If you are asked for instance to “handle the vendor situation” with no context, budget, or timeline. Instead of diving in blindly, ask clarifying questions: “I want to make sure I approach this correctly. Could you help me understand what success looks like here? What’s our budget and timeline, and who else should be involved in this decision?”

Sometimes this conversation reveals that the request wasn’t well thought out. Other times, it provides the clarity needed to succeed.

How to say it: “I want to tackle this effectively. Could we schedule a brief meeting to discuss the scope, timeline, and resources available? I want to make sure I’m setting realistic expectations.”

The Art of the Professional No

Remember, saying no isn’t about being negative—it’s about being strategic. Every yes to one thing is a no to something else. When you protect your time and energy for your most impactful work, you’re not just helping yourself; you’re helping your team focus on what matters most.

The key is in how you frame it. Lead with understanding, offer alternatives when possible, and always explain your reasoning in terms of delivering better results.

---