We spend an extraordinary amount of time discussing what government should do.
Raise or lower interest rates. Modernize public transportation. Build more infrastructure. Digitize government services. Reform education. Subsidize agriculture. Clean up our rivers. Introduce new technologies into the financial system.
These are important debates. But increasingly, I find myself interested in a different question.
What happens after the government decides?
A law is passed. An executive order is signed. A department issues a memorandum. Congress appropriates money. A regulator announces a new rule. Government launches a program.
In public conversations, we often treat these moments as accomplishments in themselves. Politicians announce them. Agencies publicize them. Media report them. Supporters defend them, and critics attack them.
Then public attention moves elsewhere.
But from a public-policy perspective, that is precisely when the more interesting story begins.
Between a government decision and the outcome citizens experience lies an entire system: national agencies, local governments, regulators, bureaucracies, businesses, financing institutions, organized groups, communities, and individual citizens. Each interprets the policy, responds to it and sometimes changes it simply through the way it behaves.
This is the distance between policy intention and policy reality.
I have become increasingly interested in that distance while pursuing my doctoral studies in public policy and management. Studying economic policy under Dr. Ramon George Atento has forced me to look beyond the policy announcement and ask what happens between intervention and outcome.
Economics provides an excellent illustration.
When a central bank changes interest rates, nobody seriously assumes that the announcement itself immediately changes the economy. Monetary economists talk about transmission mechanisms: the channels through which a policy decision eventually affects borrowing, investment, consumption, asset prices, expectations, and, ultimately, inflation and economic activity.
The policy must travel.
And as it travels, many things can happen.
Banks may not lend as expected. Businesses may remain reluctant to invest. Consumers may continue spending despite higher rates. Expectations may change. External shocks may overwhelm domestic intervention. The central bank controls its policy instrument, but it does not mechanically control everything that follows.
This raises a question that deserves much greater attention outside monetary policy:
What if we thought about all public policies as having transmission mechanisms?
Consider public transportation modernization. Government may have a perfectly defensible objective: safer vehicles, cleaner technology, more efficient routes and better transportation for commuters.
But declaring that objective does not modernize a single vehicle.
The policy must pass through transport agencies, local governments, financing institutions, operators, cooperatives, drivers and commuters. Operators must be able to finance new vehicles. Banks must consider them creditworthy. Routes must remain economically viable. Regulators must have the capacity to enforce standards. Drivers must see a sustainable livelihood. Commuters must still be able to afford the service.
A failure anywhere along that chain can create a very different outcome from the one envisioned when the policy was designed.
This does not necessarily mean the original policy was wrong.
It may mean its transmission was poorly understood.
The same principle applies to digital government. Putting a government service online may improve efficiency, but only if citizens can access it, agencies can integrate their systems, databases are reliable, employees know how to operate the technology, and procedures actually change rather than simply placing a digital interface over an old bureaucracy.
Digitalization can change the interface without changing the institution behind it.
Infrastructure provides another example. Government can appropriate billions for roads, bridges, flood control, and transportation. But an appropriation is an input, not an outcome. Between the budget and the public benefit lie procurement, engineering standards, contractors, right-of-way issues, national and local coordination, monitoring, maintenance, and accountability.
We therefore need to become much more careful about what we call policy success.
Passing a law is not success.
Appropriating money is not success.
Launching a program is not success.
Even implementing an activity is not necessarily success.
The relevant question is whether the intervention produced the outcome it was intended to produce, for the people it was intended to serve, at a cost society can justify and in a manner that can be sustained.
This distinction becomes even more important when governments look abroad for solutions.
During our discussions about central bank digital currencies, for example, I became interested in China’s experience with the e-CNY. It would be easy to ask whether the Philippines should follow China and accelerate toward a retail Central Bank Digital Currency (CBDC).
But that begins with the solution rather than the problem.
The more useful question is: What Philippine problem are we trying to solve?
If the problem concerns settlement efficiency between financial institutions, the appropriate intervention may be different from one designed to increase financial inclusion. If the concern is payment resilience, that demands another set of capabilities. If existing digital payment systems already solve much of the consumer problem, introducing another technological layer may create complexity without producing proportional public value.
Policy should begin with the problem, not with the attractiveness of the solution.
This is also why importing so-called global best practices deserves caution.
A policy does not travel from one country to another by PDF.
What worked in China, Singapore, South Korea, or Scandinavia emerged from particular institutions, administrative capacities, political arrangements, economic structures and social conditions. We should certainly learn from them. But learning is different from copying.
The relevant question is not simply, “What worked elsewhere?”
It is, “Why did it work there, and do the conditions that made it work exist here?”
This brings us back to institutions.
Public policy is sometimes discussed as though government was a single actor: “government decided,” “government failed,” “government should.”
Government is not one actor.
It is an ecosystem of institutions populated by people with different mandates, incentives, information, and capabilities. Outside government are businesses, civil society organizations, professional groups, communities, and citizens who possess their own information and pursue their own interests.
Policy travels through this ecosystem.
And information travels with it.
Policymakers rarely possess all the information required to anticipate the consequences of their decisions. They depend on bureaucracies, technical experts, regulated industries, affected communities, researchers, and organized stakeholders to understand problems and evaluate alternatives.
That interaction is not peripheral to policymaking. It is part of policymaking itself.
This is particularly interesting to me because much of my professional life has involved communication, stakeholder engagement, and public affairs. I used to see these primarily as activities surrounding policy. Increasingly, I see information exchange itself as part of the institutional machinery through which policy is made and implemented.
Who gets heard matters.
But so does what information reaches government, how credible it is, how competing information is evaluated, and whether institutions can act on what they learn.
That is why the gap between policy intention and policy reality cannot always be blamed simply on “poor implementation.” That phrase has become almost too convenient.
Sometimes the problem began much earlier.
Perhaps policymakers misunderstood the problem. Perhaps affected stakeholders possessed information that never reached decisionmakers. Perhaps incentives were misaligned. Perhaps financing assumptions were unrealistic. Perhaps implementing agencies lacked capacity. Perhaps the policy borrowed an international model without understanding the institutions that made it successful elsewhere.
Implementation failure may actually be design failure revealed later.
This suggests a different way of evaluating government.
Instead of asking only what policies were announced, laws passed, budgets allocated, or programs launched, we should pay much closer attention to the journey from decision to consequence.
What happened after the government decided?
Which institutions carried the policy? Where did information move or fail to move? How did stakeholders respond? Which assumptions survived contact with reality? Where did implementation depart from design? And most importantly, what eventually changed in the lives of the people the policy was supposed to help?
Those questions are less dramatic than policy announcements.
But they may tell us far more about whether government actually works.
Because ultimately, citizens do not experience policy intentions.
They experience policy outcomes.