Most team communication problems are role problems

In almost every team retrospective, someone eventually writes "communication problem" on a sticky note. The answer lands within the week. One more Slack channel, one more weekly sync, two more people in copy. Six months later, the same sticky note comes back.

Those answers treat a symptom. Most teams already communicate a great deal. What they lack is a shared answer to who decides what. As long as that question stays open, everyone compensates by telling everyone, just in case.

Three situations another channel leaves untouched

Three scenarios show up everywhere, and each one is settled by writing a role.

The message everyone reads and nobody picks up

A customer reports a bug in the support channel. Four people see it. Each assumes another one has it, because nothing says who owns that kind of issue. The message sits there for three days.

The retrospective will call it a communication problem. Yet the message went through, it was read, and it simply had no accountable recipient. One written accountability settles it in a line: answers bug reports within 24 hours.

The meeting that exists so a decision can happen

A weekly meeting with eight people whose only real output is a call on a tool subscription. Nobody is allowed to decide alone, so everyone gets invited. The company pays eight hours of work a week for a decision that needs ten minutes.

A domain assigned to a role makes the meeting disappear. The Tooling role decides on subscriptions up to $200 a month, and past that the matter goes through a consent decision with the people it touches.

Copying everyone

Putting six people in copy costs a lot of attention and costs the sender nothing. It is insurance. If the thing goes sideways, nobody can claim they were out of the loop. People copy widely because they do not know who should have decided, so they warn broadly.

Once each person's scope is written down, the recipient list gets short and obvious.

What the research says about decision roles

Paul Rogers and Marcia Blenko put the question on the table in the Harvard Business Review of January 2006, under the title "Who Has the D?". They argue that an organisation's ability to decide quickly and then carry out what it decided predicts performance better than its industry, its size or its strategy. That ability rests on a single point, knowing who owns each decision. When that point stays vague, the decision dissolves into internal process and nobody can say where it stands.

With the Economist Intelligence Unit, Bain surveyed 300 companies with more than $500 million in revenue. The average company loses a quarter of its productive capacity to organisational friction, pointless meetings and redundant coordination. The top quartile loses half as much. That quarter is made of exactly the exchanges and meetings that exist to paper over unclear responsibilities.

What roles leave open

Of course, writing roles settles only part of it. Some of the silence in a team comes from fear, and no accountability changes that.

In 2003, Frances Milliken, Elizabeth Morrison and Patricia Hewlin interviewed forty full-time employees across a range of industries for the Journal of Management Studies. 85% had been in a situation where they judged an issue important and said nothing to their supervisor. The reasons they gave cluster around fear of being seen negatively and a belief that nothing would change. The sample is small, and twenty years of research on organisational silence has pointed the same way. It is one of the mechanisms hierarchy builds in by design.

Those situations call for time, a facilitation practice, and managers who can take bad news without sending it back to the sender. A written role helps at the margin, by giving the person an explicit mandate to raise the issue. It leaves the relational work fully intact.

Write a role instead of opening a channel

A useful role holds three blocks.

Its purpose says why it exists, in one sentence, something like "customers get a reliable technical answer".

Its domain says what it decides alone, without asking anyone: the content of the knowledge base, tool subscriptions under $200 a month.

Its accountabilities say what others can expect from it, in action verbs: answers bug reports within 24 hours, publishes release notes on every deploy.

The test fits in one question. Take the last three issues that dragged on in your team and ask, for each one, which role should have made the call. When the answer is "we discussed it together", you have found the missing role. That is also what separates a role from a job description. The job description covers an employment scope, the role covers decision authority.

Where conversations live once the roles are written

That leaves the question of where conversations land. Attaching a discussion to a role rather than to a topic channel changes two things. The people concerned are the ones holding the role, with no distribution list to maintain. And six months later, the trail sits where you go looking for it.

That is how Rolebase works. Every discussion belongs to a role and moves through statuses, from preparation to closed, with the option to invite someone from another role for a single conversation. Decisions are recorded in the role that made them, with their context, and show up in the organisation news feed. Meetings review the role's active discussions instead of reopening every subject from scratch. When a question comes back, search shows whether it was already settled, by whom and when.

See the features, or create your organisation free for up to five active members.

How do I know whether our communication problem comes from unclear roles?

Take the last three issues that dragged on and ask, for each one, which role should have decided. When the answer is "we discussed it together" or "it depends", the issue belongs to nobody. What is missing is a domain or an accountability, rather than a channel.

Should we cut meetings to improve team communication?

A meeting that exists only to make a call possible disappears on its own as soon as a role gets that domain. The rest deserve an agenda built from the open items of the roles in the room. Meeting overload is almost always a symptom of unclear responsibilities.

How many communication channels should a team have?

The rule for opening one matters more than the count. A channel created for a subject that already belongs to a role duplicates the information and scatters the trail. A channel created because nobody knows where to send a type of request points to a missing role.

Is writing roles enough to make people speak up?

Milliken, Morrison and Hewlin found in 2003 that 85% of the employees they interviewed had stayed quiet on something they judged important, out of fear of being seen negatively. A written role gives an explicit mandate to raise a tension, which helps. Whether it feels safe depends on how bad news gets received.