Beyond Deliverables: Engineering Conditions for Change

Governments, like most large organizations, take pride in being outcome-driven. We set goals, align teams, measure progress, and deliver results. And rightly so - outcomes matter. But in a complex world, where cause and effect are rarely linear and solutions rarely permanent, a focus on “engineering” outcomes often isn’t enough on its own.

Despite our best efforts, outcomes drift, they decay, or they don’t emerge at all. We push harder - add more reporting, more plans, more pressure and effort - and still, they don’t stick.

The problem isn’t what we’re aiming for, but the conditions we are aiming from.

🧲 The Hidden Force Beneath Outcomes

Conditions and outcomes are like magnets.

If the polarities are aligned, they snap into place - no force required. If misaligned, you can still force it to stick, but only by holding it there with effort. The moment you stop, it shoots apart.

Something similar happens when we try to “deliver” outcomes without attending to the system conditions that support them. Outcomes that emerge naturally from supporting conditions are stable and self-sustaining. Outcomes that are forced into existence against the grain of the system are brittle and short-lived.

This is why deliberate conditions engineering is so important: creating the conditions that make the desired outcomes most likely.

🎭 Conditions Engineering and Outcomes Engineering

Outcomes engineering is the familiar process of defining what we want to achieve: define the goal, plan backwards, push forward.

Conditions engineering is the less visible craft of shaping the environment in which outcomes emerge. It’s about tending to the systems, drivers, cultures, and capacities that help good things take root, grow, and sustain.

There is a growing body of evidence and practice that supports this, rooted in complexity science and backed by validated tools and frameworks. Approaches like Outcome Mapping, Human Learning Systems, Collective Impact, and Developmental Evaluation all reflect this shift. They are designed not to control outcomes, but to cultivate the conditions that make progress possible.

In short:

• Outcomes give us direction.

• Conditions give us traction.

You can force a desired outcome for a while. But unless the system conditions “want” that outcome, it won’t last.

🔁 The Dynamic Interplay

These aren’t rival approaches. The real leadership craft is in working the interplay between them:

• Use outcomes to set a compass and align collective effort.

• Use conditions to shape the terrain and make progress sustainable.

• Let outcomes act as signals - if they’re drifting, it may be time to adjust the conditions, or even reconsider the outcomes themselves.

Much of this work is structural and systemic, but also deeply human. For change to happen at scale, we need people to be at their best, and systems to be at their best. Conditions engineering includes all the work of building environments where both can thrive.

🌳 Why It Matters for Public Servants and Leaders

In a world of polycrisis, complexity, and unpredictability, mastering the dynamic between conditions and outcomes isn’t just helpful - it’s becoming a core competency of public leadership.

The best leaders today:

• Know how to identify and push toward outcomes.

• Know how to understand and cultivate optimal conditions.

• And crucially, know that these aren't either-or choices, but tools in continuous dialogue.

In complexity, the role of leadership is not only to set direction - but to shape the conditions for others to thrive.

🔄 Deeper Public Craft

We don’t always control the outcomes. But we can cultivate systems that attract the outcomes that matter - where wellbeing, inclusion, and justice are not just delivered, but drawn in by the way the system is built.

So, the next time you’re struggling to deliver on a result, pause. Step back. And ask yourself:

• What’s the magnetic field around this work?

• What would it take to flip the polarity?