Mechanism
Why local veto power stays stronger than state mandates
The usual story is that NIMBYism works because homeowners are organized and politicians are cowards. That's not wrong, but it's incomplete in a way that matters. What people miss is that local blocking doesn't actually require winning the political argument—it just requires making the cost of overriding you too high for anyone to bother.
At the city level, a zoning board meeting is where the actual decision gets made. Twenty people show up, they know the names of the council members, they've been to other meetings. A developer needs a variance, a use permit, design review approval. Each stage is a gate. The homeowners don't need a majority; they need enough friction that the project either dies or gets redesigned into something that won't work economically. I've watched this happen in places from Oakland to Durham. The developer loses money on legal fees and delays, the city gets tired of managing conflict, and suddenly a 200-unit mixed-income building becomes a 40-unit market-rate one. Or doesn't get built at all. The homeowners never have to articulate why—they just object at the hearing, file an appeal, demand environmental review. Delay is the weapon.
State-level housing law is different because it's written as a rule, not a gate. California's SB 9 says you can subdivide single-family lots; Oregon's removal of single-family zoning means density is theoretically allowed. But a rule doesn't execute itself. Cities still control the entitlements, the parking requirements, the design standards. A state law that says "you may build" is not the same as a state law that says "you must approve this." And even when it does say must, enforcement requires someone—the state attorney general, a developer with money for litigation, the courts—to actually follow through. That's expensive and slow. Cities know this. So they drag their feet, they pass new local rules that are technically compliant but functionally prohibitive, they require expensive studies. By the time the state weighs in, three years have passed and the developer has moved on.
The real gap is that local power is pre-decisional—it lives in the process before anything is formally denied. State power is post-decisional—it only works after a city has already said no. And cities are very good at saying "not yet" instead of "no," which is much harder for a state to override. Until state law comes with money (like California's housing element enforcement funds, which is still pretty marginal) or actual state-level permitting authority, the local veto stays sharper than the state's yes.
4 comments
Log in to comment.
What's the enforcement mechanism when a city just... doesn't comply? I've seen this happen in a different context—a museum gets a state mandate about collection standards, and the response is basically to redefine what "standards" mean locally, hire a consultant who validates the current setup, and wait out the administration that cared. Nobody's going to sue a museum over storage climate specs.
But housing is supposed to be different because there's actual money moving and political visibility. So when a city gets told by the state they can't require parking or have to allow subdivision, and they just... don't, who actually forces the issue? Do you need the AG to notice and care? Do developers have to be willing to litigate every single project? Because if it's the latter, that's still a pretty high bar—legal costs eat into margins fast, especially for the smaller developers who'd actually build the mixed-income stuff you mentioned. The big ones can probably afford to fight, but they're not the ones solving the housing crisis.
I watched this play out in reverse once, which makes me skeptical of the framing. A medium-security facility in the Midwest—this was early 2000s—had a court order to reduce overcrowding and implement a education-based reentry program. State mandate, pretty explicit. The warden didn't have to convince the legislature or win a zoning board. The order was already written.
And it still took eight years to actually function, because the gates were different but just as effective. The warden complied with the letter—hired the staff, built the classroom wing, admitted people to the program. But he controlled the referral process. He could send people who were "too difficult" to the program, then claim low completion rates meant the program didn't work. The program director reported to someone who reported to someone else, not directly to him. Budget allocations got restructured so the education funding had to fight for space with operations. Guards' schedules changed in ways that made it hard to run classes during peak hours. Nobody was technically violating the order. They were just making it expensive to enforce.
The state could have sued, could have sent monitors, could have made it a condition of the entire facility's funding. But that's expensive and produces political blowback, and the state admin eventually just... accepted that the program would be this inefficient thing that technically existed. My point is that local actors have friction-making power even without formal veto authority. You're right that they need enforcement to lose, but enforcement doesn't fail because of clever legal maneuvering—it fails because someone has to sustain the will to override an institution that has every incentive to wait you out.
I saw this play out directly in a mid-sized city planning department, and the post is right about the mechanism but understates how much of it is just institutional inertia rather than active resistance. The zoning board thing is real—I watched a developer burn through three years and six figures on a by-right project because the city kept finding new studies it wanted before signing off. But the interesting part was that nobody was particularly organized against it. The same five homeowners showed up to two meetings. The real problem was that the city staff had no incentive to move fast, the process was opaque enough that delay didn't require justification, and once a project gets stuck in that limbo, it stops mattering whether the opposition is genuine or just how the machine runs.
Where the post might be slightly off: state mandates do work, but only when they're written to strip discretion rather than add it. California's parking minimums got eliminated partly because you can't really litigate a local variance request into the ground the same way when the default is "no parking required." But even then, cities find other gates. What I noticed is that friction beats rules in local governance because enforcement is local too—the mayor lives in the city, the planning director answers to the planning commission, the developer's recourse is expensive and slow. A state law is just a constraint the locals have to route around, not something that changes who has skin in the game.
The mechanism you're describing—friction as a veto tool—is real, but I think there's a layer underneath that explains why it persists even when states try harder to enforce. It's not just that delay is cheap for blockers and expensive for builders. It's that local governments have structural cover that state governments don't.
When a city council votes to deny a project or drag out approvals, they're not openly rejecting state law. They're applying local standards—design guidelines, traffic studies, parking ratios—that happen to be stricter than what the state technically allows. It's procedurally legitimate even when it's substantively hostile. A state AG has to prove bad faith or deliberate violation, which is a much higher bar than just showing a project got slower. And politically, the state is attacking a *city*, which has voters and a mayor and the kind of legitimacy that makes intervention look like overreach. Homeowners don't have to win the argument about housing; the city's structural position wins it for them.
The states that have actually moved density are the ones that didn't just write permissive rules but rewrote the *approval process itself*—removed local discretion entirely, made ministerial approval mandatory, cut off appeals. That's rare because it looks like a direct hit on local autonomy. Much easier to pass a law that says density is allowed and then watch cities find technically-valid ways to make it uneconomical. You've basically described Oregon's problem exactly: a rule with no execution mechanism is a rule you can ignore if ignoring it looks procedurally reasonable.