Design the Process, Don't Write the Law

There is a permanent tension in political design between writing a law and building a process that produces laws. Almost all of our attention goes to the first. I think it belongs on the second, and the reason is that laws have a property we consistently underrate: they are static, and the world is not.

The Illustration

The American right to bear arms looked entirely reasonable in the era it was written. A population with muskets, a government with muskets, and a recent memory of what happens when only one side is armed. Whatever you think of the reasoning, it was responsive to the situation.

Look at what it means now. Millions of personal firearms set against a government holding nuclear weapons, armed drones, satellite surveillance, and an army. Whatever function the provision was meant to serve — deterring tyranny by keeping the citizenry a credible counterweight — it cannot serve now. The military asymmetry is total.

The clause did not change. Everything around it did. And that is a failure of legislation as a form, not a failure of the people who wrote that particular sentence. They were solving their problem. They had no way to write a sentence that would keep solving it after the invention of the aircraft.

Anything committed to the books permanently will eventually be obsolete, because culture, technology, and the distribution of power all move and the text does not.

The Alternative, and Its Honest Difficulty

The alternative is to build a process that adjusts laws as conditions change, and to put your design effort there rather than into the content of any particular statute.

I want to be honest that this is not a clean escape. Processes go obsolete too. The electoral college was a process, designed with reasons behind it, and it now produces outcomes nobody would design on purpose. Veto arrangements, committee structures, filibuster rules — all processes, all now doing something other than what they were built for.

Worse, the founders' deepest failure was a process failure rather than a legislative one. They did not foresee industrial capitalism, and therefore did not foresee that concentrated private wealth would come to shape the legislature and the executive from outside. No particular statute could have prevented that. The vulnerability was in the design of the machine.

So process design is not a solved problem, and pretending otherwise would be dishonest.

But it is the more promising direction, for a simple reason: a bad process can in principle notice and correct itself, and a bad law cannot. A law has no mechanism for observing that it has stopped working. A well-designed process has exactly that mechanism as its purpose.

The Second-Order Cost

There is a further problem with a legislature-centred system, and it is the one I find most damaging in ordinary life.

It biases the entire society toward legislative answers. Raise almost any problem in conversation — anything from road safety to loneliness to the behaviour of a particular industry — and within a minute someone will propose a law. That is the reflex. It is what "doing something" has come to mean.

In practice legislation is rarely the best instrument available. Reorganisation usually beats it: changing the structure so that different incentives operate, so that a different culture grows, so that the behaviour you wanted becomes the path of least resistance rather than the prohibited path. That approach is slower to describe, harder to campaign on, and vastly more effective when it works.

We reach for legislation anyway, and the reason is not that we have compared the tools. It is that voting for legislators is the only political strength most people have. We propose laws because passing laws is the one thing our system lets us gesture at. The instrument gets chosen by the shape of the lever we were handed, not by the shape of the problem.