Navigation design deliverables move through increasing fidelity: sketches, then wireframes, then mockups, then interactive prototypes. Which fidelity is appropriate depends on the audience and the moment, echoing a principle that runs throughout this course, a rough sketch can align a team quickly in an early ideation session, while a fully annotated wireframe or clickable prototype is what a development team actually needs to build something correctly, especially without ongoing access to the design team during implementation. Reusable navigation components and wireframe templates speed up producing these deliverables consistently across many pages.
Presenting this work well matters as much as producing it. Facilitating a design review means setting a clear agenda and specific goals for the feedback being sought, and running an effective critique means keeping feedback focused on the work itself rather than the person who made it, pushing for specific and actionable comments rather than vague reactions, and making sure everyone in the room actually contributes rather than letting one voice dominate.
A wireframe handed to a remote team with no annotations is really just a picture, the annotations are what turn a picture into instructions someone else can actually build from.
1: Low-fidelity sketches or wireframes. When three concepts are still being compared and one or more will be discarded, investing in full mockups or clickable prototypes for all three wastes effort on directions that won't survive the decision. Low-fidelity deliverables let leadership evaluate and choose between the concepts without the team over-investing before a direction is even confirmed.
2: Fully annotated, high-fidelity wireframes. A remote team without ongoing access to the designers needs documentation precise enough to resolve questions on its own, since there's no easy way to just ask. A rough, unannotated sketch or a verbal summary would leave far too much open to interpretation for a team implementing without that safety net.
For the content team, a site map or structural diagram showing exactly what new categories the redesign introduces, and therefore what content needs to be created for them, is the appropriate deliverable. The leadership-facing concept comparison from question 1 is deliberately high-level and built to support a decision between directions; it wouldn't give the content team the structural specificity they need to know precisely which new sections require new content, since that level of detail is exactly what a decision-stage deliverable is meant to leave out.Fill in your own details below; the prompt updates as you type. When it's ready, copy it into Claude or whatever AI tool you use.
Casts the AI as: You're a UX writer specializing in navigation labels and information architecture terminology.
Spells out exactly what to analyze and return.
What this section contains, Current audience and Current problem with label tell the AI what your specific situation is, not a generic one.
Table comparing all variations with recommendation
Fill in your own details below; the prompt updates as you type. When it's ready, copy it into Claude or whatever AI tool you use.
Casts the AI as: You're a UX researcher specializing in information scent and navigation usability.
Names 5 specific outputs to produce, so the response comes back structured rather than a general summary.
Site type, Target audience and User goals tell the AI what your specific situation is, not a generic one.
Structured evaluation with overall score and priority recommendations