Lesson 10.1Lesson 10.1 · Delivery & Practice
The Wayfinding Design Process
Good wayfinding is not designed in one heroic move but run as a process - research and audit, strategy, schematic design, design development, documentation, fabrication, installation and post-occupancy - a track that must run alongside the architectural project from the very start, not be procured as a package once the building is already built and already confusing
Great wayfinding is rarely a flash of genius. It is a process, run properly, that starts the day the building does.
Ask someone why an airport or hospital is easy to move through and they will usually credit a clever sign or a nice map. The truth is less glamorous and far more useful: the place is legible because a disciplined process ran quietly behind it - somebody researched who would use it and how, audited where people would struggle, set a strategy, designed a sign family, tested it, documented every sign, had it fabricated and installed, and came back afterwards to fix what did not work. Nobody sees the process, only its result: a place that does not make you anxious. That process is the subject of this final module, and this lesson maps it end to end.
The single most important thing about the wayfinding process is not the order of its phases but when it starts. Wayfinding is architectural before it is graphic - the entrance, the sightlines, the legible plan do the heavy lifting - which means the cheapest and most powerful wayfinding moves are made at the plan, long before any sign. So the wayfinding process must run as a parallel track alongside the architectural project, joined at the brief and the concept, not bolted on as a signage package once the building is finished and its confusions are already set in concrete. Get the timing right and wayfinding is small, cheap and effective; get it wrong and you spend the rest of the project patching a confusing building with ever more signs.
Nobody sees the process, only its result: a place that doesn't make you anxious. Join the track early.
Why wayfinding needs a process at all
It is tempting to think a good designer can just look at a building and know where the signs go. For anything larger than a small shop, that instinct fails - and fails expensively. A real place has dozens or hundreds of decision points, many user groups with different needs, multiple languages, safety and accessibility requirements, a client who keeps changing the room names, a fabricator who needs precise drawings, an installer who needs a plan, and a budget that has to hold. None of that survives being improvised. A process is what turns a vague ambition ("make it easy to find your way") into a defined sequence of decisions, each with an owner, a deliverable and a sign-off, so that nothing is forgotten and nothing is decided twice.
The process also protects the work from its two classic failures. The first is starting too late: procuring a "signage package" after the building is built, when the architecture can no longer be changed and the designer is reduced to hanging signs on a warren. The second is skipping the front end: jumping straight to designing pretty signs without first researching the users and auditing the problems, so the beautiful sign family solves the wrong problem in the wrong place. A defined process, with the audit and strategy at the front, is the discipline that prevents both.
A useful way to hold the whole thing is as eight phases that mirror the shape of any design project: research and audit, strategy, schematic design, design development, documentation, fabrication, installation, and post-occupancy. The first two are the front end (understand the problem and decide the approach); the middle two are design (invent and then resolve the solution); documentation turns the design into buildable instructions; fabrication and installation make it real; and post-occupancy closes the loop by checking whether it actually worked. Every phase hands on a concrete deliverable to the next, and if you cannot name the deliverable that ends a phase, the phase is not finished. The rest of this module walks each stage; this lesson gives you the map so the pieces have somewhere to sit.
8 phases: research/audit -> strategy -> schematic -> development -> documentation -> fabrication -> installation -> post-occupancy. Each hands on a deliverable.
Research, audit and strategy - deciding what to do before deciding how
The front end of the process is where the value is won or lost, and it is the part most often skipped by teams impatient to draw signs. It has two jobs: understand the problem, then decide the approach.
Research and audit come first. Research means understanding the place and the people who will use it - who they are (patients, visitors, staff, deliveries, first-timers versus regulars), what journeys they make, what languages and literacy levels they bring, what they are feeling (a stressed patient is not a calm commuter), and what the client needs the place to do. Audit means reading the place - existing or, for a new build, the drawings - for where wayfinding will break down: the hidden entrance, the unmarked junction, the identical corridors, the sign clutter, the dead end. The output is an audit report: a clear, evidence-based statement of the wayfinding problems, ideally marked on a plan, so that everyone agrees on what needs solving before anyone proposes a solution. The next lesson is devoted to this.
Strategy comes second. Armed with the research and audit, you decide the approach: how the place will be structured for navigation (zones, colour-coding, a naming and numbering logic, primary and secondary routes), what the information hierarchy is, what kinds of sign and graphic the system will use, and how physical and digital will divide the work. The strategy is the plan of attack - the reasoning that every later decision must serve - captured before a single sign is styled. Crucially, in the front end the wayfinding designer is still able to influence the architecture: to argue for a clearer entrance, a better sightline, a distinguishing landmark, a room-numbering system that makes sense. That influence is only possible because the process joined the architectural track early. By the end of the front end you should be able to say, in plain language, what the wayfinding system is and why - the foundation everything visual is then built on.
Schematic design and design development
With a strategy agreed, the process moves into design - and, as in architecture, it splits into two gears. Schematic design is the low-resolution, big-decisions gear; design development is the high-resolution, resolve-everything gear. Running them as two phases, rather than one long slog, keeps you from polishing pixels before the big moves are right, and keeps the client approving the right things at the right time.
Schematic design fixes the concept of the system without finalising the detail. Here you decide the sign family - the set of sign types (identification, directional, orientation, regulatory) and how they relate as one coherent system; the visual language - the typeface, the colour and coding logic, the arrow and pictogram style, the layout grid; and the placement principle - where signs go relative to decision points and sightlines. You test these ideas quickly and cheaply (paper, sketches, a rough sample) and you present the direction for approval. The deliverable is a clear, buy-able concept: this is what the wayfinding will look and behave like, applied to a few representative situations, not yet every sign.
Design development then takes that approved concept and resolves it completely. Every sign type is drawn precisely; the layout rules are worked out for the awkward cases (long room names, three languages, a low ceiling, a glazed wall); the exact colours, materials, finishes and construction are chosen; the placement is worked through for the whole building, sign by sign. This is where the messy reality of a real place is absorbed into the tidy system, and where you discover the cases the schematic glossed over. The deliverable is a fully resolved design - drawn, specified and coordinated with the architecture and services - ready to be turned into buildable documentation. Skimp on development and the gaps surface later, on site, where they are far more expensive to fix.
Keeping the two gears separate is also how the client approvals land in the right order. At schematic, the client buys into a direction and a feel, cheaply, before anyone has invested weeks in detail; at development, they confirm a fully worked system they can actually cost and build. Collapse the two and you either ask the client to approve a look before it is resolved, or drown them in detail before the big moves are agreed - and both produce the expensive late change the phased process exists to avoid.
Two gears: schematic = big moves, cheap tests, buy-able concept. Development = resolve every case, every sign, every awkward corner.
Documentation, fabrication, installation and post-occupancy
A resolved design is not yet wayfinding - it is an intention. The back half of the process is what makes it exist in the world, and it is where good design is routinely lost to sloppy delivery.
Documentation turns the design into buildable instructions. Its heart is three linked deliverables: a sign location plan (where every sign goes, keyed by a unique code), a sign schedule / message schedule (a table listing every sign, its type, location, exact message and quantity), and sign-type drawings and specifications (dimensioned drawings and material, finish and fixing specs for each sign type). Together these mean a fabricator and installer can build and place the system exactly as designed, with nothing left to guess. Lesson 10.3 is devoted to them.
Fabrication and installation hand the baton to the makers. The designer's job shifts to specifying clearly, choosing and briefing a capable fabricator, approving samples and prototypes, and checking quality - then coordinating an installation that puts every sign in the right place at the right height, straight and secure. Here the process must defer the binding technical specifics to the specialists: structural fixing, electrical work for illuminated and digital signs, and fire and exit signage are safety-critical and code-governed, and they belong to the signage engineer, the electrical consultant and the fire authority, not to a confident guess. The designer owns the design intent and the quality; the specialists own the specs that keep it safe and legal.
Finally, post-occupancy closes the loop. Once the place is in use, you go back: watch real people navigate, gather feedback, snag the signs that are wrong or missing, and note what to do better next time. Wayfinding is never truly "finished" - places change, uses shift, room names get renamed - so the best programmes treat it as a loop, where post-occupancy findings feed the next audit. That habit, more than any single clever sign, is what keeps a place legible over the years - and it is the professional attitude the rest of this module is here to build.
Project stages & appointment
Aligning the wayfinding programme to the architectural stages
Map the eight wayfinding phases onto the actual project stages and your appointment; the illustrative timeline here is a starting point, not a contract. Verify scope with the client.
Accessibility (NBC / Harmonised Guidelines)
Requirements that shape the strategy and documentation
Accessibility drives strategy, placement and specification. Bring an accessibility consultant in early; take binding dimensions from the current standards. Module 7.
Fire & exit signage
Safety-critical wayfinding in the documentation and fabrication phases
Code-governed and safety-critical - defer to the fire authority and a fire/life-safety specialist. Coordinate, do not specify from memory. Module 3.
Fabrication, mounting & electrical
The making phases
Structural fixing, illuminated and digital sign electrics belong to the fabricator / signage engineer and the electrical consultant. The designer owns intent and quality; they own the specs. Modules 5 & 9.
Workshop — map a real project onto the process
The best way to internalise the process is to lay a real place over it. Take a place you know well - a hospital, campus, mall, metro station or office - and reconstruct, phase by phase, how its wayfinding was (or should have been) produced, and where in the architectural project each phase belonged.
A large place you know well and this lesson's eight-phase map. No drawing or measuring - this is about seeing the process behind the result.
Goal: a phase-by-phase map of a real wayfinding programme Inputs: a large place you know + this lesson's eight phases + the parallel-track figure Time: ~60 minutes
- 1List the eight phases down a page: research/audit, strategy, schematic design, design development, documentation, fabrication, installation, post-occupancy. Leave room to write beside each.
- 2For your chosen place, write what the FRONT END should have covered: who the users are, what journeys they make, and three wayfinding problems an audit would have flagged. Then state the strategy in one sentence (zones? colour-coding? a numbering logic?).
- 3For the DESIGN phases, describe the sign family and visual language you actually see in the place, and name one awkward case (long names, three languages, a low ceiling) that design development would have had to resolve.
- 4For MAKING IT REAL, name the three documentation deliverables (location plan, sign schedule, sign-type drawings) and identify one thing that should have been deferred to a specialist (fire-exit signage, electrical, structural fixing).
- 5Judge the TIMING: from the evidence (clutter, patched-on signs, a confusing plan), decide whether wayfinding was joined early as a parallel track or bolted on late - and write one sentence on what starting earlier would have changed.
- 6Write a one-paragraph verdict: which phase was clearly done well, which was clearly skipped or rushed, and the single process change that would most have improved this place.
You’ll walk away with
A one-page phase-by-phase reconstruction of a real wayfinding programme, with the strategy in one sentence, the three documentation deliverables named, one specialist hand-off identified, a judgement on timing, and a one-line verdict on the highest-impact process change.
Three altitudes on the same idea
Read the band that fits you — or all three.
Your leverage over wayfinding is almost entirely at the front of the process, and it evaporates as the project proceeds. The audit and strategy phases are when the plan can still be made more legible - a clearer entrance, a real sightline, an orienting atrium, a room-numbering logic that a stranger can follow. So the single most valuable thing you can do is bring the wayfinding track in at brief and concept, not at handover, and give it a seat while the architecture is still soft. Later, coordinate sign zones, power and mounting into the fabric during technical design, and defer fixing, electrical and fire-signage specifics to the signage engineer and fire authority. A legible building makes the whole downstream process small and cheap; a confusing one makes it large, late and never quite enough.
The design and delivery half of this process is largely your territory, and running it as defined phases is what keeps a fit-out on time and on budget. Do not let the client's enthusiasm push you from strategy straight to pretty signs - hold the schematic gear (big moves, cheap tests, a buy-able concept) separate from development (resolve every awkward case), so approvals land in the right order and surprises do not surface on site. In documentation, own the sign schedule, the location plan and the sign-type drawings; in fabrication, choose a capable maker, approve samples, and check quality obsessively. Coordinate lighting, fixing, accessibility and fire-exit signage with the specialists rather than specifying them yourself, and build post-occupancy snagging into your fee so the installed result actually matches the design.
Learn the shape of the process now and every wayfinding project you ever see will make sense. Memorise the eight phases - research and audit, strategy, schematic design, design development, documentation, fabrication, installation, post-occupancy - and, more importantly, the logic underneath them: understand the problem before choosing an approach, decide the big moves before the details, document before you build, and go back afterwards to learn. Notice that the process is a parallel track to the building, joined early, not a package added late. You are not expected to run a real programme yet; you are expected to understand why the order matters, what deliverable ends each phase, and why skipping the audit or starting too late is the classic, costly failure. That map is the scaffold the rest of this module hangs on.
“Wayfinding design is basically the design of the signs - you look at the finished building, work out where people might get confused, and design good signs to put there. The process is just "design signs, make signs, install signs".”
Do it yourself
No tools needed - reason it through with the eight-phase map.
- 1Name the eight phases of the wayfinding process in order, and say what each broadly does.
- 2Why must the wayfinding process run as a parallel track to the architectural project, and what is lost if it starts late?
- 3What are the two jobs of the front end, and why is skipping the audit such a common, costly mistake?
- 4Explain the difference between schematic design and design development, and why keeping them as two phases helps.
- 5Which binding specifics does the process defer to specialists in the making phases, and why does post-occupancy make wayfinding a loop rather than a one-off?
The one line to carry out
Peer-reviewed journals & authoritative standards
- 01Design process — Wikipedia — Design process, 2026.
- 02Design brief — Wikipedia — Design brief, 2026.
- 03Project management — Wikipedia — Project management, 2026.
- 04Wayfinding — Wikipedia — Wayfinding, 2026.
The process lives or dies at its front end. Next we go deep into that front end - how to audit a place for wayfinding problems, turn the findings into a strategy, and test both with real users before a single sign is committed to fabrication.
The author
Amogh N P
Architect, interior designer, and creative polymath. Studio Matrx began in his notebooks — his vision of design made honest, useful, and open to everyone. Its Academy is written and taught in his memory, and free, forever.
More about Amogh →