Know when and how to say no.

Saying no is a skill, and most people are bad at it. Done badly it makes you look difficult. Done well it protects the project and nobody resents you for it.

Example of Saying No Constructively

Consider the scenario where a team member says, “This is just 5 minutes of work, but it’s not in my scope, so I’m not doing it.” This approach can appear unhelpful or petty. A better response might be, “I’ve taken care of it this time, but let’s clarify whose responsibility this should be going forward to ensure we’re all clear on our roles.”

The Importance of Saying No

Project demands arrive in an overflowing bucket. No is how you stop it tipping over: it protects your workload, the goal, and the scope.

Setting Clear Boundaries

Before effectively saying no, ensure you have clearly defined roles and responsibilities in your project and team. This clarity helps everyone understand what falls within their purview and what does not. That’s what makes a no defensible. Ensure you set up a framework for roles and responsibilities at the onset of your project. Leverage a Project Initiation Document or similar format to align on this before starting the work.

When to Say No

Out of Scope: If a request falls outside the agreed-upon project scope, it’s acceptable to decline.
Out of Role: If the request falls under the role of another team member, such as writing Technical Documentation as a Project Manager.
Resource Constraints: When there’s a lack of resources—time, team members, budget—it may be necessary to refuse additional tasks to maintain project quality.
Prioritization Conflicts: If a new request conflicts with higher-priority tasks, say no to protect the work that’s already been prioritised.

How to Say No

It’s all in the delivery. Here’s how to do it constructively:

Be Direct but Polite: Clearly explain why you are saying no. Ensure the reasoning is objective and relates to project priorities or resources.
Offer Alternatives: Suggest an alternative solution or compromise. For example, “I can’t do this now, but I can schedule it for next week.”, or “I can’t help you with this, but this other person might be able to.”
Educate: Use this as an opportunity to clarify role responsibilities or project scope. It helps prevent similar issues in the future.
Follow-Up: If appropriate, check back to see if a suitable resolution was found. It shows that, while you said no, you still care about the issue.

Say no early, say why, and offer something instead. Do that and people stop hearing a refusal and start hearing a plan.