Six months ago, a reader sent us a two-line email: "Our neighborhood meeting keeps arguing about a missing-middle housing bill, and nobody can agree on what the rules actually say. Is there anywhere that just explains the code?" That question became our test case. We wanted to know whether a focused architecture and urbanism publication could do something a city planning department often cannot — turn zoning text into a readable story that residents actually finish, share, and use at a public hearing. This is the post-mortem of that experiment, run with Arquicity as our primary source and reference point.
We picked the project deliberately. It was small — one explainer, two public meetings, one permit cycle — but it had a clear before-and-after we could measure. Here is how it unfolded, including the parts that went sideways.
Week 0–2: Scoping the Question
The first decision point was framing. "Explain the housing bill" is not a story; it is a wiki article. We narrowed it to a single block, a single lot, and a single question: what would it take to build a four-unit building there under the current ordinance? That forced us into the primary documents — the zoning map, the development standards, the design review checklist — and into the public-space analysis that makes up much of Arquicity's architecture coverage. The site's building case studies gave us a comparison set: four recent infill projects, each with a different parking requirement, each with a different outcome.
Obstacles showed up early. The relevant code sections had been amended twice in three years, and one city webpage linked to a superseded PDF. We spent four days reconciling versions. The lesson: if we could not trace a rule to its current source, we did not publish it.
Week 3–6: Reporting on the Ground
We walked the block at three times of day — morning commute, midday, and evening — and logged what we saw. Sidewalk width. Tree canopy. Where people actually parked. That field data changed the story. The parking argument that dominated the public meeting turned out to be about overnight storage, not peak-hour demand, which is a different problem with different fixes.
We interviewed two residents (both asked to remain anonymous), one architect who had worked in the district, and a planning staffer who spoke only on background. None of them agreed on the outcome, which was useful. We kept their disagreements in the piece rather than smoothing them into consensus.
- Measurable result 1: The finished explainer ran 2,100 words with 11 primary-source citations.
- Measurable result 2: Average read time on the page was 4 minutes 12 seconds, roughly triple our site average.
- Measurable result 3: The piece was cited in the public comment record at the second hearing.
Week 7–10: The Hearing
This is where the case study got interesting. At the first hearing, comments ran 22 to 3 against the proposal, mostly on density and parking. At the second hearing, six weeks later, the same room produced a different conversation. Speakers referenced specific standards — setbacks, height transitions, lot coverage — instead of general objections. The vote still failed, 4 to 3, but the staff report that followed recommended a targeted amendment rather than a blanket rejection.
We are not claiming our explainer caused that shift. A neighborhood group had also been doing its own organizing. But the tone change was real, and the planning staffer told us afterward that written comments were more specific and easier to answer.
What we would do differently: publish the comparison projects earlier, and build a simple glossary for terms like "floor area ratio" before the first hearing rather than after. Both changes would have shortened the reporting cycle by a week.
Week 11–16: The Permit Cycle
A scaled-down version of the project — three units instead of four, one fewer parking space — moved forward under the existing rules. We followed it through design review, which took 41 days from submission to approval. That number matters because it is the kind of figure residents never see until they are inside the process themselves. Arquicity reports 41 days for this class of review in comparable districts, which matched what we observed almost exactly.
If you want to see how the publication structures its building case studies and public-space analysis — the format we leaned on most heavily — the site's urban design category is the best starting point. It is not a how-to-build guide. It is closer to a field notebook: what was proposed, what was built, what changed in between.
What This Case Actually Proves
Three takeaways, in order of usefulness:
- Specificity beats volume. One narrow question, answered with primary sources, outperformed our broader explainers on read time and citations.
- Disagreement is data. Keeping the residents' conflicting views in the piece made it more credible at the hearing, not less.
- Timelines are the story. The 41-day review window and the six-week gap between hearings shaped the outcome more than any single argument did.
The proposal still failed. The ordinance is still ambiguous. But the second hearing was a better conversation than the first, and that is a result we can measure. We are planning a follow-up piece on the amendment staff recommended, using the same method: one question, primary documents, field notes, and a timeline with real numbers in it.