In a complex organization, communication problems are rarely what they appear to be. A reputational crisis is usually not a social media problem. Internal disengagement is not an intranet problem. Falling trust in a public service is not a media-plan problem. These are symptoms of a system that isn't working as a whole.

And yet the most common reflex is still to intervene on the piece. Replace the community manager. Redo the website. Launch a campaign. The system stays intact, and a few months later the symptom comes back.

The problem with always operating piece by piece

Thinking in pieces has one advantage: it's fast, demonstrable, and lets you present a result at the next meeting. It also has a structural cost: every local intervention generates consequences elsewhere in the system that were never measured beforehand and are almost never traced back afterward to their real origin.

The most expensive consequence of always operating piece by piece is that problems come back. They come back wearing a different face, in a different area, tied to a different person in charge. And the organization treats them as new every time.

When the same symptom reappears every year in a different form, it isn't bad luck: it's a sign that the problem is in the system, not in the piece.

What changes when you think in systems

Systems thinking isn't an elegant metaphor. It's a concrete operation that changes three things in how a complex organization's communication is approached:

  1. It changes the diagnosis. Instead of asking "what's failing here," you ask "what pattern is repeating, and what interactions are sustaining it."
  2. It changes the intervention. Instead of acting on the most visible symptom, you act on the point in the system with the greatest capacity to affect the whole (what systems thinking calls a leverage point).
  3. It changes measurement. Instead of measuring the immediate local effect, you measure the effect on the system's aggregate behavior, accepting that the response may take time.

Three systemic patterns that keep showing up in public communication

In our work with public organizations, three patterns recur with a frequency that stopped being anecdotal a long time ago. All three are systemic. All three keep being tackled, unsuccessfully, piece by piece.

1. Quick fixes that make the problem worse

An organization with eroding trust launches more campaigns to "be more present." More presence with the same worn-out narrative amplifies the problem instead of solving it. The piece-level intervention (more communication) makes the system worse (less trust through overexposure).

2. Cause and effect separated in time and space

A transparency cutback made today shows up as a reputational crisis eighteen months later, in an apparently unrelated case. The organization looks for the cause in the immediate past and doesn't find it. The system does: it remembers perfectly.

3. The obvious solution is the wrong one

If the organization publishes little, the assumption is that it should publish more. If it publishes a lot and it isn't working, the assumption is that it should publish better. The third option is almost never considered: publish differently, with a different message architecture, aimed at a different node in the system.

The shift in framing: from the closed project to the continuous cycle

Thinking in systems in organizational communication means moving away from isolated campaigns and operating instead as a continuous cycle. This is exactly what the VISTA methodology structures: plan with a view of the whole, act with judgment, check what happens across the whole system (not just in the piece you intervened on), and adjust the next round.

This isn't trivial. Breaking the logic of the closed project requires changes in how services are procured, how team performance is measured, how results are reported to governing bodies. But it's the only way to make problems stop coming back.

What to expect from a provider that thinks in systems

If your organization is public or complex and you're evaluating a communication provider, three signals separate the one who thinks in pieces from the one who thinks in systems:

  1. Before proposing, they map. They ask to see the whole system: actors, flows, past decisions and their effects. They don't jump to the solution.
  2. They identify leverage points. They don't tell you "you need to communicate more"; they tell you "this specific node is sustaining the pattern — this is where to intervene."
  3. They accept that the response takes time. They don't promise results in weeks for variables that only move over quarters. Being honest about timing is a sign of systems thinking.

If the same communication problems keep coming back with a different face every year in your organization, it's probably not an execution problem. It's a framing problem.

Let's talk

No commitment. Reply within 48h.

Conclusion

Communication in a complex organization isn't fixed piece by piece. It gets fixed when someone agrees to look at the whole system, identifies the pattern sustaining the problem, and dares to intervene at the point where the needle actually moves, even if it isn't the most visible one.

That requires patience, judgment, and a different conversation with leadership. But it's what separates organizations that improve from those that recycle the same problem for a decade straight.