Our sample meal-delivery website has a beautifully restrained mobile header. Open its menu and you find “Discover,” “Our World,” “Lifestyle” and “More.”
The customer wants to know whether dinner can reach their ZIP code. The website would prefer to establish a relationship with their aspirations.
This is a fictional example, but the design problem is real: a mobile menu can hide the very choices that would tell someone where to go. Good mobile navigation makes the next useful destination recognizable before people commit to exploring it.
Let’s follow this customer rather than judging the menu by how neatly it closes.
Can someone work out where dinner lives?
The first label asks for a guess
“Discover” might contain meals, delivery areas, a company video or a moving account of our founder discovering vegetables. Its tone is pleasant; its destination is unclear.
A label such as “This week’s meals” carries more information. “Delivery areas” answers a different question and deserves a recognizable route of its own.
Nielsen Norman Group describes this predictive quality as information scent: the clues that help people judge where a link will lead.3 A menu can be visually simple and still provide very little of it.
For a franchise adviser, the equivalent might be “How we help,” “Franchise options” and “Book a call.” The right labels come from the audience’s questions, not a universal list of fashionable menu words.
Planning a new site? See how we approach custom website creation.
The important path is nested inside the general one
In our sample, a person must open Discover, then Lifestyle, then Meal plans before seeing the food. Each level adds a decision before there is much evidence to support it.
Exposing useful categories earlier can shorten that uncertainty. It does not require putting every page into the main menu. A small set of clear starting points can lead to more detailed choices once the person understands where they are.
Think of it as signage in a parking garage. A sign for the exit helps. A sign for “Your onward journey” is technically optimistic, but several of us are still on level three.
Keep navigation separate from filtering. Choosing a meal category and narrowing meals by dietary attributes are related tasks, but they do not necessarily belong in the same branching menu. Forcing every combination into the navigation makes the structure expand very quickly.
Returning should not restart the expedition
Suppose the customer opens a meal, checks the details and returns to the list. Losing their place, filters or menu context adds avoidable repetition.
Within a menu, clear back controls and a visible current level help people understand the hierarchy. Closing the menu should return them to the page predictably. The controls need to work with a keyboard and assistive technology as well as a thumb.
Worth reading next: Your menu labels should sound like the pages people are looking for.
These details are easy to miss in a presentation that only shows the menu open. A navigation system is a sequence of actions, not one impressive screenshot.
For this sample site, I’d test three ordinary journeys:
- Find out whether an address is inside the delivery area.
- Locate suitable meals and open one set of details.
- Return to the selection and continue without rebuilding the search.
Ask people to complete those tasks without naming the links they should use. Watch the first choice and the recovery when it goes wrong. Telling someone to “use Delivery areas” mostly tests whether they can follow an instruction.
Baymard’s ongoing navigation research is useful background, but a benchmark from another group of sites cannot tell us exactly how this audience will behave.1 The actual menu still needs observation.
The improved version needn’t shout. It can remain visually quiet while making meals, delivery information and ordering easy to recognize. That is a rather better use of restraint than asking a hungry person to decode the brand.