Week 3 — Why Multi-Line Signs Don't Work in Motion
A common response to last week’s argument is: “Well, the sign is right there at the corner — drivers should pay attention as they enter the block.” This argument doesn’t survive contact with the physics of reading.
Federal sign-design guidelines assume one inch of letter height yields about fifty feet of legibility under static, focused, optimal conditions. In actual driving, where sign-reading is incidental and glance-based, the practical legibility runs roughly half that:
- 6-inch headers (“NO STOPPING,” “2-HOUR PARKING”) — readable in motion at about 100–150 feet.
- 4-inch secondary lines (time bands, days of week) — readable at 75–100 feet.
- 3-inch lines — readable at 50–75 feet.
- 2-inch text — 25–40 feet.
- 1-inch fine print — effectively requires the vehicle to be stopped.
A multi-line sign — like the LA-style stack of “NO STOPPING / 2-HOUR PARKING / PASSENGER LOADING ZONE” with separate weekday and Saturday columns — cannot be read on a single glance. Each line requires its own fixation. At 30 ft/sec, four fixations consume more than a second of off-road glance time, and NHTSA’s voluntary distraction guidelines flag any single off-road glance over two seconds as a safety concern.
The signs are not designed for the task they’re being asked to perform. The information is correct; the form factor is wrong. A driver cannot read a multi-line tabular regulatory sign while moving at 20 mph any more than they can read a paperback book while jogging.
This is why even cities with perfect sign placement (which is rare) and perfect sign content (also rare) still fail to inform the driver at the moment of decision. The format itself doesn’t fit the cognitive task. Single-line signs with one piece of information per fixation are the only signage that works for a moving driver, and most American urban parking signs are far more complex than that.
Next week: what drivers actually do given this information environment — and why the result is rational behavior under bad conditions, not driver negligence.
Continue the series
12 parts · ~72–84 min total
The most productive piece of real estate any American city owns isn’t a building. It’s a 22-foot rectangle of pavement next to the curb. Every parking space along a commercial block sits at…
Read week 1 →Picture an average driver cruising at 20 mph through a downtown corridor — about 30 feet per second. They’re scanning for parking. Three numbers determine the outcome.
Read week 2 →A common response to last week’s argument is: “Well, the sign is right there at the corner — drivers should pay attention as they enter the block.” This argument doesn’t survive contact…
So what do drivers actually do? Empirical observation of drivers searching for parking shows that they don’t read regulatory signs proactively. They can’t, and they don’t try.
Read week 4 →The empty decision window isn’t a passive problem. It’s the input to a feedback loop:
Read week 5 →Take a representative midsized downtown with 5,000 managed curb spaces. The exact figures vary, but a working baseline:
Read week 6 →The single-space curbside meter performs two functions, only one of which is payment. The other is indication — the meter at a space tells the driver, at a distance and in motion, that the…
Read week 7 →For roughly a decade, parking-industry vocabulary has converged on a set of appealing words: asset-light, no-hardware, frictionless, free the curb of clutter. The reasoning has been that…
Read week 8 →There are two coherent ways to manage curb space. Either one can work well.
Read week 9 →Curb improvements need to happen in a specific sequence. Each step depends on the one before it. Skip a step and the framework collapses.
Read week 10 →A working on-curb display needs to satisfy four design constraints simultaneously. The constraints come from the geometry of the parking decision (covered in weeks 2–4), and any product…
Read week 11 →When a curb-management change is proposed — a new vendor, a new payment scheme, a new enforcement model, a new technology — there’s one question worth asking before any other:
Read week 12 →