Audit, Strategy & Testing

An audit is a systematic reading of a place - or, for a new build, of its drawings - to find exactly where wayfinding will break down and why. It is not a vague impression that "the signage is bad"; it is a specific, evidence-based inventory of problems, located on a plan, that everyone can agree on before anyone proposes a solution.

The method is simple and physical: walk the real journeys, as the real users, and log every decision point. Pick the key journeys - main entrance to the commonest destinations, the car park to reception, the drop-off to the emergency department - and walk each one slowly, pausing at every point where a person must make a choice (which way at this junction? which of these doors? up or down here?). At each point, ask: is it obvious where to go from the space itself? If not, is there a sign, is it in the right place, does it say the right thing, can you read it, does it contradict the space? Note where you would hesitate, where you would guess, where you would give up and ask. Photograph the failures.

Crucially, the audit must distinguish architectural failures from signage failures, because they have completely different fixes. An architectural failure - a hidden entrance, no sightline to the destination, a warren of identical corridors, a confusing plan - often cannot be fixed with signs at all, only patched; it wants an architectural change if the project is early enough, or an honest acknowledgement that signage is compensating. A signage failure - a missing sign at a decision point, clutter, unclear wording, a sign contradicting the space - can be fixed within the sign system. Marking both kinds on a plan, in different colours, produces the audit's core deliverable: a hotspot map that shows where people get lost and whether the space or the signs are to blame. Do it for an existing place before a redesign; do it on the drawings for a new build, early enough that the architectural findings can still change the building.

An audit tells you what is wrong; a strategy decides what you will do about it. This is the bridge from problem to solution, and getting it explicit - written down, reasoned, agreed - is what keeps every later design decision honest.

The strategy answers a set of structural questions, in roughly this order. How will the place be organised for navigation? Are there natural zones or districts that should be named and made distinct; would colour-coding or a numbering logic help people hold a mental map; what are the primary and secondary routes? What is the information hierarchy? What must a person know at the entrance versus at each junction versus at the destination, so that information is revealed progressively rather than dumped all at once? What is the terminology? The names and terms the system will use - agreed once, consistently, in the languages the place needs - because inconsistent naming (Casualty here, Emergency there, A&E on the third sign) is one of the commonest and most confusing failures. What kinds of sign and graphic, and what role for digital? The families the system will use, and how physical signage and any digital or app-based layer divide the work.

A good strategy is also honest about the architecture. Where the audit found architectural failures and the project is early enough, the strategy should recommend spatial fixes - a clearer entrance, an orienting landmark, a better sightline - not just more signs. Where the architecture cannot change, the strategy states plainly where signage is compensating and accepts the limits of that. The deliverable is a concise strategy document: the reasoning, the zoning and naming logic, the hierarchy, the terminology and the sign-and-digital approach - the plan of attack that the schematic design will then give visible form. If you cannot explain the strategy in plain sentences to the client, it is not yet a strategy; it is a pile of preferences.

The discipline of writing it down matters more than it sounds. A strategy held only in the designer's head quietly drifts as the project wears on, and every later argument - about a sign type, a colour, a word - has no settled reference to appeal to. A written, agreed strategy is the thing you return to when a decision is contested: does this choice serve the zoning logic and the hierarchy we agreed, or not? That single question, answerable only because the strategy was made explicit, keeps a large system coherent under months of pressure.

A strategy and a design on paper are a set of predictions about how people will behave. Predictions are cheap to make and often wrong, so the professional habit is to make the idea real enough to test, at the lowest cost that still teaches you something, and to climb that ladder before committing to the expensive, irreversible step of fabricating the whole system.

The ladder runs from cheap and rough to costly and real. At the bottom, paper and desk checks: sketch the sign at a junction, print a message layout at rough scale, and walk through the logic on the plan - does the information appear where the decision is made? Next, scale mock-ups: models or printouts placed in a model or a drawing to test relationships and sequence. Then, crucially for signage, a full-size sample: one real sign, at real size, in real light, seen from the real viewing distance - because letter height, contrast, colour and glare behave nothing like they do on a screen or an A4 sheet, and a sign that looked perfect at desk scale can be illegible on the wall. Finally, a prototype run of a few signs installed along an actual route, so you can test the system, not just a single sign.

Each rung answers different questions, and the point of climbing in order is that the cost of changing your mind rises as you climb. A flaw caught on paper costs a new sketch; the same flaw caught after the whole system is fabricated and installed costs a re-manufacture, a re-install and a lot of face. Prototyping is not perfectionism or delay - it is the cheapest insurance in the whole process. In India, where a place may need three scripts on one sign and serve many low-literacy users, a full-size, real-light prototype tested with actual users is especially valuable: it is the only honest way to know whether the type, the pictograms and the layout truly work for the people who will depend on them.

The final, humbling truth of the front end is this: the design team cannot judge whether a place is easy to navigate, because they already know where everything is. Familiarity is a curse - you cannot un-know the layout, so you cannot feel the confusion of a stranger. The only cure is to test with people who do not know the place, and to watch what they actually do rather than ask what they think.

The core technique is the walk-through, or wayfinding test: give a real person - ideally a genuine first-time visitor, and deliberately including people who will find it hardest (elderly, low vision, non-local-language, a stressed parent) - a realistic task ("find the radiology department", "get from the car park to gate 14") and follow them, silently, taking notes. Where do they pause? Where do they guess wrong? Where do they backtrack? Where do they give up and ask a person? Do not help, do not explain - their struggle is the data. What people do is far more reliable than what they say, because people are polite about signs and honest with their feet.

The simplest and most powerful version is the fresh-eyes test: bring in someone who has never seen the place - a colleague from another team, a friend, anyone - and have them navigate it cold. A stranger will find in an hour the confusions the design team has become blind to. Make it a habit, not a one-off: fresh eyes at strategy (does the logic make sense to an outsider?), fresh eyes on a prototype (can a stranger use this sign?), fresh eyes after installation (does the whole thing work?). And feed every finding back - fix what the test exposes before fabrication where you still can, and snag what it exposes afterwards. Testing is not a box to tick at the end; it is a way of working that treats the anxious, unfamiliar visitor - the true client of all wayfinding - as the only judge whose verdict actually counts.