The meeting had all the right people in the room.
A law enforcement representative. A prosecutor. A victim advocate. A forensic interviewer. A child welfare worker. On paper, it was exactly what a coordinated community response is supposed to look like: multiple disciplines, multiple agencies, a shared case and a shared table.
And yet nothing was coordinated. Everyone reported what their agency had done. Nobody asked what the others needed. The conversation moved in parallel lines that never quite touched. People left with their own next steps and no shared picture of what they were collectively trying to do.
It was a team in a technical sense. It was not a system.
What Makes Something a System
We use the words interchangeably — team, group, coalition, system — as though they describe the same thing at different scales. They do not.
A team is a collection of people with a common goal. A system is something more specific: It is a structure in which the parts are functionally interdependent, where what one part does changes what is possible for the others, and where the whole produces something none of the parts could produce alone.
The distinction matters because you can have every right person in the room and still not have a system. You can have talented, committed, well-resourced individuals who work in close proximity and never actually integrate. And when that happens, leaders often respond by adding more: more meetings, more communication tools and more team-building without addressing the underlying structure.
More people in parallel is still parallel.
What Gets Lost in the Gap
The cost of confusing a team for a system is not always visible in the short term. People are working. Things are happening. Progress, measured individually, looks fine.
What gets lost is the emergent capacity; the things that only become possible when parts of a system are genuinely responding to each other. Early warning. Adaptive response. The ability to catch what falls between roles.
In human services, that gap has consequences for the people being served. A survivor moving through a system that is not actually integrated experiences that fragmentation directly in repeated disclosures, in contradictory information, in the feeling that no one has the full picture. The system’s structural problem becomes the client’s lived experience.
In any public sector context, the gap shows up as inefficiency at best, and at worst, as harm.
What Leaders Actually Need to Build
Building a system requires something different from building a team. It requires attention not just to who is at the table but to how information moves between them, whether what one part learns reaches the other parts that need it. It requires boundaries that are clear enough that each role knows what it is responsible for, and permeable enough that those roles can genuinely influence each other.
It requires feedback. Not the feedback of a performance review, but the ongoing, structural kind; the loops that tell the system whether what it is doing is working and create the conditions to adjust when it is not.
And it requires a shared reference point. Not just a shared mission statement, but a shared understanding of what success looks like at the case level, the program level and the community level, something concrete enough that people can tell when they are drifting from it.
None of this is about harmony. Functional systems are not conflict-free. They are systems where tension is productive rather than corrosive and where disagreement surfaces problems rather than burying them.
The Question Worth Sitting With
Most leaders I know went into this work because they care about outcomes. They want the people they serve to get what they need. They want their teams to thrive. They are working hard toward both.
But wanting the right outcomes and building the right structure are not the same thing. You can have a room full of capable, motivated people and still have built something that functions like a collection of individuals rather than a coherent whole.
The question is not whether your team is talented. It almost certainly is.
The question is whether what you have built is actually a system, and if not, what would it take to get there.
Megan Rodgers is a doctoral candidate and human services professional with over eight years of experience coordinating multidisciplinary teams across complex organizational systems. Her work sits at the intersection of clinical practice and applied theory, with a particular focus on systems thinking, self-control frameworks, and the institutional forces that shape human behavior. Megan has presented at professional conferences on topics including imposter syndrome, bringing research-grounded insight to audiences navigating the realities of public service. She is passionate about bridging the gap between academic theory and everyday practice; making big ideas accessible, actionable, and real.
Leave a Reply
You must be logged in to post a comment.