The reason so many public sector initiatives fail is not lack of effort, lack of funding or lack of good people. It is that we keep applying simple solutions to problems that are not simple and then wondering why the problems persist.
This is not a criticism. It is a description of what happens when the tools we have were built for a different kind of problem than the one we are actually facing.
Two Kinds of Problems
There is a useful distinction that does not get made often enough in public service: the difference between complicated problems and complex ones.
Complicated problems are hard, but they are knowable. Building a bridge is complicated. So is filing a federal grant report, or designing a new intake system, or coordinating a multi-agency response protocol. These problems have many moving parts, but the parts behave predictably. With enough expertise, enough time and enough resources, complicated problems can be solved. Once the solution is found, a complicated problem tends to stay solved.
Complex problems are different in kind, not just degree. Think about reducing domestic violence in a community. Or improving educational outcomes for children experiencing housing instability. Or building trust between law enforcement and the populations they serve. These problems involve human beings in relationship with each other and with systems that are constantly changing. The parts do not behave predictably. What works in one neighborhood may fail in another. What worked last year may not work this year. The problem shifts as you work on it.
You cannot solve a complex problem the way you solve a complicated one. But we keep trying.
What Happens When We Get This Wrong
When we treat complex problems as complicated ones, we reach for solutions that feel rigorous and look impressive: standardized protocols, logic models with clean causal arrows, best practices imported from somewhere else and applied wholesale to a context they were not designed for.
These tools are not useless. But they carry an assumption; that the system will behave the way we expect it to, that the intervention will produce the predicted outcome, and that the variables we have identified are the ones that matter most. In a complex system, that assumption is almost always at least partially wrong.
The result is initiatives that produce outputs without producing change. Programs that work in the pilot and disappoint at scale. Interventions that address the visible symptom while the underlying conditions quietly shift. And, eventually, a kind of institutional exhaustion, the accumulated weight of having tried so many things and moved so little.
What Complexity Actually Requires
Working effectively in complexity does not mean abandoning rigor. It means applying a different kind of rigor, one that starts with observation rather than prescription.
It means paying attention to what the system is actually doing, not what your model says it should be doing. It means building feedback loops that tell you quickly when something is not working, so you can adjust before the investment grows too large to reconsider. It means distributing decision-making closer to the ground, where the people with the most accurate picture of what is happening actually are. And it means holding your solutions loosely, as hypotheses to be tested rather than answers to be implemented.
It also means tolerating something that institutional culture often does not reward: uncertainty. In complex systems, you rarely know in advance what will work. You learn by doing, by watching, by adjusting. The leaders who navigate complexity best are not the ones with the most confident plans. They are the ones with the most genuine curiosity about what is actually happening and the most willingness to change course when reality diverges from the plan.
The Honest Reckoning
Most of the problems public servants are working on are complex. Poverty. Trauma. Systemic inequity. Community health. Public safety. These are not puzzles waiting to be solved. They are conditions to be navigated, improved and tended over time by people who are willing to stay in relationship with the problem long enough to understand it, rather than implement a solution and move on.
That is harder than it sounds. It requires a different relationship with outcomes, with accountability, and with what it means to make progress. It requires organizations that are built to learn, not just to deliver.
Complexity is not going away. The communities we serve are not going to become simpler. The question is whether we are willing to build the kind of organizations and the kind of leadership that complexity actually demands.
Pretending otherwise is the one thing we cannot afford to keep doing.
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.