When Policy Meets Reality: Why Implementation Should Shape Policy

A policy can be perfectly designed and still fail at the point where it matters most: delivery.

A policy document does not experience a crowded service centre. It does not answer a confused citizen. It does not discover that a supposedly simple digital process is difficult to navigate. It does not have to improvise when technology fails, resources are limited, or an instruction that seemed clear in a meeting is interpreted differently on the ground.

Public servants do.

This is why one of the most underused sources of policy intelligence may already exist within government: the people responsible for implementing policy every day.

Policymakers bring research, data and strategic perspective. Experts bring technical knowledge. Frontline public servants bring something equally important: an understanding of how policies interact with real people, real systems and real constraints.

If we want policies that work beyond the page, that knowledge needs to enter the process before decisions are finalised.

1. The Gap Between Design and Delivery

There is often a significant difference between a policy as it is imagined and a policy as it is experienced.

Consider a government service being moved online. On paper, the reform may appear straightforward: applicants submit information digitally, upload documents, make payments electronically, and receive faster decisions.

In practice, different questions emerge.

What happens to someone with limited digital literacy? What if the payment platform fails? What happens when an applicant submits the wrong document? How does an officer handle a case that does not fit the digital workflow? Where does a citizen turn when something goes wrong?

These are not minor operational details. They can determine whether the reform achieves its objective.

The lesson is straightforward: policy design needs an understanding of the environment in which the policy will operate.

2. Frontline Experience Is a Form of Evidence

Governments rightly value statistics, research and expert analysis. But not every useful insight is contained in a report.

Professional experience can reveal patterns that formal data may not immediately explain.

An officer who regularly interacts with citizens may understand why a requirement is repeatedly misunderstood, where applications tend to stall, or which administrative step creates unnecessary delays. They may also know which informal solutions are already helping staff manage these problems.

This does not mean replacing research with anecdotes. It means bringing different forms of knowledge together.

Data can show what is happening. Research can help explain why. Operational experience can reveal what happens when a policy encounters real-world conditions.

The strongest decisions make use of all three.

3. A Practical Example: Learning From Digital Immigration Reform

Digital transformation in immigration services provides a useful illustration.

When governments introduce digital visa or immigration services, the objective is usually straightforward: make processes more efficient, accessible, transparent and secure.

But moving a service online involves more than developing a platform.

The people responsible for processing applications encounter the practical questions that determine whether the reform works as intended. They see recurring application errors, understand where applicants struggle, identify process bottlenecks, and discover where additional guidance or system improvements may be required.

For example, Nigeria’s move towards electronic visa services demonstrates why digital reform needs both technology and operational insight. A digital platform may streamline applications, but successful implementation also depends on clear requirements, trained personnel, effective verification processes, user support, and the ability to respond when real-world cases do not fit neatly into a predefined workflow.

The broader lesson extends well beyond immigration:

Digital transformation should not simply digitise an existing process. It should use the experience of those delivering the service to determine how the process itself can be improved.

This is where frontline knowledge becomes particularly valuable.

4. Bring Implementers In Before the Policy Is Finalised

Too often, consultation happens after the major decisions have already been made.

By then, the policy direction may be settled, documents drafted, systems commissioned and implementation timelines established. Asking frontline staff for their views at that point can turn consultation into little more than validation.

A better approach is to involve implementers while the policy is still flexible.

Before finalising a policy, frontline representatives could be asked five practical questions:

Is it practical?
Can it be delivered within actual working conditions?

Is it clear?
Will different officers interpret the requirements consistently?

Is it accessible?
Can the people who need the service understand and use it?

Is it resourced?
Do staff have the technology, training, time and tools required?

What could go wrong?
What unintended consequences should policymakers anticipate?

These questions are simple, but they can expose weaknesses before they become expensive implementation problems.

5. Test Before You Scale

Not every policy needs to be launched everywhere at once.

Where appropriate, governments can test new approaches through pilots before scaling them.

A pilot allows policymakers to observe what actually happens under real conditions. It can reveal unexpected costs, technical problems, user behaviour, staffing pressures and unintended consequences.

Most importantly, it creates an opportunity to improve the policy before those problems are multiplied across an entire system.

The principle is simple:

Design → Test → Learn → Adjust → Scale

This approach also changes the culture around policy failure. Discovering a weakness during a controlled pilot is not necessarily failure. It may be evidence that the policy is being responsibly tested.

6. Turn Feedback Into a System

One consultation is not enough.

Once a policy is implemented, the institution should continue to collect information from those delivering and receiving the service.

This can be done without creating elaborate bureaucracy. A simple feedback mechanism can allow frontline teams to record:

• recurring implementation problems;
• frequently misunderstood requirements;
• suggestions for process improvement;
• technology or resource constraints; and
• unintended effects on citizens.

The important thing is that feedback must lead somewhere.

If public servants repeatedly report the same problem but nothing changes, they eventually stop reporting it.

A useful feedback system therefore needs three components:

Listen. Act. Communicate.

Listen to the problem. Act where change is justified. Communicate what was done and why.

That closes the loop between policy design and implementation.

7. Create Space for Constructive Challenge

There is also a cultural dimension to this.

In hierarchical institutions, questioning an established process can sometimes be interpreted as resistance. Yet constructive challenge is often how organisations discover that a policy is producing an unintended result.

A public servant who says, “This process is creating a problem,” may not be challenging authority. They may be protecting the policy’s intended objective.

Leaders can encourage this by distinguishing between resistance to change and responsible professional feedback.

The aim is not to create a culture where every policy is endlessly debated. It is to ensure that useful information can move upward before a manageable problem becomes an institutional failure.

8. Make Implementation Part of Policy Design

Ultimately, the biggest shift is conceptual.

Implementation should not be treated as the stage that begins after policy design is complete. It should be part of policy design itself.

When developing a policy, policymakers should ask:

Who will deliver this?

What will the process look like on an ordinary working day?

What will citizens experience?

What capabilities will staff require?

Which systems and institutions will need to work together?

What could prevent the intended outcome?

These questions force policymakers to move beyond the document and think about delivery.

A policy is not successful because it was approved. It is successful when it produces the outcome it was designed to achieve.

Conclusion: Bring Reality Into the Room

Governments do not lack expertise. They have policymakers, lawyers, economists, researchers, technologists, administrators and frontline professionals, each seeing public problems from a different perspective.

The challenge is connecting those perspectives early enough to influence decisions.

Frontline public servants should not replace policymakers or technical experts. Their views should not automatically determine policy choices. But their operational knowledge should be treated as a legitimate and valuable input into policy design.

The next time a policy is being designed, perhaps the question should not only be:

“Is this a good policy?”

It should also be:

“What will this look like on the ground, and have we asked the people who will make it happen?”

Because the distance between a good policy and a successful policy is often found in implementation.

And sometimes, the people who know how to shorten that distance are already inside the institution.

A Call to Action

The next policy your institution develops, bring at least one person who will implement it into the room before the design is finalised.

Ask them what could work, what could fail, what citizens might experience, and what resources implementation would require. Then create a simple mechanism to test those insights before scaling the policy.

For public servants, this can start with one practical commitment: do not wait for implementation to tell you whether your policy works. Ask the people closest to implementation before you launch it.

Good policy does not always require bigger budgets or more complicated reforms. Sometimes, it begins by listening to the right people early enough.

About the Author

Emmanuella Agumage Iwagoh is a Superintendent of Immigration - a public servant with over a decade of experience in migration governance, policy analysis, and institutional performance management. Her work focuses on strengthening public sector effectiveness through evidence-based policymaking, collaboration, innovation, and improved service delivery.