In many organizations, communication is treated as something that should happen naturally. People talk to each other, attend meetings, exchange messages and make decisions. If something goes wrong, the usual response is to ask people to communicate more clearly, share information earlier or align more closely.
Sometimes, that is exactly what is needed. But when the same problems keep returning, it is worth looking beyond the individual conversation.
- Why does important information repeatedly arrive too late?
- Why do decisions get made but never translate into clear next steps?
- Why do the same topics keep coming back to meetings?
- And why does coordination so often depend on one person remembering to connect all the dots?
These patterns are rarely just about how well people communicate. They are also shaped by the way communication is organized.
This is where System Thinking in Conversations comes in: looking at communication as a system of connected roles, processes, agreements, tools and everyday behaviours — and understanding how they influence what happens between people.
Communication doesn’t organize itself
Think of a startup in its early days. Everyone knows what is happening because people work closely together, decisions are discussed directly and information travels through informal conversations. As the company grows, new teams emerge, responsibilities become more specialized and work becomes increasingly interdependent.
What worked with eight people may no longer work with thirty or eighty. Information is spread across meetings, chat channels and project management tools. Decisions are made in one place and need to be understood somewhere else. People assume others have been informed, while others are waiting for someone to clarify what happens next.
The problem isn’t necessarily that people have become less willing to communicate. The system around them has changed, but the way communication works may not have changed with it.
In a larger organization, the situation can look different. Processes are documented, responsibilities are defined and meetings are scheduled. Yet information still gets lost between departments, decisions take too long or nobody feels responsible for the handover between one team and another.
And the same dynamic can be found in families. One person remembers appointments, coordinates plans and makes sure everyone has the information they need. Everything seems to work — until that person is no longer available. Suddenly, it becomes clear how much of the system depended on their memory and invisible coordination work.
Different contexts, similar questions: What makes these patterns possible? What keeps them going? And what would need to change for people to work together differently?
What does it mean to see communication as a system?
A system-thinking perspective helps us understand the connections between individual interactions and the conditions surrounding them. Instead of focusing exclusively on a person’s behaviour or a message that wasn’t clear enough, we look at how different elements influence one another.
There are five useful areas to explore.
These areas are connected. Introducing a new tool won’t solve a problem if nobody knows who is responsible for updating it. Clearly defined responsibilities won’t help if people cannot access the information they need. And a well-designed process may remain unused if it adds steps without helping people do their work.
The question is not simply whether communication processes exist. It is whether the different parts work together — and what they produce in practice.
Leadership creates the conditions. The team makes the system work.
Managers and leaders have an important role in shaping communication. They help clarify expectations, establish responsibilities, create workable decision-making processes and make sure communication is treated as part of the work rather than something people are expected to figure out on their own.
But a system doesn’t become effective simply because a manager has designed it, explained it or documented it.
People discover what helps, what creates unnecessary friction and where information still gets lost. They see whether agreements hold up when priorities change, workloads increase or a situation arises that nobody had anticipated. They also notice when a process looks sensible in theory but doesn’t fit the way work actually happens.
One response would be to remind everyone of the rule. Another would be to explore what the experience is telling the team. Is the agreement clear? Does it fit into existing routines? Is someone responsible for making sure affected colleagues know about a decision? Is there an easy way to flag that the process isn’t working?
The second approach treats the system as something to learn from and improve, rather than a set of rules people simply need to follow.
This requires a different relationship between leadership and the team. Leaders need to create the conditions, clarify the direction and make space for improvement. Team members need to use the system, test it against real situations and contribute their observations. Both need to be willing to adjust the arrangement when experience shows that something isn’t working.
The responsibility won’t always be equal. It depends on roles, authority and context. But the people who live and work within a system need a way to influence how it develops.
Start with one recurring situation
You don’t need to redesign every process at once. A useful starting point is one specific problem that keeps coming back. Let’s say changes in priorities regularly reach some team members too late.
Rather than immediately asking who failed to pass on the information, trace what happens.
- Who first learns about the change?
- Where is the decision recorded?
- Who needs to know in order to adjust their work?
- How does the information reach them?
- How do people know the decision has been received and understood?
- What happens if someone misses the message or discovers a contradiction?
This helps distinguish individual mistakes from gaps in the system. Perhaps responsibility for communicating the change is unclear. Perhaps the decision is recorded in a place people rarely check. Perhaps nobody has agreed how to confirm that the people affected have been informed.
Once you have identified a likely gap, choose one small change to test. Agree on what will happen differently, who will be involved, who will coordinate the experiment and how long you will try it.
Then observe what happens in practice. Is the information reaching people earlier? Are fewer questions being repeated? Is it easier to see who needs to act next? Where does the new arrangement create friction? Use what you learn to decide what to keep, change or remove.
This is not about finding the perfect process on the first attempt. It is about making communication more reliable by learning from the way people actually work together.
A tool to help you map your communication system
I am developing a free tool called the Communication System Map as part of my Conversations Framework.
The Communication System Map complements the Conversation Compass, another tool in the framework. The Conversation Compass helps you explore what happens within a specific conversation — how you interpret a situation, react and respond. The Communication System Map looks at the wider environment that shapes those interactions: the roles, processes, agreements and tools people rely on.
One helps you understand the dynamics of a conversation. The other helps you examine the conditions in which conversations take place. Neither offers a universal answer. Both are ways to make patterns more visible and create room for a more deliberate response.
A system is only as good as its everyday reality
When communication problems repeat, it is worth moving beyond one question and asking another.
Individual communication skills matter. So do clarity, attention and personal responsibility. But these qualities operate within a system that can either support people or make their work harder than it needs to be.
And that system is never finished. Teams grow, relationships change, priorities shift and new dependencies emerge. What worked six months ago may no longer be enough.
The aim isn’t to eliminate every misunderstanding or create a process for every possible situation. It is to make it easier for people to share information, coordinate their work, make decisions, address tensions and adapt when something changes.
If this sounds familiar
Perhaps you also notice that the same communication breakdowns keep returning, despite everyone’s best efforts — that coordination rests on one person, information gets lost between teams, and agreeing to “communicate better” doesn’t change things for long.
Often the issue isn’t a lack of skill or another tool, but how the system around the conversations is built — the roles, processes and agreements that make a certain outcome likely. This is often where it helps to combine a look at the individual conversation with a look at the system as a whole.
In my work, I help leaders, teams and organizations examine their communication systems, find recurring gaps and choose changes that actually work in their context.
Book a first session