I keep coming back to a simple, uncomfortable observation: most of what blocks an organization is invisible to the people inside it. We respond to the event in front of us — the missed number, the difficult meeting, the stalled project — and we almost never see the pattern that produced it. Systemic perceiving is the discipline of widening that lens on purpose: learning to notice relationships, feedback loops, and the quiet mental models that shape how a system behaves long before any single decision is made.
In practice this is less mystical than it sounds. A leadership team that only sees events fights the same fire every quarter. A team that learns to see patterns starts asking a different question — not “who failed?” but “what about the way we work makes this outcome so reliable?” That shift in attention is small, but its consequences compound. Once you can see the structure, you stop treating symptoms and start changing the conditions that generate them.
I find three lenses useful. The first is events: what actually happened. The second is patterns: what keeps happening, across time and across teams. The third is structure: the incentives, beliefs, and unspoken rules that make those patterns almost inevitable. Most organizations are fluent in the first lens, occasionally reach the second, and rarely operate from the third — which is exactly where durable change lives.
Systemic thinking also changes how a leader shows up. When you accept that you are part of the system you are trying to change, blame becomes far less interesting than curiosity. You begin to ask what your own behavior is reinforcing. That humility is not soft; it is the most practical stance I know, because it puts the one variable you can actually control — yourself — back at the centre.
Once a leadership team can see the system it is part of, the same problems stop repeating.
The short briefing below is my attempt to make this tangible in a few minutes. Watch it with a notebook, and try one experiment afterwards: take a recurring problem in your team and, instead of solving it, map the pattern beneath it. Most leaders are surprised by what becomes visible — and by how many new options appear once the system can finally be seen.
A practical note: systemic perceiving is a muscle, not a personality trait. You build it by slowing down at exactly the moments you most want to react — the escalation, the blame, the quick fix — and asking what part of the system just expressed itself. Do that consistently and your team starts doing it too, because attention is contagious. Over months an organization develops a shared ability to see itself, and that shared sight is what makes large-scale change possible at all.
Full paper
Open the full PDF