Skip to Content

PERSPECTIVES / Space and Service Experience

Wayfinding Happens at Key Points Along the Path

Arrival, turns and location confirmation each call for a different level of information.

Research & PerspectivesOctober 9, 2026Edited by Qingmei Future

Research Notes

Arrival, turns, and confirmation each require different information tiers. This article explores the relationship between content, design, and use, offering a judgment framework applicable to project discussions.

Observe the path by walking the task.

Map decision points along real routes. Entrances, junctions, level changes, and destinations carry different wayfinding tasks—signage should correspond to these tasks.

Prompts must connect sequentially.

Even a clear sign must connect to what came before and what comes next. Consistent names, arrows, and numbers help people confirm they are on the right path.

Build maintenance into system design.

Events, temporary closures, and space renaming affect routes. Plan in advance who updates what, and how—this keeps the permanent system usable.

Bringing it into project discussions

  • Arrival: Can first-time visitors confirm their location?
  • Navigation: Is guidance continuous and clear at key decision points?
  • Maintenance: Can names, events, and temporary changes be updated promptly?

Bring these questions to real materials and use cases, recording the current version, the rationale for changes and feedback from use. When every adjustment has a clear basis, the team can keep applying these judgments in future work.

Reader's Note

This article presents design methods and project observations written by Qingmei Future for its website. The project links below are provided for reference to existing work and application materials. The methods suggested here do not imply that all listed projects followed the same process, nor do they constitute project outcome data.

CONTINUE READING Further Reading

Find your next step, starting with the question at hand.

When you get in touch about a project, it helps to share your business context, existing materials, primary use scenarios and the problems you want to solve. We'll use this to discuss scope and how we might work together.

Communicate project requirements ↗