Question
Why local opposition blocks housing even when states say yes
The standard story is that state-level pro-housing policy simply overrides local obstruction. California's SB 9 and 10, Oregon's statewide zoning reform—these should flatten local resistance. But they mostly don't. Housing still doesn't get built at scale. So there's something wrong with treating this as a pure hierarchy problem.
I think it's actually a venue problem. Local opposition has structural advantages that survive even hostile state law. First, implementation lives locally. A city planner, zoning board, or planning commission still has to process the actual application. They can't prevent the law from existing, but they can stretch timelines, request studies, ask for traffic analyses that take two years, flag "compatibility concerns." The state can mandate that cities allow duplexes, but it can't mandate that the permit gets issued in six months. Second, the people who show up to city council meetings are the people who live there. The state legislature hears from developers, yes, but also from statewide coalitions. A city council hears from the retired couple next door. Asymmetric participation is brutal. Third, there's a legitimacy gap. When the state overrides zoning, it feels like an imposition from above. When a city council rejects a project, it feels like democratic will (even if it's just the will of the people with time to attend meetings on a Tuesday).
What I'm genuinely unsure about: whether this means state-level reform is mostly theater, or whether it works by slowly shifting the cost-benefit ratio enough that some marginal projects pencil out anyway. The Scotts and Shonkoffs of the world would probably say the latter. But I haven't seen good evidence either way.
3 comments
Log in to comment.
You're right that implementation is the chokepoint, but I'm wondering if you're conflating two different delays. When a city stretches a permitting timeline, is that actually obstruction—like, deliberate sandbagging—or is it just the friction of any bureaucratic process? Because I taught in a district for years where we genuinely couldn't move fast on anything, not out of malice but because the systems were just built that way. Understaffed planning departments can't process forty duplex applications in six months even if they wanted to.
If that's true, then state law might work not by changing local preferences but by forcing resource allocation. A state mandate with teeth means you actually have to hire the staff to handle the volume. That's different than saying locals find workarounds. Have you seen data on whether cities that actually staffed up after these laws saw faster approvals? Or are the cases where implementation still crawls usually places where they just... didn't allocate resources to the reform?
I spent a few years watching this play out in a mid-size Oregon city right after the statewide zoning bill passed. You're describing the dynamic accurately, but I'd push back slightly on the "theater" framing—though I understand the temptation.
The state law didn't flatten local resistance, but it did something subtler: it removed the easiest excuse. Before, a city could say "we can't allow this, our code doesn't permit it." After, they had to say "we allow it, but..." and then the delays, the studies, the compatibility concerns kicked in. That's not nothing. It made obstruction require active work instead of passive rule-following. Some projects died in that friction. Others got built, slowly. The developer had legal ground to stand on, even if the process took eighteen months instead of six.
What I actually noticed, though: the venues that mattered most weren't the city council meetings. They were the planning commission review sessions, where you'd get the same five retired engineers every month, and the city staff who'd been doing this for twenty years and had relationships with the neighborhood associations. The state law constrained what they could say in public, but it barely touched how they could manage the process itself. That's where the real power was. The legitimacy gap you mention—that matters for political cover, not for whether a permit gets issued. A planner can issue a permit perfectly legally while making the applicant feel like they just survived a siege.
The venue problem is real, but I'd flip the framing slightly: what you're describing isn't why state law fails, it's the mechanism through which it *works slowly*. The implementation drag isn't a bug in the system—it's actually doing something.
I spent four years watching a mid-sized city try to enforce a state mandate around accessibility standards for collections storage. The state said you have to do this. The city's response was basically: yes, and here are the consultants we need to hire, the building assessments, the phased timeline. It took seven years to get the first phase done. But something shifted during those years. The planner who was originally resistant retired. The new planner had already worked in three other cities where this was normal. The budget committee stopped treating it as an imposition because there was now precedent elsewhere. By year seven, it wasn't theater—it was just how things worked.
I think the marginal-projects-pencil-out theory is right, but it's operating on a fifteen-year timescale, not the three-year timescale people want. State law removes the legal basis for saying no, which changes what "delay" means. Delay used to preserve the status quo. Now it just costs money and political capital. Eventually some projects happen that wouldn't have under the old regime, even if it's not the scale anyone promised. Whether that's worth the friction and the wait is probably a different question than whether it works.