With an issue this controversial, which side should I take?

The gap between policy ideals and practical action is nothing new. But whenever someone brings it up again, the comments section inevitably splits into two camps: one thinks it’s the same old story—no matter how loudly you proclaim your ideals, if they never become reality, they’re just castles in the air. The other argues that without ideals to lead the way, action is like a headless fly: you need a blueprint before you can draw up construction plans. Beneath all the back-and-forth, though, lies a more fundamental question: What standards should we use to judge how well a policy is carried through from words to action?

The debate: Are principles more important, or actions?

What makes this debate so misleading is that it forces you to choose between two things that are both right. It’s like asking someone whether breathing or a heartbeat is more important. Principles provide direction and legitimacy; actions deliver results and feedback. Without either, policy can’t get very far. But real-world arguments are rarely so mild. Some people see the same keywords appearing again and again in policy documents and immediately think, “Here we go again—more empty promises.” Others see policies warped and distorted during implementation at the grassroots level and immediately blame “unclear top-level design.” Both sides have their own examples and evidence to support their views, so the debate becomes a matter of taking sides and talking past each other.

What’s really worth unpacking isn’t whether principles or actions matter more, but where the chain that turns principles into action is getting stuck.

Laying out the arguments: Three hurdles in the chain of implementation

The first hurdle is translation. Policy principles are usually highly condensed: a few words may stand for an entire set of priorities and resource-allocation rules. But at the implementation level, they need to be translated into concrete actions that can be carried out, assessed, and held accountable. When people take shortcuts in this translation, two extremes can emerge. One is mechanical copying: passing the principle down unchanged, leaving grassroots workers unsure what to do. The other is overinterpretation: piling on requirements at every level and turning a gentle policy direction into a rigid target. That’s how actions get distorted.

The second hurdle is incentives. Principles are put into practice by people, and people’s behavior is shaped by the incentives around them. If the assessment system focuses only on short-term numbers, implementers will naturally choose actions that produce quick results with little risk—even if those actions don’t align with the long-term direction of the principle. Conversely, if the incentive structure allows room for trial and error and takes long-term outcomes into account, implementers will behave differently. Unless this hurdle is cleared, principles and actions will always be separated by a rubber wall: things may look like they’re moving, but nothing is really getting through.

The third hurdle is feedback. Policy implementation isn’t a one-off event; it’s an ongoing process of adjustment. A principle may be clear at the central level, but local authorities may face entirely different constraints. Without a smooth feedback mechanism that sends accurate information from the implementation level back to decision-makers, principles will become increasingly detached from reality, while actions become increasingly reactive. Feedback isn’t about finding fault; it’s a necessary design feature that keeps the chain of implementation flexible.

My position: Don’t side with principles or actions—side with the mechanism that connects them

If I had to choose a side in this debate, I’d choose the mechanism that connects principles to action. Neither principles nor actions are lacking; what’s missing is the system that links the two. That system includes clear rules for translating principles into practice, a sensible incentive structure, and effective channels for feedback. Without these, even the best principles can be implemented in ways that bear no resemblance to their intent, and even the most diligent actions can head in the wrong direction.

Some might say this is too middle-of-the-road and amounts to saying nothing. But the reality is that most policy failures don’t happen because the principles were wrong or people failed to act. They happen because the mechanism for putting principles into practice broke down. When a policy principle is introduced, if implementers don’t know how to turn it into everyday actions, if they receive no positive feedback after acting, or if they have no way to report problems, then that principle is destined to remain on paper. Conversely, when the mechanism works, even if the principle itself needs adjusting, implementation can generate the information needed to make corrections.

So I don’t side with the principles camp or the action camp. I stand in the middle ground where principles and actions can calibrate each other. It may not be conspicuous, but it determines the real distance between policy on paper and policy on the ground.

Acknowledging what the opposing sides get right

Of course, siding with the mechanism that connects principles to action doesn’t mean dismissing the concerns of the other two camps. The principles camp is right to remind us that action without direction is dangerous. Many policy implementations that once seemed efficient ultimately caused problems precisely because they had discarded the constraints imposed by principles from the outset. The action camp is right to insist on results and reject the use of “sound principles” to cover up “poor implementation.” Both reminders are necessary. If the mechanism for putting principles into practice is detached from the guidance of principles and the test of action, it too can become another exercise in going through the motions.

A more honest way to put it is that the mechanism for putting principles into practice isn’t a one-time fix. It performs differently at different stages, in different fields, and at different levels. In some areas, the process works smoothly; in others, it’s completely jammed. Recognizing these differences is more meaningful than choosing sides.

Discussion

In your industry or a field you’ve observed, have you seen a policy principle translate into action especially smoothly—or especially awkwardly? Which link do you think is getting stuck: translation, incentives, or feedback? Share your observations in the comments. No slogans—just specific examples.