Before Adding More People, Solve the Real Problem

"We need more people."

It's one of the most common responses when a project starts slipping behind schedule.

Deadlines are approaching, stakeholders are asking for updates, and the pressure is rising. The natural assumption is simple: if the current team can't finish the work, adding more people should increase capacity and solve the problem.

Sometimes that's true.

But surprisingly often, adding people doesn't solve the problem—it amplifies it.

The reason is simple: people don't just produce work. They also communicate, coordinate, learn, review, ask questions, make decisions, and depend on one another. If the real constraint isn't a lack of capacity, increasing headcount may simply increase the amount of coordination around the same bottleneck.

As producers, our responsibility isn't to ask, "How many more people do we need?" It's to ask, "What is actually preventing the current team from succeeding?"

The Illusion of More Capacity

Imagine a production team waiting three days for creative approvals.

Adding three more artists won't make approvals happen faster.

Or imagine engineers waiting on design decisions before they can implement a feature.

Hiring another engineer won't remove that dependency.

Perhaps lighting is blocked because assets haven't been finalized. Maybe QA is overwhelmed because requirements keep changing. Perhaps everyone is working hard, but priorities shift every week, forcing constant rework.

In each of these situations, the bottleneck isn't people.

It's the system.

When we increase headcount without addressing the underlying constraint, we simply send more work into the same traffic jam.

Brooks's Law: Often Quoted, Frequently Misunderstood

One of the best-known ideas in software engineering comes from Fred Brooks in The Mythical Man-Month:

"Adding manpower to a late software project makes it later."

Known as Brooks's Law, this statement has been quoted for decades. However, it is often treated as an absolute rule—which was never Brooks's intention.

Brooks explained that new team members don't become productive immediately. Existing team members must spend time onboarding them, sharing knowledge, reviewing work, answering questions, and integrating them into established workflows. During that transition, experienced contributors temporarily produce less while helping others become productive.

Brooks also emphasized that many tasks simply cannot be divided indefinitely. Some work requires sequential decisions, shared context, or close collaboration, meaning that adding more people cannot reduce the critical path.

That doesn't mean adding people is always the wrong decision.

When work is well-defined, divisible, and supported by a stable process, additional capacity can absolutely accelerate delivery.

The important question isn't whether Brooks's Law is "true."

The important question is whether your project's bottleneck is actually a shortage of people.

Coordination Is Work

As teams grow, coordination grows with them.

Every additional person introduces new communication, new dependencies, new reviews, and new handoffs. Researchers have long shown that larger teams face increasing coordination costs because people spend more time synchronizing their work instead of producing it.

This doesn't mean large teams are ineffective. Some of the world's biggest games, films, and software products are built by hundreds of talented people.

The difference is that successful large teams invest heavily in structure.

They divide work into clear ownership areas, establish reliable communication channels, document decisions, define responsibilities, and reduce unnecessary dependencies between groups.

Without that structure, adding people often creates complexity faster than it creates capacity.

New Team Members Need More Than a Task

A new artist doesn't just need a ticket.

They need to understand the project's visual language.

A new gameplay programmer needs to understand technical architecture.

A production coordinator needs to know who approves what, where information lives, how reviews happen, and which conversations matter.

Research on onboarding consistently shows that productivity depends not only on technical knowledge but also on social integration, organizational understanding, and confidence in navigating the team's workflow.

Until that learning happens, experienced teammates spend valuable time mentoring instead of producing.

That's an investment—and often a worthwhile one—but it should never be mistaken for immediate capacity.

Find the Constraint Before Expanding the Team

Before requesting additional headcount, ask a different set of questions.

Is this actually a capacity problem?

Or is work waiting for approvals?

Are priorities changing too frequently?

Is scope unstable?

Are teams blocked by dependencies?

Is ownership unclear?

Are decisions taking too long?

Is information difficult to find?

Is one specialist becoming the bottleneck for everyone else?

Each of these problems has a different solution.

Adding people only solves one of them.

When Adding People Is the Right Decision

This isn't an argument against hiring.

Sometimes additional people are exactly what's needed.

If there is a sustained backlog of ready work, responsibilities are clearly defined, scope is stable, and work can be divided with minimal coordination overhead, increasing capacity can significantly improve delivery.

Likewise, bringing in a specialist to remove a specific bottleneck—a technical artist, pipeline engineer, tools programmer, or experienced producer—may unlock the productivity of an entire team.

The key difference is intentionality.

You're adding people because you've identified the constraint—not because the schedule slipped.

A Producer's Checklist

Before asking for more headcount, consider these questions:

• What evidence shows this is a capacity problem rather than a workflow problem?

• Where is work actually waiting?

• What is the current bottleneck?

• Will another person remove that bottleneck or simply depend on it?

• Who will onboard the new team member?

• How long until they become productive?

• Is the work stable enough to scale?

• Can responsibilities be divided cleanly without increasing unnecessary coordination?

If you can't answer these questions, it's probably too early to conclude that the project needs more people.

Final Thoughts

People are not interchangeable units of productivity.

Every new team member brings talent, perspective, and future capacity—but they also require communication, context, onboarding, and coordination.

The best producers resist the temptation to treat headcount as the first solution.

Instead, they identify the real constraint, strengthen the system, remove the bottleneck, and then add people only when the evidence shows that additional capacity will genuinely improve outcomes.

Because successful production isn't about building the biggest team.

It's about building the team that can move forward together.