Why More Work Doesn’t Automatically Mean More People 

For a long time, it was reasonable to assume most challenges could be solved by adding more people. Leaders looked at the volume of work in front of them, compared it against the resources they had available, and made staffing decisions accordingly. 

Lately, however, these conversations are changing. 

Organizations are still facing growth. They’re still trying to move faster. They’re still navigating major changes in technology, operations, and customer expectations. But more often than not, they aren’t coming to the table asking for a specific number of resources. Instead, they’re coming with a business objective in mind: 

• They’re trying to support a transformation.  
• They’re trying to increase productivity.  
• They’re trying to adapt to a new technology.  
• They’re trying to scale a function without disrupting the rest of the organization. 

In other words, they’re no longer approaching the question as solely a workforce discussion. 

The Conversations Sound Different Now 

One observation I’ve made over the last few years is that leaders are becoming much more focused on outcomes than they are on headcount. 

Historically, many workforce conversations started with organizational structure—a leader would identify a growing workload and determine how many people were needed to support it. Today, the conversations are more centered around objectives. Leaders want to understand how their teams can support the broader goals of the organization. They’re increasingly asking how a function contributes to business outcomes instead of simply evaluating whether the team is large enough to accomplish today’s work. 

A big part of that shift comes from visibility. 

Organizations have access to more operational information than they did five years ago. Leaders can see where work stalls. They can see which teams are overloaded. They can identify bottlenecks, delays, duplicate effort, and inconsistent processes. That visibility creates a different type of conversation because it gives leaders more ways to think about improving performance. 

Instead of automatically saying, “We need five more people,” many leaders are asking, “What is preventing this team from producing more with the resources it already has?”  

It’s a more complicated question, but it’s also usually a more useful one. Because while sometimes the answer is additional capacity, sometimes it isn’t. 

Sometimes the Work Isn’t the Problem 

One thing that’s become clear through customer conversations is that organizations usually know where their pain points are. They know the report that takes too long, the process everyone complains about, and the workflows that have become overly manual. The challenge is that they don’t have the bandwidth to step back and address them. 

I think about a retail organization we worked with that had someone spending roughly 15 hours every week pulling data from multiple systems, validating it, and preparing reports for the broader team. Nobody thought it was an efficient process, but it had become standard procedure. The prospect of changing the current state seemed so far away and too challenging, that it was simply accepted.  

That process was eventually automated because the team sat down, created the space to solution a different way, and stayed focused on the results that aligned with the organizations efforts to find more efficient ways of working. Eventually, that process was automated. The organization recovered those hours, gained access to fresher information, and improved visibility into performance. What looked like a capacity constraint from a distance turned out to be a workflow problem. And the work was only overwhelming because too much effort was being spent on manual tasks. 

I’ve seen similar patterns with disconnected systems, unclear ownership, manual handoffs, and processes that haven’t been revisited in years. Hiring more people can help absorb that friction, but if the underlying issues remain, organizations often end up with more people working around the same problems. 

Every Organization Has “That One Person” 

Almost every organization has a person everyone depends on. That could be the employee who’s been there for 20 or 30 years, or the person who understands every process like the back of their hand, or the go-to individual everyone calls when something breaks. 

Whenever I hear leaders say, “If this person leaves, we’re in trouble,” that statement usually reveals something important about their process and how work is organized. 

Great organizations need great people. There’s no replacing experience, judgment, or institutional knowledge. But when too much organizational knowledge lives inside one person’s head, everything is harder—growth, onboarding, handoffs, knowledge transfer, all of it.  

At that point, adding more people doesn’t necessarily create more resilience. 

Over time, I’ve become increasingly convinced that scalability comes from documentation, governance, and shared ownership more than it comes from organizational size. 

That’s not always the first thing leaders want to hear. 

Granted, it’s usually easier to discuss staffing plans than process maturity, but if an organization is built around a handful of heroic individuals, growth is going to eventually expose those weaknesses. 

Being Close to the Work Changes What You See 

One thing I’ve learned is that the most valuable teams are close enough to the work to understand how the organization truly operates. 

When you’re embedded in the day-to-day, you start noticing things that don’t show up on an org chart or a project plan. You see where work slows down, and the processes and reporting tasks everyone works around without question. You see the handoffs that should create clarity, but instead, slowly break down and create friction because the appropriate gates are missing or lacking integrity 

I think that’s why some of the best improvements come from people who are close to the work, but intentionally remove themselves to ask questions like, “Why are we doing it this way?” or “Does it make sense to continue operating this way?” I’ve also seen organizations benefit from ideas borrowed from completely different industries because many operational challenges aren’t nearly as unique as we think they are.  

The other thing proximity creates is clarity. Over time, strong teams execute faster and easier when expectations, ownership, and communication are clear.  

Without that structure, organizations tend to rely on individual heroics to keep things moving. With it, they grow, onboard, and adapt without constantly rebuilding the process. 

The goal should be to understand the environment well enough to leave the work operating better than you found it.  

A Better Place to Start 

I’m not making the argument that organizations should stop hiring. There are plenty of situations where additional people are exactly what’s needed. 

What I am suggesting is that leaders spend a little more time understanding the work itself before deciding how to solve the challenge in front of them. 

• What’s creating delays? 
• What’s consuming the team’s time? 
• Where does work break down? 
• How much of the organization depends on a handful of people? 
• What would happen if those people left tomorrow? 
• How much effort is being spent managing the process instead of moving the business forward?  

I’ve found those questions usually lead to more productive conversations than staffing discussions alone—because sometimes the answer is more people, but sometimes it could also be better documentation, or a clearer operating model, or removing work that shouldn’t exist anymore. It would be irresponsible to not mention that technology like AI, should have a seat at these discussions. But just like how adding more bodies onto a weak operating model will only restrict an organization’s ability to transform, investing in AI without starting the conversations here will also shackle the opportunity.  

Much of my perspective comes from conversations with leaders who are trying to deliver more while balancing growth, transformation, and day-to-day execution. If these challenges sound familiar, feel free to connect with me. I’m always interested in hearing how different organizations are approaching them and what lessons they’re learning along the way.