Why we print the grid on every page
A visible grid keeps a team honest about alignment. How we use one from first sketch to shipped code.
We plan, design and build wayfinding, data tools and reports for transit operators, hospitals, utilities and foundations. Then we hand over the source and write down why every part is the way it is.
Northline Transit, P-034
38%
Four operators ran four maps in three languages. We counted 1,900 journeys at Sentrum station before drawing a single line, then replaced all four with one network diagram and 37 sign types.
Network maps, sign families and digital directions for stations, hospitals and campuses, tested on site with people who've never been there.
Planning tools and dashboards for operators who need one number they can defend in a board meeting, built on the data they already have.
Reports where every figure links to its source, the charts say one thing each, and the PDF passes an accessibility audit.
We walk the site or the product with the people who run it and count what actually happens.
Three directions in week three, one by week five, then the full system in the real material.
Prototypes go in front of strangers from week six. The build follows what the tests say.
Source, tokens and a written rationale, plus two half-days with the team that will run it.
A sign system outlives the team that drew it. If the reasoning isn't written down, the third person to change it undoes the first person's work without knowing it.
A visible grid keeps a team honest about alignment. How we use one from first sketch to shipped code.
What 1,900 observed journeys taught us about arrows, distances and the word "exit".
How we footnote an annual report so a journalist can check any figure in under a minute.
Tell us what the system is, who uses it and when it has to work. We'll answer with a scope, a team and a fixed price.
Part of the Design Systems Library