Systems Thinking as a Catalyst for Social Change: The Iowa Education Story
Book: Systems Thinking for Social Change Author: David Peter Stroh ISBN: 978-1-60358-580-4
Chapter 2 opens with a real story from Iowa. Two organizations that should have been working together were accidentally making each other’s lives harder. And that pattern? It shows up everywhere.
The Iowa Education Story
In 2011, the Iowa Department of Education (IDE) and the state’s Area Education Agencies (AEAs) sat down together. Both groups were responsible for K-12 education in Iowa. But they had always been funded separately and operated independently.
The problem was getting worse. Budgets were shrinking. Test scores weren’t keeping up with national averages. Iowa’s kids needed better support, and that meant these two organizations had to actually work together.
Easier said than done. Most partnerships like this fail. But this one worked.
The initiative, called Collaborating for Iowa’s Kids, became a real success story. Within four years it grew to include 80-100 participants. Both organizations started operating with shared purpose, shared values, and common goals. They met monthly with local school districts, reviewed shared data, and launched an early literacy initiative across the state.
So what made the difference?
Accidental Adversaries
Early on, the leaders of both groups used systems thinking to understand why collaboration had been so hard despite everyone’s good intentions.
The pattern they uncovered is called “Accidental Adversaries.” It’s a systems archetype. Here’s the basic idea: two groups are designed to be part of the same system and help each other. But over time, each group focuses only on its own responsibilities. In doing so, each one makes life harder for the other. Neither group means to. It just happens.
In Iowa, it played out like this. The IDE kept rolling out new programs to provide guidance across the state. But those programs overwhelmed the AEAs and disrupted their ability to manage their own resources. So the AEAs started customizing or ignoring the IDE’s programs. Which made the IDE’s job harder. Which led them to create even more programs. And round and round it went.
When both groups saw this pattern laid out clearly, something clicked.
Mark Draper, director of special education for the Green Hills AEA, said it was “the most concrete and useful conversation I’ve had on the relationship between our two groups in the past 20 years.” Connie Maxson from the Department of Education called it the best conversation she’d had on the topic in seven years.
They agreed on clear roles. IDE would set direction and lead. AEAs would implement. And they brought local school districts into the alignment work too. Instead of trying to fix everything at once, they focused on early literacy first because of its long-term impact on student success.
Four Challenges of Change
The Iowa story highlights something bigger. Systems thinking helps people deal with four common challenges when trying to create lasting change.
1. Motivation. People discover their own role in making problems worse. The IDE saw that rolling out programs without considering AEA needs created a cycle of disengagement. The AEAs saw that customizing everything led IDE to push even more programs. When you see your part in the mess, you actually want to change.
2. Collaboration. People learn how they collectively create the bad results they’re experiencing. In Iowa, both sides realized they were in the same sinking boat. One they built together. Only by working together could they build something better.
3. Focus. Systems thinking helps people pick a few key changes instead of trying to do everything. Iowa’s organizations chose to target early-childhood literacy as their starting point because it had the biggest long-term payoff. This is the opposite of the usual approach where people spread resources thin across too many initiatives and get less done.
4. Continuous learning. Complex social problems are never fully solved. They keep changing. Systems thinking pushes people to accept that knowledge is never complete. Learning beats knowing because it lets you adapt. Iowa put in place a process for assessing progress and adjusting strategies over time.
The key difference between systems thinking and typical approaches? Most methods help people identify a shared vision. Systems thinking goes further. It shows people how they are personally responsible for the current reality. That’s what actually gets people to change their behavior, not just their words.
As Peter Senge put it in The Fifth Discipline: “The building of shared vision lacks a critical underpinning if practiced without systems thinking.”
When to Use Systems Thinking
Stroh uses a great analogy here. Since 1991, Intel used the motto “Intel Inside” to show that its chips powered computers everywhere. Systems thinking works the same way. It powers change within many different frameworks. Stroh calls it “Systems Thinking Inside.”
It’s especially useful when you see these six signs:
- A problem is chronic. It keeps coming back no matter what people try.
- Diverse stakeholders can’t align despite sharing the same goals.
- People optimize their part without understanding their impact on the whole system.
- Short-term efforts backfire. What people do to fix the problem actually makes it worse over time.
- Too many initiatives. People are running a bunch of disconnected projects at the same time.
- Solutions over learning. People push “best practices” instead of engaging in continuous learning.
Systems thinking can also help defuse unintentional conflict between groups, as it did in Iowa. Even in deeper conflicts where people aren’t willing to collaborate directly, systems thinking can help third parties understand the dynamics and find possible ways in.
Collective Impact and Systems Thinking
One of the most popular frameworks for large-scale social change is Collective Impact, introduced by John Kania and Mark Kramer. It brings nonprofits, businesses, government agencies, and the public together to solve complex problems. The model has five conditions for success: a common agenda, shared measurement, mutually reinforcing activities, continuous communication, and backbone support organizations.
It’s a solid framework. But it has gaps. Critics like Paul Schmitz point out three areas where Collective Impact can fall short:
- Leaders tend to tout their own successes instead of being honest about what’s not working.
- Organizations see issues from their own perspective instead of thinking about the whole picture.
- Community members aren’t always engaged as active leaders.
Systems thinking directly addresses the first two problems. Here’s how it strengthens each piece of Collective Impact.
Mutually reinforcing activities. Systems thinking builds trust by showing that everyone is doing their best with what they know. It also builds vulnerability by showing people the negative side effects of their well-meaning actions on others and on themselves. When people see how connected they really are, their actions become genuinely supportive instead of just coordinated on paper.
Common agenda. Systems thinking helps in four ways. It gives people a shared language. It creates a common understanding of why problems persist. It raises the gap between what people say they want and the incentives they have to keep things the same. And it helps stakeholders build a shared theory of change.
That third point is a big deal. Without it, people rally around a nice-sounding vision while quietly protecting the status quo. Acknowledging the benefits of change AND the real reasons it’s hard makes the vision grounded in reality.
Shared measurement. Systems thinking focuses on both qualitative and quantitative data. It looks at progress across different time horizons, watches for unintended consequences, and tracks performance against the theory of change. This protects against a common trap: getting seduced by short-term data that doesn’t reflect long-term results.
Continuous communication. When people take responsibility for their impacts, understand the common agenda, and know how to interpret short-term results in a long-term context, communication gets better naturally. Systems thinking also emphasizes that continuous learning is the foundation of continuous communication.
The Martin Luther King Lesson
There’s a powerful observation in this chapter about Martin Luther King’s “I Have a Dream” speech. About 70% of that speech was devoted to painting a picture of the difficult reality. Only 30% was about the dream itself.
That’s not an accident. Vision becomes real only when people truly believe they can shape their future. And that belief starts with an honest look at where things stand right now, including their own role in creating the current situation. If people don’t see how they contribute to the present, they’ll assume the work is about changing others instead of changing themselves.
Key Takeaways
Systems thinking works as an engine inside other change frameworks. It’s not a competing approach. It’s a power source.
It motivates people by showing them their role in the problem. It builds real collaboration by revealing shared responsibility. It creates focus by directing energy toward high-impact changes. And it supports continuous learning by treating every result as new information, not a final answer.
The Iowa education story proves this isn’t just theory. Two organizations that had been accidentally working against each other for years turned it around. They built shared purpose, aligned their efforts, and started getting results for kids.
That’s the promise of “Systems Thinking Inside.” Not a magic formula. A better way of seeing.