A navigation system has to satisfy several concerns at once: understanding real user needs through both generative and evaluative research, supporting the genuinely nonlinear way people actually seek information, reflecting the underlying information architecture accurately, providing labels clear enough to scan quickly, and laying elements out consistently enough that their placement itself communicates meaning. The underlying objectives these concerns serve are balancing the breadth and depth of the structural navigation, fulfilling business requirements, and, often overlooked, building the brand's credibility, since a navigation system that works well quietly earns trust with every successful click.
Several concrete guidelines follow from this. Support both vertical movement through the hierarchy and lateral movement across it, without cluttering the interface in the process. Keep breadth and depth balanced at every level. Give the most prominent placement to links leading to the most important content. Group related links together, following the same logic that makes visually proximate things read as related. Keep the layout of navigation elements consistent across the entire space. And always make the user's current location visible, whether through highlighting or breadcrumbs, so they never have to wonder where they are.
Every one of these guidelines can be violated quietly and separately, a navigation system rarely fails because of one dramatic mistake, but because several small violations compound on top of each other.
1: "Book a Flight" lacking prominent placement. The guideline is explicit that the most important content deserves the most prominent placement. Burying the site's single primary conversion action as the sixth item in a dense list directly works against the goal of getting visitors to complete a booking, every extra moment spent scanning for it is an opportunity for someone to give up.
2: Scattered related links. A traveler needing both baggage policy and check-in time information represents exactly the kind of related-task pairing the grouping guideline exists to serve. When those links live in different, disconnected parts of the navigation, customers who can't easily find one while looking at the other are far more likely to just call support instead of continuing to hunt.
A reasonable priority order, given the business metrics described: fix "Book a Flight" prominence first, since it connects most directly to declining conversion, the site's core commercial function. Fix the scattered related-link grouping second, since it connects directly to the rising support costs. The crowded navigation bar and missing location indicators are real violations too, but neither has as clear a direct line to the two specific business metrics given in this scenario, so they're reasonable to address once the two highest-impact fixes are underway.This is the kind of reasoning the source material's objectives section is pointing toward: navigation guidelines aren't equally urgent in every context, connecting each violation back to the actual business consequence it's producing is what turns a list of guidelines into an actionable priority order.