How to Say No to More Work When Your Team Is Already Full
When your team is full, explain what the new request would displace. Check the remaining work and available capacity, then offer options: change a deadline, reduce the scope, move another commitment, or assign suitable help. Ask the person with authority to approve the tradeoff before you promise delivery.
You may need to say no to the proposed deadline even when the work matters. A useful response gives the requester enough information to choose what happens next. “We’re too busy” leaves them guessing about the constraint. “We need to move this report or change the new deadline” gives them a decision to make.
Check Capacity Before You Answer
Start with the work that remains in the period the request concerns. A full calendar tells you little about whether the right people have time for a particular task. Check estimates with those who will do the work and include review time, dependencies, and handoffs.
Distinguish available project hours from total paid hours. Meetings, routine support, leave, and existing responsibilities use time. Do not count the same hours as available capacity and as time reserved for those duties.
Record uncertainty in the estimate. If a task could take between eight and sixteen hours, explain what drives that range. A schedule that fits only at the lowest estimate needs a plan for the extra work. You also need the right skills at the right time; spare hours elsewhere on the team may not resolve a specialist bottleneck.
A Worked Example: Maya’s Overloaded Team
This fictional case develops the overloaded-team example on the homepage. Maya’s team has 64 hours available for project work this week after routine duties and known absences. Existing commitments require an estimated 64 hours. A director asks for a new analysis that will take another 20 hours, due Friday.
Accepting it without changing anything would create 84 hours of demand against 64 hours available. Maya needs to explain the 20-hour shortfall before the director treats Friday delivery as agreed.
She checks the work with her team. A lower-priority report accounts for 24 of the committed hours and might move to the following week. Postponing it would leave 40 hours of existing work. Adding the new analysis would bring this week’s estimated demand to 60 hours.
The arithmetic identifies an option. Maya still needs to check who uses the report, whether the delay affects their work, and whether next week has room for those 24 hours. The four hours left this week provide limited headroom if an estimate changes; they do not guarantee delivery.
Compare the Options Before Recommending One
Maya can take several options to the director. Each changes a different part of the commitment:
Accept the full request by Friday: This leaves a 20-hour shortfall unless someone approves and confirms additional capacity. Maya should not conceal that gap by assuming the team will absorb it.
Delay the new analysis: This protects the current commitments, but Maya needs to ask which decision the analysis supports and what a later delivery would cost.
Reduce the scope: The requester might accept a smaller deliverable that answers the immediate question. Because the current workload already fills the week, even a smaller version requires some work to move or confirmed extra help.
Move the 24-hour report: This creates enough estimated capacity for the full analysis this week. It depends on the report owner accepting the delay, next week’s capacity, and approval of the revised priorities.
Assign suitable help: Another person might take part of the work, but Maya needs to confirm availability, skills, and the time her team would spend briefing and reviewing it.
Maya recommends moving the report, subject to the checks. She identifies who must approve the change and gives the director a fallback if those checks fail. She does not count an unanswered request for help as extra capacity.
Use Wording That Makes the Choice Clear
Maya can respond without promising more than her team can deliver:
“We have 64 project hours available this week and 64 already committed. The new analysis adds about 20 hours. I recommend moving the 24-hour report, which would bring this week’s total to 60 hours. I need to confirm that its users can accept the delay and that next week has capacity. If those checks hold, can you approve the revised priorities?”
If the director asks for an immediate yes or no, she can state the limit:
“I cannot commit to both the current workload and the full analysis by Friday with the capacity we have. We need to change a commitment or confirm additional help before I can give you a credible delivery plan.”
If the response is “Everything is a priority,” Maya can ask for the consequence that should guide the choice:
“Which missed deadline would have the greatest consequence? If we keep both dates, who can authorise the extra capacity or a smaller deliverable? I can bring you the options, but the current plan is 20 hours over capacity.”
Keep the discussion about the work and the decision. If frustration starts driving the exchange, use the preparation and sample wording in How to Have a Difficult Conversation at Work Without Losing the Point.
Check the Week You Are Moving Work Into
Deferring work can make this week look manageable while creating the same shortfall next week. Before Maya recommends the new date, she checks next week’s commitments with her team. She also asks the report’s users what they can do with a later version and whether they need a limited update in the meantime.
If next week is full, she must revise the option. She might negotiate a different date or narrower report, or ask the director to stop lower-value work. If the report owner cannot accept a delay, she returns to the other options for the new analysis.
The same discipline applies when you are the individual receiving extra work. You can say, “I can finish this by Thursday if the dashboard moves to Monday. Please confirm which should take precedence.” Check the effect of that move before presenting it as workable.
Record the Approval and the Review Point
After the director approves a workable option, Maya records the revised dates and tells the affected people. Until then, she describes the arrangement as a proposal. A colleague’s silence does not establish that they accepted a delayed handoff.
For this fictional case, Maya could record:
“Proceed with the new analysis for Friday after the director approves moving the report and its owner confirms the revised date. Maya will confirm next week’s capacity before the team starts. We will check the remaining estimates on Wednesday and raise any new shortfall or dependency problem that day.”
For a review to help, someone needs to compare the work remaining with the time remaining. If an assumption fails, Maya should bring back the changed estimate and options while there is still time to adjust. How to Decide Before Certainty Arrives explains how to build these conditions into a recommendation.
Make the Recommendation Easy to Review
Use the free Decision Brief and completed workplace example to set out the request, evidence, options, and approval you need. You can download it with or without subscribing to emails.
Before sending your recommendation, check that the requester can see what you can deliver, what must change, and who needs to agree. You cannot remove a capacity shortfall by choosing more reassuring words. You can give the person setting priorities a clear basis for deciding which commitment to change.
