Navigating the gap: why policy programmes succeed or falter after legislation
In this article, I explore why programmes designed to implement policy succeed or falter, and what it takes to bridge the gap between statutory intent and lived change. From procurement and performance incentives to behavioural insight and cultural fit, I reflect on the choreography of implementation and how we can do it better.
Once legislation is passed, the real work begins. The passage of an Act is often seen as the finish line, when in reality it’s the starting gate. What follows—the design and implementation of programmes that bring the law to life—is where complexity unfolds. And it’s here, in the space between statutory intent and lived experience, that success or failure is quietly shaped.
From statute to strategy
When an Act becomes law, it carries expectations—some explicit, others implied. Translating those expectations into operational programmes requires interpretation, design, and strategic foresight. This phase begins with a deceptively simple question: “What does this mean in practice?” The answer involves unpacking legislative language, clarifying scope, and identifying the systems, people, and behaviours that must shift.
Designing with depth
Programme design is not just technical—it’s relational. It calls for robust research into both the policy domain and the social contexts it touches. What do people believe about this issue? How do they act? What incentives or barriers shape their choices?
Ambiguity in goals or delivery mechanisms can quietly erode momentum. If the “how” is left vague, implementers fill in the gaps—sometimes creatively, sometimes inconsistently. And where there’s conflict—between agencies, sectors, or worldviews—design becomes negotiation.
Implementation: the art of making things work
Implementation is where the abstract becomes tangible. It’s where frontline teams interpret policy, systems are built or adapted, and citizens encounter change. Several factors shape this phase:
- Resourcing and capability: Are the right people in place, with the right tools and support?
- Discretion and interpretation: How do implementers understand their role? What latitude do they have?
- Leadership and governance: Is there clarity of direction, and are feedback loops active?
- Cultural and contextual fit: Does the programme resonate with local values, practices, and histories?
One often-overlooked element is procurement. When new systems are needed to deliver services or monitor performance, procurement becomes a critical hinge point. Translating policy intent into functional specifications—often under time pressure and within rigid frameworks—is no small feat. Poorly scoped systems can be technically sound but practically unusable, especially if end users aren’t involved in design.
Beyond systems, implementation also hinges on how incentives and performance measures are designed. These metrics are meant to guide behaviour, but they can easily distort it. A focus on throughput might discourage quality engagement; a narrow compliance metric might lead to box-ticking. Designing incentives requires nuance: measuring what matters, not just what’s easy to count.
Behavioural insight: the human element
At the heart of every policy programme is a behavioural shift. Whether it’s about safer driving, healthier eating, or fairer hiring, the goal is to influence choices. Programmes that succeed often embed behavioural insight from the start. They ask: What matters to people here? What do they fear, hope for, or resist?
This is where incentives and measurement systems intersect with psychology. If people feel coerced or surveilled, they disengage. If they feel respected and supported, they’re more likely to participate. Behavioural design isn’t just about nudges—it’s about relationships.
Learning as we go
No programme lands perfectly. That’s not a flaw—it’s a feature of complex systems. What matters is whether we’re listening. Are we gathering feedback from those delivering and experiencing the programme? Are we willing to adapt?
Continuous learning isn’t just about evaluation reports—it’s about cultivating a mindset of responsiveness. Success is rarely linear. It’s iterative, relational, and often surprising.
References
- Matland (1995), Ambiguity-Conflict Model
- Fixsen et al. (2005), Implementation Research
- Moynihan (2008), Performance Management
- Hood (2006), Gaming in Targetworld
- Behavioural Insights Team (2014), EAST Framework
- NZ Government Procurement Guidelines
- Treasury NZ (2021), Living Standards Framework