In the communication departments of mid-size and large organizations there's a silent pattern: everyone is competent at their own job, everyone works, there are weekly meetings, there's a shared calendar. And yet, looking at the combined output over a quarter, something stands out: the pieces don't talk to each other, the messages don't reinforce one another, and one person's decisions quietly invalidate someone else's before anyone notices in time.

That's what separates a team from a sum of individuals. And the cost of not being a team doesn't show up in any single piece — it shows up in the aggregate.

The trap of coordination as a substitute for teamwork

Many departments confuse coordinating with teamwork. Coordinating means splitting up tasks and flagging overlaps. Teamwork is something else: producing results that no single member would have produced alone, because they emerge from the interaction itself.

A coordinated newsroom is one where each person does their part and sends it up the chain to be stitched together. A newsroom that works as a team is one where the final result improves through internal conversation — where someone flags an inconsistency with a piece from last week and both get adjusted, where a junior writer corrects a senior one because they've read something the senior hasn't.

The clearest sign of a team isn't social cohesion. It's that the combined output improves when someone junior challenges someone senior — and the senior person is grateful for it.

The three operating conditions of a real team

In our work with internal and external communication teams at complex organizations, we've identified three conditions present in teams that produce added value — and absent in those that merely coordinate:

  1. A binding shared goal. It's not enough for it to be written down: it has to be the standard the team is measured against, not the standard each member is measured against individually. When individual incentives pull in a different direction than the shared goal, the shared goal loses.
  2. Willingness to be corrected by anyone on the team. Especially by whoever has less seniority. When that willingness is missing, the team operates in courtesy mode: no one points out the mistake because it isn't their place, and errors pile up until they blow up.
  3. Shared operating memory. This isn't the intranet or the project binder. It's knowing, at any moment, what was said last month, what was promised to whom, and which decisions were left open. Without shared memory, every conversation starts from zero and drains the time of whoever actually remembers.

The invisible enemies of the team

In public and complex environments, three factors erode a team and are rarely named out loud:

Three dynamics that destroy teams without anyone deciding to

  • The expert who only surrounds themselves with people who agree with them. Usually well-intentioned. It turns every discussion into confirmation. The team stops thinking collectively and starts confirming the expert instead.
  • The protector who believes looking after the team means never pushing it. The team gets used to a low standard and loses the ability to respond when the organization demands more.
  • The producer who only reports what's already done. Weekly meetings cover completed tasks only. Whatever is stuck, uncertain or going wrong stays out of the conversation until it becomes a crisis.

Why multidisciplinary teams win at public communication

Communication for a complex organization demands different profiles: strategy, journalism, data analysis, technology, compliance. When these profiles work in silos, each one optimizes their own piece and the whole suffers. When they work integrated, decisions improve because they're made with several frames of reference at once.

A good example: a reach metric might be celebrated by the social media team, questioned by the analytics team (because the reach came from an audience that isn't strategic for the organization), and reframed by the strategy team (because it changes the reading of the past month). If those three profiles don't talk to each other, the report ships with the high number, and the organization makes the wrong call on a good-looking figure.

How a team is built, not how it's hired

Teams aren't hired, they're built. The difference matters. Hiring good people is necessary and not sufficient. Building a team requires deliberate interventions: meetings that discuss the how, not just the what; post-publication review rituals where the team learns from the last cycle; spaces that explicitly invite people to contradict a superior at no cost.

This is the job of whoever leads. It can't be delegated and it can't be bought. And it delivers results far above anything a tool upgrade can offer.

If you look at last quarter's aggregate output and see pieces that don't talk to each other, the problem probably isn't individual talent. It's team architecture.

Let's talk

No commitment. Reply within 48h.

Conclusion

A sum of competent individuals produces correct work. A team produces something different: results that improve because people challenge each other, remember collectively, and move toward a binding shared goal. That difference shows up in the quarter's aggregate, not in the piece of the day.

In public and complex communication, where every decision carries regulatory and reputational consequences, the difference between a sum of individuals and a team isn't cosmetic: it's the line between acting with collective judgment and piling up well-intentioned individual decisions that, together, lead nowhere.