Policy Implementation Analysis
- Introduced by
- Jeffrey Pressman & Aaron Wildavsky
- Year
- 1973
- Type
- Process-tracing policy analysis
- Family
- Implementation studies
What does it do?
Policy implementation analysis studies what happens between the moment a policy is decided and the moment it reaches its intended effect, asking why outcomes so often fall short of stated objectives.
The field was founded by Jeffrey Pressman and Aaron Wildavsky's 1973 study of a federal employment program in Oakland, which showed how a long chain of required agreements and clearances steadily eroded great expectations. The method traces the implementation chain — the actors, decision points and conditions through which a policy must pass — to locate where and why it succeeds or fails. Its central object is the implementation gap between policy as legislated and policy as delivered.
The intuition behind the method
Imagine a relay race where a baton must pass through dozens of hands before crossing the finish line, and every runner has the right to slow down, change direction or refuse to run. Even if each runner cooperates ninety percent of the time, the probability that the baton survives a long chain of independent handoffs is small. Pressman and Wildavsky showed exactly this: a program that everyone agreed on still failed because it required so many separate approvals that the joint probability of success collapsed. Policy implementation analysis is the study of that relay — counting the handoffs, finding where the baton gets dropped, and explaining why.
History
Implementation studies were inaugurated by Jeffrey Pressman and Aaron Wildavsky's 1973 book Implementation, whose famously long subtitle described how great expectations in Washington were dashed in Oakland through a federal economic-development program. The book launched a wave of research, and a top-down tradition was formalised by Daniel Mazmanian and Paul Sabatier in their 1983 Implementation and Public Policy, which specified the conditions for effective implementation. A rival bottom-up tradition associated with Michael Lipsky, Benny Hjern and Richard Elmore stressed frontline discretion and backward mapping. Later scholars such as Richard Matland and Søren Winter sought to synthesise the two and to incorporate governance and network perspectives.
When to use it
Use policy implementation analysis when a policy has been adopted but is producing disappointing or uneven results and you need to understand where in the delivery system it is breaking down. It suits multi-level programs that pass through several organisations, intergovernmental schemes, regulatory mandates and any reform whose success depends on cooperation across many actors. The top-down variant assumes identifiable objectives and a traceable chain of authority; it is less suited where goals are genuinely contested, where delivery is highly decentralised and discretionary, or where the relevant action happens bottom-up at the frontline. In those cases it should be combined with street-level and bottom-up perspectives. It is not a tool for estimating whether a policy works in principle, but for explaining why an adopted policy does or does not work in practice.
Limitations and considerations
- The classic top-down version assumes clear, consistent objectives that many real policies lack, limiting where it applies cleanly.
- It can underweight the legitimate discretion and local adaptation that bottom-up scholars show are often essential to delivery.
- Reconstructing long implementation chains is data-intensive and depends on access to documents and candid interviews.
- Attributing the implementation gap to specific causes is interpretive, and rival explanations are often hard to rule out definitively.
Source conditions do not replace independent scientific review or validation by an analysis engine.
Strengths
- Locates the precise points in a delivery system where policy stalls, turning a vague sense of failure into actionable diagnosis.
- The multiplicative logic of decision points provides a powerful, intuitive explanation for why long implementation chains routinely underperform.
- Connects frontline outcomes to statutory design and political conditions, bridging legislative intent and administrative reality.
- Generalises across sectors and levels of government, offering a common framework for analysing intergovernmental and contracted delivery.
Applications
- Analysing why federally funded programs delivered through state and local agencies fail to reach intended beneficiaries.
- Tracing the implementation of environmental and regulatory mandates across multiple agencies and jurisdictions.
- Examining health-system reforms whose success depends on coordinated action by ministries, providers and frontline staff.
- Evaluating education reforms that must pass from national policy through districts and schools to classrooms.
- Studying the delivery of development programs by donors, national governments and local implementers across long aid chains.
How it works
How it works
The analyst first establishes what the policy was actually meant to achieve, distinguishing formal statutory goals from the often vaguer or conflicting intentions of the actors who designed it. Clear, consistent and measurable objectives are treated as a precondition for coherent implementation; ambiguous or contradictory goals are themselves flagged as a likely source of later failure. This step provides the benchmark against which delivery will be judged.
The analyst reconstructs the chain of organisations and individuals through which the policy must travel from the deciding authority down to frontline delivery and the target population. Each link — a ministry, an agency, a contractor, a local office, a street-level worker — is identified along with the resources and authority it controls. The length and complexity of this chain is itself diagnostic, since each additional link multiplies the opportunities for delay, distortion or veto.
Within the chain, the analyst pinpoints the decision and clearance points where an actor's agreement is required for the policy to proceed. Pressman and Wildavsky's key insight was that these points compound multiplicatively: many separate approvals, each individually likely, can jointly become improbable. Mapping these points and the actors who hold them locates the chokeholds where implementation most often stalls or is renegotiated.
Drawing on the top-down tradition of Mazmanian and Sabatier, the analyst examines the factors that condition implementation: the tractability of the problem, the statute's ability to structure implementation through clear objectives and adequate resources, and non-statutory variables such as political support, socio-economic conditions and the commitment of implementing officials. These factors explain why a well-mapped chain performs well or badly and connect frontline behaviour to the broader policy environment.
Finally, the analyst synthesises the evidence into an explanation of the implementation gap: the difference between intended and actual outcomes, and the specific mechanisms — veto points, resource shortfalls, goal ambiguity, weak commitment, frontline adaptation — responsible for it. This diagnosis supports recommendations to shorten chains, clarify objectives, align incentives or strengthen capacity, closing the loop from analysis to policy redesign.
Common pitfalls
- Assuming the policy had clear objectives when in fact goals were ambiguous or conflicting, so the analysis measures against a phantom benchmark.
- Counting organisational links while ignoring the discretion exercised by frontline workers, which can rescue or wreck implementation regardless of structure.
- Treating implementation as a one-shot delivery rather than an ongoing process of renegotiation and adaptation among actors.
- Recommending more central control as a reflex, when the real fix may be clarifying goals, adding resources or empowering local adaptation.
Frequently asked questions
What is the difference between top-down and bottom-up implementation analysis?
Top-down analysis starts from the policy decision and traces authority downward, asking whether implementers complied and why outcomes deviated from statutory goals; Mazmanian and Sabatier exemplify it. Bottom-up analysis starts from the frontline and the target population, mapping the network of actors actually solving the problem and treating local discretion as central, as in Lipsky's street-level work. The two are complementary, and synthesis frameworks combine the clarity of top-down goals with the realism of bottom-up delivery.
Why do long implementation chains fail even when everyone agrees?
Because each required clearance is a separate decision that can be delayed, blocked or renegotiated, and the probability that the whole sequence succeeds is roughly the product of the individual probabilities. Pressman and Wildavsky showed that a program supported by all parties still faltered because it needed dozens of independent agreements, and the joint probability of completing them on schedule was low. Reducing the number of decision points, or building in slack, is therefore a recurring practical recommendation.
Is the implementation gap always a sign of failure?
Not necessarily. Some divergence between policy as written and policy as delivered reflects sensible local adaptation to conditions the central designers could not foresee, which bottom-up scholars regard as legitimate and even desirable. The analytic task is to distinguish productive adaptation from breakdown caused by resource shortfalls, weak commitment or veto points. A good implementation analysis judges the gap against the policy's underlying purpose rather than against literal compliance alone.
Related methods
Sources
Pressman, J. L., & Wildavsky, A. (1973). Implementation: How Great Expectations in Washington Are Dashed in Oakland. Berkeley: University of California Press.
ISBN: 9780520053311Copied.Mazmanian, D. A., & Sabatier, P. A. (1983). Implementation and Public Policy. Glenview, IL: Scott, Foresman.
ISBN: 9780819133663Copied.