I Used to Look for the Action. Now I Look for the Pattern.

My thinking on this has changed. That is probably the most honest way to start.

Earlier in my career, the question I asked most often was: what needs doing? It was a good question. It produced action. It moved things forward. In roles where the work was immediate and the stakes were high, it was often the right question.

Then, as I took on more responsibility, the question shifted. Who needs to do it? I was managing people, coordinating responses, making sure the right person was in the right place. Still action-focused, but beginning to think about the team rather than just the task.

Then: who else needs to be involved? Partnership working became central. The problems I was dealing with did not sit neatly within one organisation. They required multiple agencies, multiple perspectives, multiple contributions. The question became about the collective response, not just the individual action.

And then, gradually, a different question began to emerge.

Why is this happening again?

The Shift to Pattern

I have worked across social work, victim services, practice education and community safety leadership. Each of those roles gave me a different vantage point on the same underlying problems.

When I previously worked as a social worker, I saw individual cases. When I moved into practice education and lecturing, I began to see patterns across cases. When I moved into community safety leadership, I began to see patterns across services, across partnerships, across years.

The same problems kept appearing. Not the same people, necessarily, but the same dynamics. The same thresholds that created gaps. The same handover points where risk fell between organisations. The same recurring locations. The same types of vulnerability that services were not designed to address.

Operational action remained important. Leaders still need operational grip. The ability to respond effectively to what is in front of you does not become less valuable as you develop strategic thinking. But experience taught me that responding well to individual cases, however important, does not change the conditions that keep producing them.

The question I now find myself asking most often is: what condition in the system is continuing to produce this outcome?

Case, Action, Partnership, Pattern, System

I think of this as a progression, not a hierarchy.

A case requires action. An action requires the right people. The right people require effective partnership. Effective partnership, over time, reveals patterns. Patterns point to systems.

This does not mean that every problem is a system problem. Some things genuinely are individual failures, practice issues or capability gaps. But the instinct to reach immediately for individual accountability, without first asking whether the system is contributing, is one of the most common errors I see in community safety leadership.

Repeat demand is one of the clearest signals. When the same person, the same address, the same type of incident keeps appearing, the question is not only how to respond better this time. It is what is creating the conditions for this to keep happening.

Recurring risk at organisational interfaces is another. When risk consistently falls between agencies, the problem is rarely that the individuals involved are incompetent. It is more often that the system has not been designed to hold the risk at that point. Thresholds, referral routes, information-sharing arrangements, accountability structures: these are system conditions, and they require system-level leadership responses.

What This Means for Leadership Development

Leadership development is often framed as becoming better at answering the same questions. Getting faster, more decisive, more skilled.

But some of the most significant development I have experienced has involved learning to ask a different question altogether.

Moving from "what needs doing?" to "why does this keep happening?" is not a small shift. It requires a different kind of attention, a different relationship with data, a different tolerance for complexity, and a different willingness to challenge the structures and processes that your organisation has invested in.

It also requires patience. System-level change is slower than operational action. The feedback loops are longer. The results are less immediately visible. That can be uncomfortable for leaders who are used to the satisfaction of completing a task.

But the longer I have worked in community safety, the more convinced I have become that the most important leadership contribution is often not the action taken today, but the question asked about why today's action keeps being necessary.

Explore the 4P Community Safety Leadership Framework

This article sits within the Lead Systems domain of the 4P Community Safety Leadership Framework, which explores how leaders understand and influence the wider conditions that shape community safety outcomes.

Explore Lead Systems | Explore the full Leadership Framework