Before We Start
The implementation gap, named precisely
Policymakers can design a technically sound, well-intentioned policy, but what actually happens when that policy meets the real world can diverge significantly from the original design intent. This divergence is specifically called the "implementation gap" — a genuinely important, distinct stage of the broader policy cycle.
💡 Street-Level Bureaucrats — A Specific, Named Insight From Lipsky
Michael Lipsky's specific contribution: front-line workers implementing policy day to day — teachers, police officers, social workers — exercise genuinely significant discretion in how they apply rules to specific individual cases, meaning implementation ISN'T simply mechanical execution of a predetermined plan; it's itself a form of ongoing policy-making.
Mnemonic
The implementation gap, its causes, and two competing models
Street-Level Bureaucrats
Teachers, police, social workers exercise real discretion
Lipsky's specific insight — front-line implementers genuinely shape policy outcomes through their individual, case-by-case discretionary decisions, not merely execute a fixed, predetermined design.
Causes of Implementation Failure
Unclear mandates, inadequate resources, multiple veto points, principal-agent problems
Several specific, distinct factors can each independently contribute to a genuine gap between policy design and policy reality.
Top-Down Model
Central control
One theoretical perspective on implementation — emphasizes central authorities' ability to direct and control the implementation process from the top.
Bottom-Up Model
Local actors adapt policy to context
The genuinely contrasting perspective — emphasizes how local, front-line actors actively adapt and reshape policy to fit their specific local context, rather than simply executing central directives unchanged.
💊 A useful way to remember the top-down/bottom-up contrast: top-down asks "how well did local implementers follow the central design?" while bottom-up asks "how did local implementers' adaptations actually shape the real policy that citizens experienced?" — these represent genuinely different analytical starting points for evaluating the same underlying implementation process, connecting directly to Lipsky's core insight that implementation itself constitutes a form of policy-making.
⚖️ Applying the Framework — Analyzing an Implementation Gap
A new government program is designed with specific, detailed eligibility criteria intended to be applied uniformly. In practice, front-line caseworkers across different local offices interpret and apply these criteria somewhat differently based on their own professional judgment about each specific case, leading to genuinely different outcomes for similarly-situated individuals in different locations.
Apply Lipsky's Street-Level Bureaucracy Framework
This scenario directly illustrates Lipsky's core insight — the front-line caseworkers are exercising genuine discretion in applying the program's criteria, meaning the program's actual real-world effect (which varies by location and caseworker) diverges from its uniform, on-paper design. This is exactly the "implementation is itself policy-making" dynamic Lipsky identified.
Apply the Bottom-Up Model's Analytical Lens
A bottom-up analysis of this scenario would specifically focus on understanding WHY and HOW individual caseworkers are adapting the criteria differently across contexts — treating this variation as a genuine, informative feature of how the policy actually functions in the real world, rather than simply a "failure" to be eliminated through stricter top-down control. This reflects the bottom-up model's distinct analytical starting point, genuinely different from a purely top-down evaluation focused on measuring deviation from the central design.
📌 Exam Application
Implementation questions test both Lipsky's specific concept and the top-down/bottom-up model distinction:
Lipsky's concept: "What did Lipsky mean by 'street-level bureaucrats,' and what is his key insight about them?" → Front-line workers (teachers, police, social workers) who exercise significant discretion; his key insight is that implementation is itself a form of policy-making, not merely mechanical execution.
Model distinction: "What is the difference between the top-down and bottom-up models of implementation?" → Top-down emphasizes central control and directive-following; bottom-up emphasizes how local actors actively adapt policy to their specific context.
Causes of failure: "Name two specific causes of implementation failure." → Unclear mandates, inadequate resources (multiple veto points and principal-agent problems also correct).
⚠️ The Trap — Treating Implementation as Simple, Mechanical Policy Execution
It's intuitive to think of implementation as simply carrying out a predetermined plan exactly as designed. Lipsky's street-level bureaucracy insight directly challenges this — front-line discretion means implementation genuinely shapes and reshapes the policy's real-world effect, functioning as a form of ongoing policy-making itself.
The safeguard: Remember implementation as an active, discretion-involving process that genuinely shapes policy outcomes, not simply mechanical execution of a fixed, predetermined design.
✓ Quick Self-Test
Answer before checking:
1. What is the "implementation gap"?
2. What did Lipsky mean by "street-level bureaucrats"?
3. What is the top-down model of implementation?
4. What is the bottom-up model of implementation?
Answers:
1. The divergence between a policy's design/intent and its actual, real-world effect.
2. Front-line workers (teachers, police, social workers) who exercise significant discretion when implementing policy.
3. Emphasizes central authorities' ability to direct and control the implementation process.
4. Emphasizes how local, front-line actors actively adapt policy to their specific context.
Next Lesson
REIA — Policy Evaluation Criteria
→