The playbook
Website Navigation: Checklist
Use this website navigation checklist before a new release, a handoff, or a scheduled review. Its purpose is to verify the decisions that affect navigation success rate. Check an actual page or interaction record; a box marked complete without evidence does not show that the customer journey works.
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.
Before you use the checklist
Name the exact item being checked and its purpose. Gather label, destination, device, test result. If one of those details is unknown, mark it as unknown and assign a way to resolve it. An invented value makes the checklist look complete while weakening every later decision.
Working checklist
| Check | Evidence to keep | Responsible role |
|---|---|---|
| Choose labels that match customer language | A dated observation showing how label was verified | website lead |
| Limit ambiguous overlapping menu choices | A dated observation showing how destination was verified | designer or developer |
| Test keyboard touch and narrow-screen behavior | A dated observation showing how device was verified | site owner |
Check the failure path
- Look specifically for this failure: hiding the only navigation when the desktop menu collapses.
- Provide an accessible mobile menu with the same essential destinations. Record the actual correction, not just the intention to make it.
- Repeat the affected task after the correction and check test result.
- Make sure the next owner can find the decision and supporting evidence.
Use three outcomes for each check
Mark an item as complete only when the expected behavior or information has been observed. Mark it as incomplete when a required condition is absent. Use not applicable when the condition genuinely does not belong to the chosen scope, and write a short reason. These states keep a review useful without forcing every process into an identical mold.
For example, if the check is “Choose labels that match customer language,” a meeting about the subject is not the evidence itself. Retain the relevant label and destination, the decision made from them, and the result of checking that decision. The record should allow someone who missed the meeting to understand what changed.
Decide what must be resolved first
An incomplete item that prevents make important destinations discoverable through clear menus and links deserves attention before a cosmetic improvement. Assign an owner and a next action to that issue. Keep optional refinements visible, but do not let them obscure a failure in the core process.
Close the review
Recheck corrected items and note anything still uncertain. The checklist is finished when the next owner understands what was verified and what remains open. Follow navigation success rate using a consistent definition so later reviews can connect execution quality with useful results.
Design recovery as part of the experience. People enter incomplete information, use slow connections, and return to interrupted tasks. A clear error and a preserved input are often more useful than another decorative element.
Skip the manual steps. Let AgentixHUB run this for every client.
Start now