When Is a Team Too Big? When Teams Grow and Nothing Moves Forward

Your team has grown, and you can feel it in daily operations. In the past, everything could be resolved quickly through informal channels. Today, every decision takes too long, nobody feels truly responsible, and everyone is stretched to their limits.

And somehow you think to yourself: "We have more people now—shouldn't everything be faster and better?"

However, that's often not the case. In this post, I want to examine possible reasons for this and also look at what helps get back into the flow.

The term "team" is often used quite loosely. Sometimes it refers to an entire department, sometimes a project group, a squad, an entire company, or simply "everyone who's somehow involved."
When we talk about team size or team composition, it's worth first clearly defining what a team is in the strict sense.
I'm basing this on what psychologist Richard Hackman, among others, has described:
A team is a clearly defined group of people who work together on a task over an extended period, pursue a common goal, and are highly interdependent in achieving it.
A few points are particularly important here:

• It's clear who belongs and who doesn't.
• The group is relatively stable, not constantly changing in composition.
• Members depend on each other: they can only achieve good results together.
• There's a shared task or direction that's more than "everyone doing something in the same area."
• And it needs a framework within which this team can operate: decision-making authority, resources, communication.

There's no magic number. It depends, as always. However, there are numerous studies and also practical experience.

These numbers aren't hard rules, but they provide good guidance: When is it worth taking a closer look and asking whether the current team size or composition still makes sense?

The question of when teams become too large is often discussed, but too small isn't good either. A team isn't automatically a team just because two people are working on something.

A real team has a common goal, needs to coordinate, and depends on each other to achieve that goal.

As a practical rule of thumb: Three people is the minimum for real team behavior to emerge. Below that, you're often more of a duo with coordination needs, which can be perfectly fine in many cases. But then you don't need team development—you might need clear coordination and agreements instead.

In my experience, teams with up to 7 people usually work very well; when there are more, it can become unwieldy.
What I often observe then:

When several team members feel like they're losing track despite coordination meetings, no longer know what others are working on, can't see a common goal anymore—that's often a clearer indicator than any study.

When a team grows, there are often ideas like: "We need a new meeting." Sometimes also: "We need a new role" or "We can solve this with tool XY." All of this can help address coordination effort, but rarely solves the actual problem.

What sometimes works when a real split isn't possible—e.g., because the company doesn't allow new teams: Working in sub-teams.

This means: A team of ten people internally divides into smaller groups, each focused on one topic. This creates more focus, less coordination effort—and the team still formally remains intact.

Maybe you've been working as one team so far, everyone does everything somehow. Decisions are made together, tasks are sometimes distributed spontaneously. The thought of splitting up feels unfamiliar at first. Almost like a break. What if the connection is lost?
Especially in young companies, I often observe uncertainty at this point and the reflex to leave everything as it is for now. Yet a team split can achieve exactly the opposite: It strengthens the connection—because clarity creates trust and smaller units facilitate real collaboration.

Smaller teams provide relief. They reduce cognitive load, reduce coordination effort, and create more focus. A prerequisite for this is also that it's clear:

• Who is responsible for what
• How the interfaces work
• And where decisions are made

The design of tasks also plays an important role. Ideally, teams can deliver value independently of each other, with few dependencies—close to the market and users.

In one project, we used the image of cell division for this: Knowledge, attitude, and culture of the original team are consciously carried forward and continue to develop in the new units.

The crucial question isn't just: What do we lose through a split? But also: What do we gain? Discussing these questions with the team from the beginning and returning to them repeatedly helps with letting go and creates real momentum toward the new.

Sometimes it's not a single team that's the problem, but the overall structure. Multiple teams work alongside each other, but not well coordinated with each other. Typical signs of this:

• There are thematic overlaps without clear coordination.
• Teams block each other because they're too dependent on one another.
• Responsibility gets stuck with individuals or is so diffuse that nobody is responsible.
• Handoffs lead to friction losses instead of smooth collaboration.

In such situations, off-the-shelf reorganization doesn't help. It's more useful to take a close look at the business domain and work flows. This works best together with those who experience them daily and know their business domain.

Collaborative methods like Event Storming, User Needs Mapping, or Value Stream Mapping help develop a shared picture. These formats help make dependencies, responsibilities, and interfaces visible. Wardley Mapping can also be useful as a supplement—for example, when it comes to technological decisions, make-or-buy, or platform architecture.

Only then is it worth looking at the appropriate team design. For example, with Team Topologies or dynamic re-teaming approaches that help create structures that facilitate collaboration and enable flow.

Answer the following questions for your team:

• Are there tasks that regularly get left undone because nobody feels responsible?
• Do you know what others are currently working on?
• Do you often feel like you're taking on things that should really belong elsewhere?
• Are you highly dependent on other teams?
• Do you lack focus because everything is equally important and you don't know what to tackle first?
• Are you constantly working on multiple topics in parallel?
• Do certain topics always get stuck with the same people?

If you nodded internally to several questions, this might be the right moment to look at your team structure and size.