What's a good way to design a menu in which some menu items are dependent on others?

by Nathan Friend   Last Updated April 24, 2018 19:16 PM

My company likes to design interfaces with side menus that look like this:

A side menu

The problem with this design is that it allows the user to click on links like "Profile" before they've selected which profile they want to view. This leads to confusion - new users naturally try and click directly on the "dependent" links (e.g. "Profile") when searching for detailed information in the app.

To solve this, we typically do one of two things:

  1. Disable the dependent links (like "Customers → Profile" or "Customers → Orders") until the user has visited the search page ("Customers → Search")
  2. Leave the dependent links enabled, but automatically redirect the users to the relevant search screen if they haven't previously selected an entity.

As a side-effect, this design introduces a concept we call "context" - clicking the "Customers → Profile" link brings up the customer currently "in context" (i.e. most recently selected from the search screen). While this behavior can be handy at times, it can also lead to some confusion and some tricky edge cases.

How can I redesign this application flow to avoid the issues described above? I'm open to all ideas, even if they don't directly involve the menu structure.



Related Questions


Duplicate links in a navigation structure

Updated April 25, 2017 14:16 PM

Good usage of top AND left hand navigation?

Updated August 02, 2016 08:06 AM

Parent and child navigation organization

Updated August 24, 2016 08:06 AM

Which is the best Side Menu or Fixed Bottom Menu?

Updated September 29, 2017 04:16 AM