The Navigation Budget: Give Every Menu Slot a Clear Job
A practical method for prioritising structure, menu items and user journeys based on what customers actually need to accomplish on a business website.
Category: Web Design and User Experience
The main menu is a limited resource. Yet it is often treated as a table of contents where every department, service and initiative must have a place. The result is long labels, overlapping choices and important customer journeys that disappear among internal priorities.
A navigation budget means that every visible space in the menu must be justified by a clear task. Who is this choice for? What does the user expect to find? What next step should the page support? The method makes it easier to discuss web design based on customer needs, rather than on who is shouting the loudest internally.
The problem is rarely just the number of menu items
A menu with few choices can still be difficult to use. “Solutions”, “Expertise” and “What we do” may, for example, lead to almost the same content. The user has to open several pages to understand the difference.
The opposite problem occurs when the menu mirrors the organisational chart. The customer then needs to know which department provides the service, even though they are simply trying to solve a specific need. The company’s internal structure becomes the customer’s navigation problem.
Good navigation answers three questions without requiring the user to investigate every option:
- Where am I?
- Where can I go next?
- Which choice fits my task?
This requires an interplay between structure, wording, typography, visual cues and content. The menu cannot be fixed in isolation if the pages behind the choices lack a clear purpose.
Start with tasks, not pages
Before designing a new menu, you should make a short list of the tasks the website needs to support. Use real customer enquiries, search terms, questions for sales and customer service, visitor data and insights from meetings. Do not start with an export of the current pages.
Typical tasks on a business website may include understanding a service, assessing whether the provider is a good fit, finding documentation, comparing alternatives, viewing relevant customer cases, contacting the right specialist or applying for a job.
Then prioritise the tasks based on their importance to both the customer and the business. A task that many customers have, but that the company has buried deep in the structure, is an obvious candidate for better placement. A page that is important internally but rarely relevant to visitors does not need to be in the main menu.
Five questions for every menu slot
- What specific user task does this choice support?
- Does the target audience understand the label without insider knowledge?
- Is the choice clearly distinct from the other choices?
- Is there sufficiently good content behind the menu item?
- Does the choice provide a natural path forward?
If you cannot answer clearly, the menu item should be reworded, moved or removed.
Create a structure that can grow
A common mistake is to make room for everything the company offers today, without rules for what comes later. The menu then grows a little every time a new service, campaign or target audience is introduced.
Therefore, define which types of content belong at each level. The first level may consist of broad customer needs or stable content areas. The second level may contain specific services, products or situations. Individual pages for campaigns, expert articles and niche offerings should not normally have a permanent place at the top level.
The structure should also have clear owners. When a new page is proposed, someone must assess whether it belongs in an existing category, replaces outdated content or genuinely requires a new branch. Without such rules, even a well-organised menu gradually becomes unwieldy.
Write labels that reduce interpretation
Menu items are functional copy, not advertising headlines. They should be short, recognisable and precise. Creative wording can work in campaigns, but navigation should use words the target audience already associates with the task.
“Create results with us” says little about what the page contains. “Accounting services”, “IT operations” or “Book a site visit” set a clearer expectation. At the same time, labels should be broad enough to cover the content behind them. A general menu item must not lead to a page about just one narrow service.
Test the words without explanation. Show the labels to someone who knows the customers but has not participated in the project. Ask them to describe what they would most likely find behind each choice. Different interpretations are a sign that the wording needs to be improved.
Let typography show what matters
Navigation is also about readability and visual hierarchy. If all links, buttons, headings and help text compete for attention, the user receives no help prioritising.
Use a limited number of font sizes and weights. Ensure a clear distinction between primary choices, sublevels and supplementary information. Long menu titles should not be squeezed in using very small type. It is better to improve the wording or structure.
Typography must work when the text is enlarged and when the screen is narrow. Text that overlaps, is cut off or hidden can make essential services inaccessible. Readable line spacing and good contrast are more important than making the menu look compact.
Use the visual identity as a guide
Colours, surfaces and shapes should not merely decorate the website. They should make its functions easier to understand. A brand colour can, for example, highlight the primary action, while calmer colours are used for secondary choices. If every element uses the strongest brand colour, it loses its navigational effect.
Be consistent about what looks clickable. Buttons with the same design should have roughly the same function, and standard links should be recognisable as links. Avoid making decorative boxes look like buttons, or clickable elements lacking visible cues.
The active page, open menu levels and keyboard focus must be visible. Do not use colour alone to communicate state. Combine it with shape, underlining, a border or another clear signal.
Make the menu accessible without creating a separate solution
Accessible navigation is not a parallel version of the menu. It is the same solution, built so it can be used with a keyboard, screen reader, enlarged text and different screen sizes.
Test the entire menu without a mouse. It should be possible to open, close and move through all levels in an understandable order. The focus indicator must be easy to see and must not be hidden behind fixed headers or other elements.
On mobile, the menu button must have an understandable name and clearly indicate when the menu is open. Large desktop dropdown menus should not automatically be squeezed onto a narrow screen. Mobile navigation often needs simpler levels, larger touch targets and a clear way back.
Also make sure that contact information and important actions are not available only inside a complicated menu. Users should be able to reach them through the content on relevant pages.
Separate navigation from conversion
The main menu should help users find their way. It should not carry the entire responsibility for conversion. A prominent contact button can be useful, but it does not replace good calls to action within the content itself.
A visitor reading about a specific service needs an action that fits the situation. This could be booking an assessment, requesting a quote, viewing a relevant customer case or contacting a specialist. A general “Contact us” button provides less support because the user still has to formulate their needs on their own.
Place the action after the page has provided the necessary basis for a decision. For a simple service, this can happen early. For a complex purchase, users may first need to understand the offering, who it is for, how the process works and what the next step involves.
Test the navigation with realistic tasks
Do not just ask test participants whether they like the menu. Give them specific tasks and observe where they start, which words they misinterpret and when they go back.
Relevant test tasks may include:
- Find out whether the company provides a specific service in your area.
- Find a customer case that resembles your business.
- Find out who you should contact about a specific need.
- Find information that can be used before a procurement meeting.
- Find a vacant position and see what the application process requires.
Test on both mobile and large screens. Pay particular attention to hesitation, misclicks and words users repeat aloud. These observations often provide more value than general comments that the design looks neat.
Follow up with a few clear metrics
After publication, you should investigate whether important pages are being found, not just how many people visit them. Look for whether users move from overview pages to relevant services, whether they have to use internal search to find key content and where they leave important customer journeys.
Many clicks on a menu item are not necessarily positive. If users open several nearby options before finding the right page, this may indicate unclear labels. Therefore, combine traffic data with observation, search terms and the content of actual enquiries.
A simple deliverable for the next menu review
Conclude the work with a short navigation document that designers, developers and content owners can continue to use. It should include:
- The most important user tasks, in order of priority.
- Approved menu levels and the purpose of each level.
- An explanation of what each main option should contain.
- Rules for naming, visual states and mobile display.
- Planned actions on the most important page types.
- Responsibility for assessing new pages and menu proposals.
A navigation budget does not limit the company’s opportunities. It protects the most important customer journeys from internal complexity. When every menu position has a clear purpose, the website becomes easier to understand, easier to use and better equipped to generate relevant enquiries.
