Common Sense Policy Isn’t Simple
Updated: 16 hours ago
What I learned about how we avoid the hard questions
I have worked in public policy for over 20 years. For about half of that time, I naively believed policy was created and implemented based on what the public needed.
For the rest of it, I felt like all I did was fight, or strategize, to get key files the attention they deserved. Many of them had simple, fast solutions that could have been handled staff to staff. A known gap in existing legislation, for example, that everyone agreed on and no one moved to fix.
The problem usually isn't that we don't know what's wrong. Most of the time, we know exactly what's wrong. The problem is what we do next.
Another committee, another report
What I saw again and again. An issue comes up. Everyone in the room agrees it's real. People on the front lines have been describing it for years. Maybe there's already a report on it, or two.
So we strike a committee.
The committee forms a working group. The working group consults. The consultation produces a report. The report makes recommendations, many of which look a lot like the last report's. Then the recommendations go to another table for review.
Two years later, the issue is still there. But now it's been "addressed."
I don't say this to dismiss the people on those committees. Many of them care deeply and work hard. But somewhere along the way, studying a problem started to count as doing something about it. It feels like progress, and it's easy to announce. And it puts off the moment when someone has to make a decision.
Knowing isn't the same as funding
The second pattern is harder to talk about. Sometimes the issue is understood, the solution is clear, and there's broad agreement on what needs to happen. And then the money doesn't come.
Or it comes, but it's a one-time pilot when the need is ongoing. Or it's attached to a program that doesn't quite fit the problem. So the people delivering it spend their time bending the work to match the funding instead of the need.
When that happens, the gap doesn't close. It just gets a new name.
If we know the issue and we aren't funding the fix, that's a choice. Common sense says we should be honest about it.
Adding layers instead of asking hard questions
The third pattern ties the other two together. When something isn't working, the instinct is to add: a new oversight body, a new reporting requirement, a new coordinating role, a new strategy sitting on top of the old one.
Adding feels responsible. It shows action. But each layer is something else for people to manage, report to and work around. Very rarely does anything come off the table to make room.
The harder questions get skipped:
Why didn't the last approach work?
What should we stop doing?
Who actually owns this problem?
Are we willing to fund what we already know works?
Those questions are uncomfortable because the answers often mean admitting something didn't work or making a trade-off someone won't like. But they're where real change starts.
What common sense would look like
I don't think common-sense policy means simple answers. I think it means being willing to:
Act on what we already know instead of studying it again
Put money behind the problems we've agreed are real
Take something away or reassess before adding something new
Measure whether things got better for people, not whether a report was produced
Metrics of success should be based on the opinions of those impacted by it and/or work within
Comments