Building Navigation Based on User Tasks Instead of the Company Organizational Chart

How do you translate user tasks into navigation instead of simply displaying the organizational chart?

The visible navigation is built from recurring user tasks and understandable target group terms. Internal teams retain their operational responsibility but do not determine the entry logic; prototypes and task tests verify whether content can be found without organizational knowledge.

Department as the Entry Point

• Department as the Entry Point People need organizational knowledge before they can find a service, answer, or point of contact.

• Research Anecdote – Isolated, loud statements replace the systematic review of recurring tasks and actual navigation paths.

• Political Menu Item – Internal interests create equally ranked sections without clear user needs and clutter the main navigation.

Practical Example: “Department as Entry Point”

A website categorizes offerings into Sales, Operations, and Consulting – terms that are of little help to outsiders. Real tasks, however, are grouped around Launch, Integrate, and Improve; internal teams retain their responsibilities within the CMS, while the visible navigation reflects the problem-solving path.

Observed Main Tasks

• Stable Content Assignment – Every piece of content has a clearly defined location within the visible task structure, even if multiple teams are internally responsible.

Understandable Vocabulary

1. Collect core tasks from search queries, support cases, conversations, and observed user paths as problem formulations.

2. Transfer tasks into user-friendly groups and labels using open card sorting and comprehension tests.

3. Separately assign content and internal responsibilities, test prototype navigation, and visibly decide on policy exceptions.

Stable Content Assignment

• Success rate of representative user tasks where the target area and specific content are found without knowledge of internal teams.

• Number of main navigation items whose existence is solely due to organizational responsibility and not based on a documented user task.

Which decisions "Building Navigation Based on User Tasks" complements

Precisely Formulating Microtexts for Buttons, Fields, and Hints delves deeper into the checkpoint "Observed Main Tasks." The guiding question is: How do you formulate precise microtexts for buttons, fields, and hints?

A complementary perspective is offered Translating a website from a business model to a site structureIt answers the question: "How does a business model translate into a user-oriented website structure?"

If you want to practically implement "Building Navigation Based on User Tasks," you can refer to Robust Website Systems This focuses on "Navigation, Search, and Orientation" and "Observed Main Tasks."

Conclusion: Building Navigation Based on User Tasks

Navigation is a model of user tasks, not an organizational chart. Internal responsibility remains important but should not become a prerequisite for orientation.

Sources and Further Information

The classification of "Building Navigation Based on User Tasks" is based on the following official documentation and standards.

• Breadcrumbs – GOV.UK Design SystemOfficial criteria for the use, structure, position, and mobile behavior of breadcrumbs.

• Menu Structure – W3C Web Accessibility InitiativeOfficial W3C guidance on semantic menu structure and the understandable labeling of navigation.

• Navigate a service – GOV.UK Design SystemOfficial template for task-oriented top-level links, service navigation, search, contact, and the delineation of linear processes.