Destinations is an application concept that simplifies the design process of wayfinding systems. Users can view a digital representation of a project site, visually plan visitor routes, sign placements and messages.


Wayfinding systems are used to help and guide visitors navigating large buildings or places. In cities, we are constantly surrounded by such systems to give us orientation. Wayfinding systems have the difficult task of connecting rooms and floors of buildings or even whole buildings on a strategic level. At the same time, every sign has to be easily understood by first-time-visitors. After entering a building, visitors have many different goals or objectives in mind that they want to complete and they expect to be guided to them without friction.

Most ambiguities in a guidance system can be eliminated by increasing the number of signs. More elegant than increasing the frequency of information is to achieve the best possible positioning of signs in a space. The foundation for this is a sound wayfinding strategy.

Goal of this project is to first understand the design process of wayfinding systems and then design a specialized application for it.

The Current Design Process

The relevant stages of the wayfinding design process for our project are analysis, strategy, programming and design.

During analysis designers get an understanding for the architecture, either through plans, renders or by visiting a building if it exists already. They analyze lines of sight and circulation patterns.

Following analysis, a strategy is developed outlining how visitors should be guided through a site. Where traffic flows should be combined or split up, which hallways should be highlighted and how a hierarchy should be constructed.

“[We worked very graphically] while piecing those sequences together and checked step-by-step if the routes are cohesive.”

During programming, designers determine where visitors have to make decisions and create the first signs and sign sequences. They also start working on which messages - like rooms and directions - should be displayed on them. Visitors should not be overwhelmed with information and get confirmation on their way in a predictable manner.

Finally, in the design phase different variants of signs are created. Prototypes are manufactured to test different materials, colors and the signs themselves in their intended size. Sometimes walls or even rooms are created from cardboard to test how signs have to be positioned in their environment.

Wayfinding system design process according to literature

During our research phase we compared the design process how it is described in ‘Wayshowing > Wayfinding’ and ‘The Wayfinding Handbook’.

Circulation Patterns

Studying traffic flows is one of the most important steps in developing a wayfinding system. For this purpose, traffic flows are drawn on floor plans. First, all rooms, entrances, elevators, staircases, and other transitions between floors are marked. After that, all destinations and connectors are marked. Finally, traffic flows with their direction of movement can now be entered and illustrated.

Designers commonly receive documents detailing current or predicted traffic flows and important destinations from the developers and architects. In existing buildings they conduct on-site surveys as well.

Sign positions can then be drawn where they are needed to get an overview of the decisions visitors have to make.

Circulation patterns

Signage development in three steps. First, circulation patterns for all types of traffic are created. Second, preliminary sign positions are marked on the floor plan. Finally, signs are marked on the plan with their reference codes to the database.

Signage Databases

A wayfinding system can easily grow to include hundreds of different signs and become very complex. Therefore, it is necessary to create a separate database with all signs, in which data such as sign type, size, messages and exact position is recorded.

All of this data must be kept up-to-date in an ongoing project. Inevitably, changes occur during work and after coordination with project partners. This makes the process prone to errors and creates a lot of manual work. This becomes even more of a problem when working on large projects that can encompass 3.000 signs or more. For this reason, one of our interview partners uses a custom database software to manage their projects internally.

Following our research, we formulated three how might we questions that encapsulate our findings

  1. How might we aid designers in analyzing project sites?
  2. How might we eliminate repetitive tasks and simplify management of signage databases?
  3. How can we use simulation to preview sign concepts before production?
Route Creation Decision Points Sign Locations Dynamic Messages 3D Simulation

Data Structure

One of the most important aspects of Destinations is it’s data structure that is highly optimized for the design workflow. Basis is a 2D or 3D model of a site, from which decision points are generated. On top of these two components users create information sequences between places. They connect the previously generated decision points on their way to their destination. When signs are created they are assigned to a decision point and have access to all information sequences that run through that point. Because of this, signs can access the destinations referenced by sequences and in turn properties of those destinations.

As the last puzzle piece, templates connected to signs can be dynamically filled with referenced data like room properties.

This approach makes Destinations and its workflow highly flexible. Properties are dynamic and editable and connected elements are updated correspondingly.


This project was created during summer semester 2020 together with Martin Wehl as part of our bachelor thesis in Interaction Design at HfG Schwäbisch Gmünd. The project was supervised by Prof. Marc Guntow and Prof. Daniel Utz.

It is part of the goHfG startup program and was awarded the goAward in February 2021. More information and updates available at

Get the Documentation (.pdf, 47MB)

Back to Projects