Matching Each Policy Proposal to the Problem It Claims to Solve

Start With the Stated Goal, Written Plainly

Before examining any proposal, write its goal in one plain sentence. Avoid adjectives that make the goal sound self-evidently good. Instead of "restore fairness to the economy," a clearer version might be "reduce the share of household income spent on rent in the three largest cities." A measurable target makes the rest of the analysis possible, because you can later ask whether a given tool would move that specific number.

Notice whether the proposal names a target at all. Some plans state a goal and then specify no measure of success. That is not automatically disqualifying, but it means you will have to infer what success would look like, and different readers may infer different things. Recording that gap is itself useful information.

Identify the Mechanism Each Tool Relies On

A policy tool works through a mechanism, a chain of cause and effect connecting the government action to the outcome. A tax changes the price of an activity. A subsidy changes who can afford it. A regulation sets a rule that must be followed. A new agency adds capacity to enforce or administer something. For each tool in a proposal, write down the mechanism in a single sentence: "This tool works by making X more expensive, which should reduce Y."

Mechanisms are where proposals become testable. A proposal may promise that a new program will expand access, but if its mechanism depends on private providers choosing to enter a market that currently lacks them, the reader should ask what would make those providers participate. The question is not whether the mechanism is good or bad, but whether it plausibly connects the tool to the goal.

Check the Fit Between Tool and Goal

Now compare each mechanism against the goal. Three common mismatches appear repeatedly. The first is a tool aimed at a symptom rather than the cause: subsidizing a behavior that a deeper factor drives. The second is a tool whose effect operates on a different population than the one the goal describes, such as a measure meant to help small businesses that mostly benefits large firms because of how eligibility is defined. The third is a tool that requires conditions the proposal does not secure, such as a program that depends on staffing or data systems the plan never funds or describes.

A simple practice helps here. Ask, for each tool, whether its mechanism would change the measurable target you wrote down earlier, in which direction, and roughly how large the change might be. If the honest answer is that you cannot tell, that uncertainty belongs in your comparison, not hidden beneath enthusiasm for the goal.

A Side-by-Side Checklist for Comparing Two Proposals

When placing two proposals next to each other, use the same questions for both so the comparison stays fair. First, do both state the same goal, or have they quietly redefined it? A plan that aims to "improve public transit" may be measuring ridership in one case and coverage area in another, and the two cannot be compared directly.

Second, what is the primary mechanism of each tool, and what does it require from people or institutions outside government? Third, who is affected most directly, and does the proposal say so? Fourth, what evidence does the proposal offer that its mechanism works, and is that evidence drawn from comparable settings? Fifth, what does each plan leave unaddressed? Every proposal omits something, and the omissions often reveal priorities as clearly as the inclusions do.

Finally, write a short summary for each plan in the form: "If this works as designed, it should change the target by about this much, through this mechanism, with these conditions, and it is least certain about these points." Summaries written this way make disagreements specific. You may still prefer one plan, but you will know why, and you will be able to say what evidence would change your mind.