The playbook
Website Navigation: Template and Field Guide
This website navigation template turns a broad task into a record another person can use. It captures label, destination, device, then connects that information to a decision. Copy the table into your working document or system and create a separate record for each item in scope.
Put the task in context
Check the menu with a keyboard, on a phone, and with long labels. The mobile control should expose the destinations and communicate its expanded state. Ensure visitors can close it and continue without getting trapped behind an overlay.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| label | Record the label associated with this page or interaction record. Use a stable reference so later updates can be matched. |
| destination | Record the destination associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| device | Record the device associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| test result | Record the test result associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| Decision field | Entry instructions |
|---|---|
| Observed problem | Describe the actual condition and where it was observed. |
| Recommended action | State the smallest action that resolves the documented problem. |
| Evidence | Link to the record, observation, or test supporting the action. |
| Owner and next review | Name the accountable person and when the decision should be revisited. |
How to complete the worksheet
Begin with label. Use the same reference throughout the record so notes are not attached to the wrong item. Then choose labels that match customer language. This establishes the information required before the worksheet becomes a request for action.
Next, limit ambiguous overlapping menu choices. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as hiding the only navigation when the desktop menu collapses, rather than a broad instruction to “improve performance.”
Finally, test keyboard touch and narrow-screen behavior. Put provide an accessible mobile menu with the same essential destinations in the action field only when it addresses the observed condition. If the problem is different, change the action. The template is a structure for judgment, not a reason to apply the same fix everywhere.
Illustrative completed decision
| Part | Illustrative entry |
|---|---|
| Problem | Hiding the only navigation when the desktop menu collapses |
| Action | Provide an accessible mobile menu with the same essential destinations |
| First check | Choose labels that match customer language |
| Follow-up check | Test keyboard touch and narrow-screen behavior |
| Outcome to define | navigation success rate |
Adapt the fields without losing meaning
You can add fields required by your team, but each should change a decision or preserve necessary context. Keep factual observations separate from recommendations. If destination changes, record the new value and its effective date instead of silently rewriting the context of an earlier decision.
Use the record in a handoff
Ask the receiving owner to explain the next action using only the worksheet. Missing context becomes visible quickly during that exercise. Repair the record before applying the structure to a larger batch. Keep navigation success rate connected to the item so the team can later assess whether the action was useful.
Verify the actual visitor journey on a narrow screen and with a keyboard. A design can look complete while hiding an unreachable control or a missing confirmation. Record the task attempted and what happened at the end.
Skip the manual steps. Let AgentixHUB run this for every client.
Start now