Structural Navigation Model

UX & Product Architecture • Design Systems & Engineering

A structural navigation model describes the main and local paths people use to move through a product's information architecture. It shows how sections and views are organized, what users can reach from each level, and how they can move back to a broader view.

How does structural navigation differ from contextual navigation?

Structural navigation follows the product's organization. For example, Trips → Trip details → Bookings follows a section down to a local view. Contextual navigation connects related information where a user needs it. A link from a trip's traveler list to a Traveler record is a contextual route that can cross sections.

Keep a record’s name and identifying details consistent across entry points. An agent who arrives from search should recognize the same booking they see on a trip.

Navigation example for a travel operations tool

Route Design decision
Main menu → Trips → Trip details Trips gives agents a stable starting point for work organized around trips.
Trip details → Bookings Local navigation keeps a trip's bookings within reach while the agent reviews that trip.
Trip details → Traveler record A contextual link lets the agent inspect a related traveler and their other trips.
Search → Booking details A direct entry should show the booking's identity and link to its trip when the user has access.

The object map explains which records are related. Use the navigation model to choose which relationships become routes. Use the product's hierarchy to choose the breadcrumb trail. Use a separate return control when agents need to get back to a filtered list.

How do you design and test the model?

  1. Start with common tasks. Identify where users begin and which views they need to reach. Use Object Prioritization to distinguish primary entry points from nested records, and choose main sections and local views that match those tasks.
  2. Add useful contextual links. Decide which related records users need nearby. Use cardinality to anticipate how many results a path may expose.
  3. Plan orientation and return paths. Check that titles, local navigation, and breadcrumbs make sense on direct entry. For an agent returning from a booking, consider whether the trip's prior list filters should be restored.
  4. Test the routes separately. Use tree testing to evaluate labels and hierarchy. Use a prototype to test contextual links and direct entry, where placement and screen context matter.

Test whether an agent can open a booking from search, find its trip, and return to the booking list without losing their place.

Sources