Decision Points & the Journey

A decision point is any place on a journey where a person must make a choice about which way to go. The clearest examples are physical junctions: a corridor T or crossroads, a lobby with several exits, a fork in a path, a landing where the stair could go up or down, the top or bottom of an escalator, the point where you leave a train and must choose an exit, the entrance where you first decide how to penetrate the building. But decision points are defined by the choice, not only by the geometry - anywhere the route could plausibly go more than one way, or where a person could reasonably be unsure whether to continue, is a decision point. Some are obvious; some are subtle (a long counter where you must pick a queue, a plaza where the onward path is not obvious).

Decision points matter because human attention and information-processing are limited and intermittent. People do not, and cannot, continuously scan and read a building; they conserve attention on the easy links and spend it at the choices. This means information offered where there is no decision is largely wasted - and worse, adds to clutter that hides the information that matters - while information missing at a decision point is a genuine failure, because that is exactly where the person has stopped, looked up and asked 'which way?' The economy of a good wayfinding system comes directly from this: inform at the decision points, stay quiet on the links, and you give people exactly what they need with the least clutter.

There is a deeper point here that ties back to the whole course. Many decision points can be answered by the architecture itself - if, standing at the junction, you can simply see your destination, or see an obvious main path, the building has answered the question and no sign is needed. So the first move at every decision point is to ask what the space already tells you; a sign is required only where the choice is real and the architecture does not resolve it. The strongest wayfinding systems have fewer, clearer decision points because the building is organised to minimise ambiguous choices - a single main route, a clear hierarchy of paths - and then place crisp information at the genuine choices that remain. Finding and understanding the decision points is therefore not just a signage task; it is a way of reading how legible the building is in the first place.

Once you have found a decision point, the discipline is to deliver the needed information exactly there - at the moment and place the choice is made - and this timing is where a great deal of real-world wayfinding quietly fails. Two failure modes are common. The first is too early: the directional sign is placed well before the junction, so by the time the person actually reaches the point of choice, the instruction has scrolled out of their short-term memory and they hesitate again, or they act on it too soon and turn at the wrong opening. The second is too late: the sign is placed at or just past the junction, visible only once the person has already committed or overshot - the classic motorway-exit problem, where the sign for the turn appears when you are already sailing past it.

The correct placement is just-in-time: the information must be visible from the decision point, or approaching it, with enough time and space for the person to read it, understand it and act - to change lane, slow, and turn - before the choice is upon them. For a person walking, this usually means the directional sign is legible as they approach and arrive at the junction, positioned in their natural line of sight (which is why sightlines and mounting, covered in Module 5, matter so much), and repeated or reinforced if the approach is long or fast. The faster people move and the more committing the manoeuvre (a vehicle, an escalator, a merging crowd), the more lead time the information needs - a driver needs the sign much further ahead than a stroller does.

A useful test is to stand at each decision point and ask three questions in order. First: is there actually a choice here, and does the architecture already answer it? If not, second: is the needed information (usually direction) visible from here, in the natural line of sight, at the moment of choice? Third: does the person have enough time and space to act on it before committing? A 'no' to the second is a missing or mis-timed sign; a 'no' to the third is a sign placed too late or too close. This 'stand at the decision point and look' habit - seeing the junction through the eyes of someone arriving at it for the first time, at their speed - is one of the most valuable practical skills in wayfinding, and it is why designers walk the route rather than plan signs from a drawing alone.

Between the decision points lie the links - the stretches of the journey where there is no choice to make, only distance to cover - and these have their own, different job. On a link the person does not need direction (there is nothing to decide), but they do need something the previous lesson named as the most-forgotten information type: confirmation, or reassurance. As a link lengthens, or bends, or passes featureless walls, the confident decision taken at the last junction slowly decays into doubt: 'was that the right turn? should I have arrived by now? did I miss something?' A short confirmation along the link - the destination name repeated, 'Departures, keep straight', a continued colour-code, a landmark coming into view - answers that doubt before it turns into stopping, backtracking and anxiety.

The vivid way to think about this is a trail of breadcrumbs: a continuous, unbroken thread of reassurance that connects one decision point to the next, so that a person is never left wondering whether they have fallen off the route. The breadcrumbs need not be frequent or heavy - they must simply be present often enough that the person is never in doubt for long, and above all the trail must not break. A broken trail - a confirmation that appears once and then vanishes for a long stretch, or a colour-code that stops halfway - is often worse than none, because it trained the person to expect reassurance and then withdrew it exactly when the anxiety would peak. Continuity is the quality that matters: the thread must hold all the way to the destination, where identification finally confirms arrival and the journey ends.

This link-and-decision-point rhythm is what makes a route feel calm. At each decision point, clear direction resolves the choice; along each link, a steady trail of confirmation holds confidence; and at the destination, identification closes the loop. Designing a route well means walking it as a sequence - decision point, link, decision point, link, arrival - and checking that direction lands at every choice and that the breadcrumb trail never breaks in between. In India this continuity carries an extra demand: the trail must hold across scripts and for low-literacy travellers, so a consistent colour-code, a repeated pictogram or a recurring landmark can carry reassurance where words alone would exclude people. A route that directs well at the junctions but abandons people on the long links between them will still feel confusing - because being unsure you are still right is its own distinct kind of lost.

Putting this to work means building a decision-point map of the real journeys people make - the practical bridge from principle to a placed system. The method starts not with the plan but with the people: identify the key user journeys - the trips that actually matter and recur (arriving visitor to main reception; patient from entrance to a common department; passenger from platform to street exit; new employee from lobby to a meeting room). A wayfinding system serves journeys, not rooms, so you map the handful of high-volume, high-stakes routes first, including the ones taken by the most stressed and unfamiliar users.

For each journey, walk it - literally, at the user's pace, ideally as a first-timer would, and this is essential rather than optional. As you go, mark every decision point (each place you must choose), noting the choice to be made and whether the architecture already answers it. Between them, note the links and how long and how featureless they are, flagging where doubt would set in. Record what information each point needs - which of the four types - and what is there today. The output is a decision-point map: the route drawn as a line, decision points circled with the direction they must give, links marked with where confirmation breadcrumbs must fall, and the destination marked for identification. This map, built for each key journey and then overlaid onto the building plan, is the raw material of the information plan and the sign location plan you will assemble in lesson 2.4.

Two cautions keep this honest. First, decision points are best found on foot and from the user's eye level, not from a floor plan on a desk - a plan hides sightlines, crowds, glare, level changes and the real experience of arriving at a junction, so plan-only sign placement reliably misplaces information. Second, resist the pull to over-inform: the same walk that finds missing information at real decision points will also reveal signs posted where there is no choice, and stripping those away is as much a part of the method as adding the missing ones. Done well, mapping the journey turns wayfinding from guesswork - 'put a sign here, it looks bare' - into a precise, defensible logic: this is a decision point, here is the choice, here is the information that answers it, and here is the trail that carries you to the next one.