Liaison Communicator: you connect people and ideas across the team

You connect people, ideas, and teams with each other: your contribution tends to be making the information and the people understand one another, more than executing yourself.

When two people or two subgroups on the team aren’t communicating well, you’re usually the one who bridges them.

A bridge between people, not a formal role

This is a variant of the socioemotional role that Robert Bales described in his classic research on small groups (1950), focused specifically on coordination and the flow of information between people or subgroups, rather than on the emotional cohesion itself that characterizes other roles in the same family.

Ways this profile shows up

• You tend to be the one connecting different people or teams with each other, even when it’s not formally your job.
• You make sure information reaches whoever needs it, even when that’s not your direct task.
• You help different points of view within the team understand each other, translating when it’s needed.
• You act as a bridge when two people or subgroups aren’t communicating well with each other.

The cost of a function that almost never gets seen

This profile can end up absorbing an invisible coordination load that nobody else fully sees or values, precisely because it doesn’t translate into a tangible result on its own. Making this work visible, for example by naming it in team meetings, is one possibility that in some cases helps it get recognized as the real contribution it is, though each team’s context is different.

Why shared information holds the team up, according to Stanley McChrystal

General Stanley McChrystal, in Team of Teams, describes how he had to transform a rigid command structure into a network of small teams capable of deciding on their own, and describes shared access to the same information as one of the conditions that made that autonomy possible without losing coordination: when every subgroup understands what the others are doing, it decides better on its own, without having to wait for instructions from above. That idea lines up directly with this role: the invisible coordination load it tends to absorb is, in fact, the very condition McChrystal points to as essential for a network of teams to work. It isn’t a side task next to each subgroup’s “real” work, it’s what lets the whole thing move forward coordinated instead of fragmented, even though its value rarely shows up as a visible deliverable on its own.

If your main contribution to the team is more about tending the emotional climate than coordinating information, check out the cohesion builder role. You can go back to your full result in the What’s My Team Role? test.