Before you say yes to another priority

A new request arrives while your team is already carrying a full workload. It matters. The person asking needs an answer. Saying yes feels like the helpful response, especially when you want to be seen as dependable.

But before you commit, pause long enough to look at what that yes will require. A request can be worthwhile and still need a different deadline, a smaller scope or a change to something already promised.

The conversation is easier when you make those choices visible before work begins. These three questions can help.

What will move if we take this on?

Start with the commitments already in place. Which deadline, deliverable or service level would be affected by the new request?

Avoid stopping at “we are busy.” That describes the pressure without giving anyone a decision to make. Name the work and the consequence instead.

For example, you might say: “We can prepare the additional analysis for Thursday. That would move the process review to next week. Is that the tradeoff you want us to make?”

Some deadlines and safeguards cannot move. Identify those first, then discuss the choices you can actually make.

If the answer is that everything must stay on track, ask what can change in scope or resourcing. An additional priority needs a workable place in the plan.

What capacity does the work actually need?

Look beyond the number of people available. The constraint may be a specialist who is already committed, a review that only one person can complete or information another team has not yet provided.

Ask the people who will do the work what the request involves. Include preparation, coordination and review, not just the visible deliverable. Check whether a smaller first version would meet the immediate need.

A useful question is: “What is the smallest useful outcome we can deliver by that date, with the people and information available?”

Be careful about silently filling the gap yourself. If the plan depends on your evenings, or on someone else absorbing extra work without a conversation, make that assumption visible. Decide whether it is a limited exception or a sign that the commitment needs to change.

Who can approve the tradeoff?

You may be able to organize the work without having authority to change the promises attached to it. A colleague can request an urgent analysis, for example, while a different leader is accountable for the deadline it would displace.

Identify who needs to agree before the team receives conflicting instructions. Bring that person a clear choice: the requested outcome, the existing commitment affected and the adjustment you propose.

Then confirm the decision with the people doing and depending on the work. A short written recap can be enough: what takes priority, what changes, who agreed and when the arrangement will be reviewed. Avoid leaving everyone to infer the new order from the latest conversation.

Practise a more considered yes

Before your next commitment, try this sentence:

“I can see why this matters. Before we confirm the date, let's agree what moves, what capacity we need and who can approve the change.”

You can be responsive without giving an immediate promise. Sometimes a brief pause is what allows you to give an answer the team can rely on.

Notice what makes that pause uncomfortable. Is it concern about disappointing someone, being seen as difficult or losing an opportunity? Naming the pressure can help you choose your response rather than automatically accepting the work.

Take one request from this week's workload and use the three questions before confirming it. The aim is a commitment that everyone understands and has a realistic chance of delivering.