How to Ask for More Resources at Work

Managers often enter an executive conversation with a direct request: “I need more people.”

The need may be real. The team may be overloaded, deadlines may be at risk and employees may already be working beyond a sustainable capacity.

But “I need resources” focuses on the manager’s constraint rather than the business decision senior leaders need to make.

A stronger resource request begins with the outcome, explains the current capacity and presents realistic choices. It helps leaders understand what can be delivered, what each option requires and which tradeoffs they are accepting.

The objective is not to hide the need for additional resources. It is to make the business case clear enough for leaders to evaluate it.

As companies reset for a new chapter in 2021, there has been a lot of reflecting on how companies and teams made it through the uncertainty and disruption of 2020. One way was to reallocate resources or reduce teams. It drove efficiencies quickly, and it saved money. At the time, it was a difficult, but smart, step.

And now, managers tell us that what they saw as a temporary situation seems to be the new and expected normal on their teams. They’re stuck in the “do more with less” direction, and it’s causing burnout as employees continue to manage their roles and a part of someone else’s. Managers feel an urgency to reset and pull their teams out of the overload. And they’re headed into executive-level conversations with this message: “If we want to complete our project on time, I need five resources to do X”, “If we add 10 employees back to the team, we can do X.” It follows our message format, but it falls short of approval by most leaders.

Here’s why.

It’s the most common request leaders hear in companies. “I need more people.” It was the most common request before 2020 took place. So, you can imagine what it must be like now as more teams are short-staffed. If every manager added a headcount, the company would be right back to the pre-2020 bottom line. And leaders aren’t interested in backing up. They believe a lot was learned from 2020 and efficiencies – doing more with less – resonates as a positive outcome.

But the managers’ predicament is not an excuse; it’s a real challenge and a real threat to the retention of talent. Managers need to have these conversations, but they need to shift the storyline from “I can’t do it without people” to “we have choices to make about how we accomplish this\”. It means shifting the storyline to focus on a business decision and outcome rather than the challenges they’re feeling to deliver against it.

The starting point is messaging that focuses on choices and actions that lead to outcomes. Take people and headcount out of the equation. It seems like odd guidance, but it makes a big difference. When managers look at initiatives, they think from the desired outcome backward and map out how to get the work completed. They map a single path to completion, and they quickly see the need for resources to complete tasks.

When leaders look at initiatives, they consider multiple paths to lead to the outcome. They rarely see it as a single path. So, when a manager comes to them and says: “If we want to deliver X on time, we need five additional people on the team.”, leaders ask questions like: “What other options did you consider?” And when managers don’t have that context, leaders get frustrated that multiple options weren’t considered.

The best way to lead these conversations is to learn to think more from the leaders’ perspective. If you have a project in front of you that doesn’t seem doable without adding resources, pull back and think about all the options/paths you have to get there.

Assume you’re down four people and have been since last year. You have been given a tight timetable to deliver product Z, and it’s the same timetable you delivered against with those four people you no longer have. You know you can’t do it without the full team in place. That’s fair; it’s how you delivered products prior to 2020. But before you head down the single path with a message that says, “I need resources,” think a little broader.

You could:

• Partner with another team by prioritizing product Z over a product from another team on a similar timetable.
• Outsource some of the product steps to avoid adding FTEs and instead add specific help to specific steps.
• Push out the delivery date based on a new timeline that seems feasible to the team you have in place.

When a leader is presented with options like this, they look at the situation differently. They hear 1) change the approach 2) double efforts on critical steps or 3) change the timetable. They see that you’re thinking through options to get to an outcome instead of bringing challenges you have with a single path. It aligns more with the types of decisions they’re used to making, and it’s the most effective way to help them consider compromise.

The second point for the communicator to consider is setting context. In our workshops, we call it “Framing the Situation,” and we provide a methodology to help a communicator align a leader to the topic of choices that have been made to date. Instead of jumping to “How are we going to do this,” a good communicator will reset what’s already happened to date. This helps a leader see that they have already made some of the decisions that have led to the current topic.

A manager who is down four resources might begin a storyline like this:

“Last year, with uncertainty in front of us, we reduced the team by four people. And we asked the remaining six to work tirelessly to get product Y into the market in six months. They did that, and we have seen the product perform well by delivering expected revenue and good customer reviews. So, it was a success last year out of working differently on the team.

“But it came with compromise. In order to get product Y to market on the timetable, we skipped two critical points. We reduced testing, and we eliminated some of our protocols for integration. You may remember this conversation and debate last May. We made the decision to skip steps at the time, because we felt product Y so closely aligned to product X that launched the previous year. We seemed aligned with customer response and felt the break with protocols would have limited risks. In this one case, we were right.

“This year, product Z doesn’t align in the same way and following the modified steps would create bigger compromise and increased risks. As a product team, you have asked us to reset the “best practices” and protocols of development that you put in place three years ago. And when we do that, it will create some different choices to consider for product Z.”

This context aligns the leader to the topic and the broader reset they’ve put in place across the organization. They have agreed to the best practices and protocols for product Z before hearing the choices they need to make. And as you probably noticed, it calls out steps they value and a process that they put into place. So, it’s easier for the leader to consider options when they’re trying to avoid product compromise and risks.

The idea of adding back resources hasn’t come up. But it may be brought up by the leader. Because as they think through the options above, they may ask: “What if we didn’t change the approach or the timetable and instead of relying on contract resources, we added people back to your team?” When it’s set in the broader picture, it now looks like the least disruptive solution rather than the only way you can figure out how to solve a challenge.

Learning to lead conversations from a leader’s perspective is something we’ve been helping managers do for more than three decades. If you’re preparing for a tough conversation, we can help you develop the storyline that leads to the desired outcome.

Why “I Need More People” Often Falls Short

Additional headcount is one of many requests competing for limited organizational resources.

A senior leader may be evaluating hiring needs across multiple departments while also considering technology investments, customer priorities and financial commitments. If every manager describes only the pressure on their own team, the executive must determine which request has the greatest business value.

“I need more people” leaves several important questions unanswered:

• What outcome is at risk?
• What work is creating the need?
• Is the constraint temporary or ongoing?
• What alternatives have been considered?
• What will additional resources make possible?
• What happens if the request is not approved?
• Why is this the best use of organizational capacity?
• What decision is needed now?

The manager should be ready to answer these questions before making the request.

Begin with the Business Outcome

A strong resource conversation begins with what the organization is trying to accomplish.

Instead of saying:

We need three additional employees because the team is overwhelmed.

A manager might begin:

To complete the customer implementation by October without delaying our other committed launches, we need to resolve a capacity gap across testing and integration.

The second version gives the conversation a business frame. It identifies the outcome, timing and competing commitment.

This is not about avoiding the team’s workload. It is about helping leaders understand why that workload matters to the organization.

Relevant outcomes might include:

• Delivering a product on schedule
• Protecting customer commitments
• Reducing operational risk
• Meeting regulatory requirements
• Maintaining service quality
• Supporting revenue growth
• Completing an integration
• Preventing avoidable employee turnover
• Improving an inefficient process

Once the outcome is clear, the resource discussion has a purpose.

Explain the Current Capacity

Executives need an objective view of the gap between what has been requested and what the existing team can reasonably deliver.

That explanation should include:

• Current staffing or budget
• Existing commitments
• Work required for the new priority
• Critical skill gaps
• Relevant deadlines
• Known dependencies
• Work that has already been deferred
• Temporary solutions currently in use
• Risks created by continued overload

Avoid relying only on statements such as “everyone is busy.” Leaders need enough detail to understand the capacity constraint without being taken through every task.

Useful evidence might include workload trends, vacancy duration, service levels, project delays, overtime or the number of critical responsibilities assigned to the same people.

The evidence should clarify the decision rather than overwhelm the listener.

Present Options Rather Than One Demand

Senior leaders often consider several paths to the same business outcome. A manager who presents only one solution may appear to have stopped thinking once the staffing gap became visible.

Depending on the situation, options may include:

• Add permanent employees
• Use contractors for specialized work
• Borrow capacity from another team
• Reduce the project scope
• Change the delivery sequence
• Extend the timeline
• Delay another initiative
• Automate part of the process
• Stop lower-priority work
• Accept a defined level of risk

Not every option will be equally attractive. The manager’s responsibility is to show that the realistic alternatives were evaluated.

A simple comparison can help:

The conversation shifts from “approve my request” to “choose the most appropriate business tradeoff.”

Make the Tradeoffs Visible

Every option has a consequence.

If the organization decides not to add staff, it may need to accept a later date, reduced scope or greater operational risk. If it approves permanent headcount, it accepts an ongoing cost. If it uses contractors, it may gain speed without building long-term internal capability.

Managers should explain these tradeoffs directly.

This is especially important when the current team has been compensating for a capacity gap. Short-term effort can make an unsustainable model appear successful.

A manager should distinguish between:

• What the team can deliver once
• What it can deliver repeatedly
• What requires extended hours
• What work is being deferred
• What controls or quality steps are being compressed
• What risk is accumulating

Protecting employees from chronic overload is not separate from the business case. Burnout, errors and turnover can become business risks.

Provide a Clear Recommendation

Presenting options does not mean asking senior leaders to develop the solution for you.

Managers should recommend the path they believe creates the strongest balance of outcome, cost and risk.

A useful recommendation includes:

1. The preferred option
2. Why it is the strongest choice
3. The cost or resources required
4. The tradeoff being accepted
5. The decision needed
6. The timing of that decision

For example:

We evaluated adding permanent staff, using contract support and moving the launch. I recommend using two contractors for six months. That gives us the specialized testing capacity we need without creating an immediate long-term headcount commitment. It adds $120,000 to the project cost but protects the October customer launch. We need approval by May 15 to begin onboarding on time.

The recommendation is specific, and the leader understands the choice.

Frame the Situation Before Making the Request

Sally refers to this step as Framing the Situation.

Framing gives the listener the context needed to understand why the conversation is happening. It connects the current resource request to earlier decisions, changing conditions and agreed business priorities.

A manager might explain:

• What the organization originally planned
• Which assumptions have changed
• What the team has accomplished
• Which temporary adjustments were made
• What those adjustments required
• Why the next phase creates a different risk
• Which decision now needs to be reconsidered

This prevents the resource request from sounding like an isolated complaint.

It may also remind leaders that the current constraint resulted from choices the organization made for valid reasons. The conversation is not about assigning blame. It is about deciding whether those choices still fit the current situation.

Prepare for Executive Questions

Leaders may challenge the assumptions behind a resource request. That does not necessarily mean the request has failed.

Questions help executives test whether the manager understands the full business picture.

Prepare for questions such as:

• What work can stop?
• Can the timeline move?
• Can another team help?
• Is this a permanent need?
• Why can’t technology solve it?
• What happens if we do nothing?
• Can the team absorb this temporarily?
• How did you estimate the required resources?
• Which option do you recommend?
• When will the investment produce value?
• What would change your recommendation?

Answer the central question first. Then add the supporting detail the leader needs.

If information is unavailable, acknowledge it and explain how it will be obtained. Guessing weakens the credibility of the entire request.

What Not to Do in a Resource Request

Several communication choices can undermine a legitimate business need:

• Opening with employee frustration rather than the business outcome
• Presenting headcount as the only possible solution
• Using “we are busy” as the primary evidence
• Overloading the conversation with task-level detail
• Hiding the consequences of an alternative
• Threatening widespread resignation without evidence
• Asking for resources without defining the work
• Presenting several choices without a recommendation
• Treating questions as resistance
• Promising the team can continue an unsustainable pace
• Minimizing quality, customer or employee risks
• Blaming senior leaders for earlier decisions

The message should be direct without becoming adversarial.

Example of a Strong Resource Request

Our October launch requires six weeks of testing and integration. The current team can complete that work, but doing so would delay the two customer upgrades already committed for the same period.

We evaluated four options: reduce the launch scope, move the date, delay the customer upgrades or add temporary capacity.

I recommend adding two contract specialists for six months. This protects the launch and customer commitments without creating a permanent staffing decision before next year’s planning cycle.

The additional cost is $120,000. If we do not approve that option, my second recommendation is to move the launch by eight weeks. I would not recommend compressing testing because the quality risk is significantly higher for this product.

We need a decision by May 15 to protect the onboarding schedule.

This structure gives leaders context, choices, tradeoffs and a recommendation.

So, whether you’d like to schedule a coaching session to focus on a specific conversation or book a group workshop to learn the fundamentals, we hope you’ll call us when you need us.