No Road Block

Stretches of Toronto's Lower Don Trail were fenced off for construction, with no useful information provided for over 3 years. The notices online did not reflect reality and the signs on site said less. People stand at a barricade, guess, and turn back.

No Road Block began as a four-week research sprint into how people navigate those closures. The findings became a tested prototype, then a five-day build that shipped as a live product: a community-reported status site with its own identity, map theme and print system.

Four weeks of municipal notices, social posts and interviews on the trail. What people wanted was a plain answer, whether they could get on and whether it was paved, and they wanted it where they were standing, not at home planning a route. Everything the product does traces back to that.

It was the lack of usable information at the closure itself that sent people home. And they orient by bridges, in stretches of trail between access points rather than the city's section names. That became the product's information architecture.

The first prototype opened on a data visualisation, a tile for every stretch of trail. Frequent users could read it; newcomers couldn't find a detour at all. So the flow was rebuilt to start from the closed gate and end at directions, and the tiles gave way to a real map with the bridges people orient by. Familiar beat novel.

The prototype rested on an assumption: that timely closure data would exist to feed it. It doesn't. Municipal notices lag reality by days; conditions on the trail change by the hour.

The research already held the answer. The question at a barricade, can I get through, is one the people already on the trail answer better than any document. So the product inverts the model: walkers report what they see, clear, on foot only or blocked, and the majority of the last 24 hours becomes the status the next walker sees.

Stickers at the five access points link straight to that spot's status page, each headed with the question a walker is already asking there. Straight black on weatherproof vinyl: in full sun, scan contrast beats brand purity.

The identity was drawn inside the same five days as the product, playfully reworking temporary road signage. Organi letterforms dotted with the circles reminiencent of bolt holes on a roadside sign or the dots on the map.

One base, and one compliment. Brand blue works across, wordmark, trail, codes, map linework, over off-white.

The letters began as Pilowlava Atome, an open-source typeface from Velvetyne. An open face for a service built on free, community-reported information; the holes were already in it. The wordmark was then redrawn by hand as outlines.

The map is the product, so it got its own theme: the base map stripped back to what matters on foot, river, parkway, green space, trail, drawn in halftone screens at device pixels. Statuses are carried by label and icon as well as colour, and both themes follow the phone's setting.

The valley is a connectivity dead zone, so the engineering choices were design choices. The site is static, tiny and framework-free, with self-hosted tiles, a pre-rendered map when tiles can't load, and the phone's last-cached statuses when the API can't be reached.

A smooth zoom smeared the halftones into moiré on every gesture. Instead of hiding the seam, every zoom pixelates the frame into a coarse mosaic, the map re-renders underneath while nothing legible is on screen, and the new view reassembles out of the pixels.

Most case studies end at the prototype. This one shipped, and the research held: high-level statuses over detail, answers at the gate, familiar patterns over novel ones. The biggest product decision, flipping from municipal data to community reports, came straight from a research insight.

Next: tag stretches with surface, grade and width for wheelchair routing; French copy; more of Toronto's ravine corridors; usability sessions with low-vision participants on the live site.