What Donella Meadows Taught Me About Mission‑Driven Systems Work

Most "transformation" efforts fail before they start — because we're pushing on the wrong part of the system.

Over the last few weeks I've been rereading Donella Meadows' Thinking in Systems, and it's reframed how I see mission-driven organizations and the work I do in technology and operations.

The insight that stuck with me:

When you're part of a community committed to health, purpose, or shared values, you feel better about yourself and your choices — even before you've fully acted on that commitment. The value isn't just in what the organization produces. It's in how people feel about participating in it.

That reframing changes almost everything about how I approach the work.

01Symptoms vs. structure

Meadows argues that most of us try to solve problems by pushing on symptoms instead of understanding the system's structure. She points to leverage points — places where a small, well-aimed shift creates outsized change.

The catch: systems have delays. The gap between action and consequence is often what fools us. We push, nothing happens, so we push harder in the same direction — and sometimes double down on exactly the wrong intervention.

You see this in organizations all the time:

• A new tool gets rolled out to "fix" a process that people don't trust.
• More reporting is added to "drive accountability" in a system actually constrained by unclear priorities.
• More policies are layered on top of a culture problem nobody wants to name.

On the surface, it looks like action. Underneath, the structure hasn't changed.

02The trap of pushing harder on process

In my own career I've often stepped into roles where the mandate was to introduce new systems into organizations with deep roots. On paper that usually means: implement tools, modernize workflows, tighten processes, improve visibility.

The temptation is to push hard:

• Roll out the project management tool.
• Standardize the intake form.
• Enforce the new workflow.

Those things matter. But Meadows reminds me that systems resist change not because people are stubborn or "anti-tech." They resist because the current structure is serving a purpose — even if that purpose isn't obvious yet.

03The most useful question I've borrowed from systems thinking

"What is this system actually optimizing for?"

• Sometimes it's optimizing for speed.
• Sometimes for risk avoidance.
• Sometimes for local control, even when that creates inefficiency elsewhere.
• Occasionally, it's optimizing for something nobody has said out loud: preserving an old structure, minimizing discomfort, avoiding a difficult tradeoff.

When you see that clearly, two things happen:

1. You understand why the current behavior makes sense inside the system as it exists today.
2. You can have an honest conversation about whether that's still what you want to optimize for.

That second conversation is far harder than configuring another dashboard. It's also the one that actually matters.

04The hidden layer: belonging

In mission-driven organizations, there's almost always a layer beneath the org chart and the process diagrams: belonging.

People didn't join just to complete tasks. They joined because the mission, the values, or the community meant something to them. It shows up in subtle ways — how they talk about the work, the stories they tell new hires, the energy they bring to small decisions outsiders would miss.

If your "improvement" inadvertently erodes that sense of belonging, you may gain efficiency and lose something more important.

If your change strengthens belonging — through more clarity, more trust, more shared understanding — you've probably hit a real leverage point.

05How my role has shifted

I now think of my work less as "implementing technology" and more as helping systems grow into better versions of themselves without losing what makes them worth belonging to.

In practice, that looks like:

• Listening for a long time before proposing solutions.
• Asking what informal value a process is creating before we streamline or automate it.
• Surfacing what the organization is implicitly optimizing for, then checking it against the stated mission.
• Treating tools and workflows as expressions of a deeper decision — not as ends in themselves.

Meadows gave me language for instincts I'd felt for years: technology and process change land best when they respect the underlying system and the people inside it.

06The metrics problem

It's easy to count tools implemented, processes standardized, dashboards deployed.

It's much harder to measure whether people feel more connected to the mission, more trusted in their roles, and more proud of the work they do.

But if the real stock is that feeling of belonging to something that matters, then that's where the leverage is.

What systems thinking has become for me

Part of the job description now:

1. Listen for what the system is optimizing for.
2. Make it visible.
3. Help leaders decide whether it still aligns with who they want to be.
4. Then let the technology, processes, and metrics follow that decision.