There Are 3 Teams Of 18 Employees Working Today

The Morning the Office Split Into Three

You walk into the office kitchen at 9:15 a.m. and find three separate groups huddled around different tables, each deep in conversation. So naturally, one team is arguing over a spreadsheet. Another is sketching diagrams on a whiteboard. Here's the thing — the third is just... sitting in silence, staring at their laptops.

This isn't some abstract organizational theory. This is real life, right now, in a building that houses 54 people who technically work for the same company but might as well be on different planets.

What happened? Day to day, how did we get here? And more importantly, why does this particular arrangement — three teams of 18 employees working today — feel so familiar to so many of us?

What Is Team Fragmentation, Really?

Team fragmentation isn't just about people sitting in different rooms. It's about the invisible walls that go up when groups stop sharing information, stop understanding each other's priorities, and start operating on completely different assumptions.

In the scenario above, you've got 54 employees. But when you split them into three teams of 18, something shifts. On paper, they're all part of one organization. Each group develops its own rhythm, its own language, its own sense of what "success" looks like.

This isn't inherently bad. Specialization has value. But fragmentation becomes a problem when those three teams start working in isolation, solving the same problems three different ways, or worse — when they don't even realize they're solving the same problems.

The Psychology of Small Groups

There's actual science behind why 18 people tends to be a tipping point. Groups smaller than this often struggle with workload distribution and skill coverage. Groups much larger tend to fragment naturally into sub-groups anyway.

But 18? That's big enough that you can't have meaningful conversations with everyone in the group, but small enough that you develop a real sense of "us versus them" when compared to the other teams.

It's Dunbar's number territory — the rough cognitive limit on the number of people we can maintain stable social relationships with. Most researchers put that number somewhere between 10 and 20. So when you hit 18, you're right at the edge of being able to know everyone personally, but just past the point where you can easily coordinate with everyone.

Why This Matters More Than You Think

Here's what most managers miss: when you have three teams of 18 employees working today, you're not just managing three work groups. You're managing three potential cultures.

Culture isn't just ping pong tables and free snacks. Culture is how people communicate, how they make decisions, how they handle conflict, how they define "good work."

When those three teams develop different cultures, you get:

Silos that cost real money. One team builds a customer portal. Another team builds a completely different customer portal. A third team didn't even know the other two existed until the executive presentation where all three demos get shown back-to-back.

Communication breakdowns that compound. Team A assumes Team B knows about the client's special requirements. Team B assumes Team A handled the technical integration. The client gets a product that misses half their needs.

Morale issues that spread. When one team feels like they're carrying the load while another team seems to have it easy, resentment builds. And that resentment doesn't stay contained within one team — it starts leaking into inter-team meetings and company-wide communications.

How This Actually Plays Out

Let's get specific. Here's what three teams of 18 employees working today typically looks like in practice:

Team Formation and Initial Dynamics

The first few weeks are usually chaotic. That's why people are figuring out roles, establishing working relationships, and learning each other's communication styles. With 18 people, you're past the point where everyone can sit in one room and have a real conversation, but you're not yet at the point where you need formal project management structures.

Most teams try to solve this by appointing informal leaders — the person who's best at organizing meetings, the person who knows the most about the project, the person who's most comfortable speaking up in group settings.

Workflow Divergence

By month two, each team starts developing its own workflow. But team One might adopt a daily standup routine. In practice, team Two might prefer asynchronous updates. Team Three might just wing it and hope for the best.

These aren't trivial differences. They affect everything from how quickly issues get escalated to how consistently work gets reviewed.

Information Silos

This is where things really start to break down. Each team holds meetings that the other teams aren't invited to. Each team gets access to different pieces of information. Each team starts making assumptions about what the other teams know.

Before long, you've got three groups working with different information sets, different priorities, and different timelines.

Common Mistakes That Make This Worse

I've seen this play out dozens of times, and the same mistakes keep repeating:

Assuming Shared Understanding

Managers love to say "everyone's on the same page" without actually verifying it. But when you have three teams of 18 employees working today, shared understanding doesn't happen automatically. It requires active effort.

One company I worked with had three development teams building different modules of the same software platform. They all assumed they were following the same coding standards. They weren't. When they tried to integrate their modules, they spent two weeks rewriting code instead of adding features.

Over-Reliance on Documentation

Another common mistake: thinking that if you just write everything down, communication problems will disappear. Documentation is helpful, but it's not a substitute for actual human conversation.

People interpret written instructions differently. They miss nuances. Practically speaking, they fill in gaps with assumptions. And when you have three separate teams, those assumptions diverge rapidly.

Ignoring Cultural Drift

Teams naturally develop their own norms and values. Left unchecked, these cultural differences can become barriers to collaboration.

One team might value speed above all else. Another might prioritize perfection. And a third might focus on innovation. When these teams need to work together, their different values can create friction that has nothing to do with the actual work.

What Actually Works

After watching too many organizations struggle with this exact setup, here are the strategies that consistently make a difference:

Regular Cross-Team Syncs

This sounds basic, but it's shocking how often it gets skipped. Schedule regular meetings where representatives from each team share updates, flag potential conflicts, and coordinate on overlapping work.

Keep these meetings short and focused. The goal isn't to merge the teams — it's to maintain awareness across team boundaries.

Rotating Liaisons

Instead of having the same people represent each team in cross-team meetings, rotate the responsibility. This ensures that different perspectives get heard and prevents any one person from becoming a bottleneck.

For more on this topic, read our article on i must go down to the sea again or check out what is equivalent fraction of 3/4.

Shared Goals and Metrics

When teams have different success metrics, they naturally optimize for different outcomes. Align your measurement systems so that teams succeed or fail together.

This doesn't mean every team member needs identical KPIs. But there should be enough overlap that teams can't succeed while actively harming other teams.

Physical Proximity (When Possible)

If you can't colocate teams, at least make sure they have regular opportunities to interact in person. Remote work amplifies the natural tendency toward fragmentation.

Even something as simple as having lunch together once a week can help maintain the human connections that make cross-team collaboration possible.

FAQ

How do you manage three teams of 18 without drowning in meetings? Focus on outcomes, not activities. Schedule regular sync points, but keep them brief and action-oriented. Let teams handle their internal coordination independently.

What's the ideal size for a team anyway? There's no universal answer, but most research points to 5-9 people for teams that need to collaborate closely, and 15-25 for groups that can operate more independently.

How do you prevent one team from feeling like they're doing more work than the others? Establish transparent workload tracking early. Make sure all teams have access to the same information about priorities and deadlines.

Should teams report to different managers? Not necessarily. Sometimes a single manager overseeing three teams of 18 works better than three separate managers, because it's easier to maintain consistent standards and communication.

The Reality Check

Here's what I've learned from watching organizations try to figure this out: three teams of 18 employees working today isn't a problem to be solved. It's a reality to be managed.

The goal isn't to

The goal isn’t to eliminate complexity, but to harness it. And when three teams of 18 operate under a single umbrella, the challenge shifts from “how do we keep everyone in sync? ” to “how do we create a framework that lets each group thrive while still moving as a cohesive unit?

Clarify Roles and Decision‑Making Authority

Ambiguity in who owns what quickly spirals into duplicated effort or missed deadlines. Draft a concise RACI matrix for each major deliverable, defining who is Responsible, Accountable, Consulted, and Informed. Pair this with a clear escalation path: junior issues are routed through the team lead, cross‑team blockers go to the rotating liaison, and strategic pivots are decided in the quarterly steering meeting. When everyone knows the exact moment they need to step in, the system runs smoother than any ad‑hoc chat thread ever could.

Adopt a Light‑Weight Governance Cadence

Too many meetings become a drain, but too few leave gaps that breed misalignment. A pragmatic rhythm might look like this:

Weekly 15‑minute stand‑up – each team lead shares a single headline metric and any immediate roadblocks.
Bi‑weekly 30‑minute deep‑dive – rotating liaison presents a brief status report, highlights dependencies, and solicits input on upcoming work.
Quarterly 60‑minute strategy session – all three teams convene to review progress against shared goals, adjust priorities, and celebrate wins.

The key is to keep each touchpoint purpose‑driven and time‑boxed; the meeting itself becomes the artifact, not the conversation that could have been an email.

use Technology as a Glue, Not a Replacement

A shared project board (Kanban or Scrum) that is visible to all three teams creates a single source of truth for task status, priority shifts, and ownership. Integrate the board with a lightweight chat channel dedicated to cross‑team announcements, so that important updates are not lost in the noise of everyday messaging. Additionally, a simple dashboard that aggregates the core metrics from each team lets leaders spot trends at a glance, prompting timely interventions before small frictions become large crises.

build a Culture of Mutual Respect

Even the most elegant process will falter if the underlying mindset treats other teams as competitors for resources or credit. Encourage practices that surface and reward collaborative behavior:

Peer recognition – a quick “shout‑out” in the cross‑team channel when a member from Team A helps unblock a deliverable for Team B.
Joint retrospectives – after a major release, bring together representatives from each team to dissect what worked, what didn’t, and how the handoffs can improve.
Shared learning moments – short lunch‑and‑learn sessions where a team presents a tool, technique, or lesson learned that benefits the others.

When people see that success is a collective story rather than a solo narrative, the incentive to protect silos diminishes naturally.

Anticipate and Mitigate Conflict Early

Differing priorities are inevitable; the real risk lies in how they are addressed. Institute a “conflict‑first” protocol:

Identify – the rotating liaison flags a tension point during the bi‑weekly deep‑dive.
Clarify – each side briefly states its objective and constraints, ensuring the root issue is visible.
Collaborate – the group brainstorms alternatives, aiming for win‑win solutions rather than compromise that leaves one side feeling short‑changed.
Commit – a concrete action item with owners and deadlines is recorded and revisited in the next stand‑up.

By institutionalizing this loop, conflicts become manageable events rather than hidden saboteurs.

Embrace Adaptive Leadership

Leaders of multi‑team environments must shift from command‑and‑control to coaching. Their primary duties become:

Modeling transparency – openly sharing constraints, trade‑offs, and the rationale behind decisions.
Removing barriers – using influence to secure needed resources, clearing bureaucratic hurdles, or reallocating capacity when imbalances arise.
Nurturing trust – investing time in one‑on‑one conversations, listening actively, and following through on promises.

When leaders embody these behaviors, the three teams of 18 start to feel less like separate fiefdoms and more like interdependent parts of a single engine.

Conclusion

Managing three teams of 18 is less about imposing a rigid hierarchy and more about constructing a resilient ecosystem where autonomy, alignment, and shared purpose coexist. By instituting concise, purpose‑driven syncs, rotating liaison roles, aligning metrics, and providing clear role definitions, organizations can turn the inherent complexity into a source of strength. Supporting these structures with transparent technology, a culture of mutual respect, and proactive conflict resolution ensures that the teams remain agile, motivated, and focused on the same overarching objectives. In the end, the reality is not a problem to be solved once and for all, but a dynamic system to be continuously refined—one that, when well‑managed, delivers results far greater than the sum of its parts.