# Mobile Navigation [Image] Mobile navigation determines how easily users can move through a site and access the content they need. For product designers and managers, the challenge is ensuring navigation is intuitive, efficient, and accessible on smaller screens where space is limited. Mobile Navigation Testing uses a design stack of UX metrics: usability, success, and satisfaction to measure how effectively the navigation supports user needs. This approach replaces subjective opinions with measurable insights. With these findings, designers and managers can make informed design decisions, prioritize improvements, and demonstrate the impact of changes on business outcomes. For example, testing Indiana University’s mobile navigation for their online college site revealed high satisfaction but lower usability and success, showing where refinements were needed to improve clarity and reduce friction in the student experience. * * * ### Define Goals for Your Mobile Navigation Test A mobile navigation system should balance user needs like clarity, speed, and accessibility with business goals such as engagement, feature adoption, and retention. Measuring navigation success ensures mobile experiences feel seamless and business outcomes are met. **Audience** To define user needs, you first need to establish who your audience is. In the case of our Indiana University example, we targeted current and prospective online college students. **User Needs** As a customer using mobile navigation, the five most important needs would be: 1. The navigation should be simple, clear, and easy to operate with touch gestures. (Navigation should be [**Usable**](https://glare.helio.app/define/user-needs/usable)) 2. Pages, features, and content should be easily located without unnecessary searching. (Features should be [**Findable**](https://glare.helio.app/define/user-needs/findable)) 3. The structure should instantly make sense, with common actions placed where users expect them. (Navigation should be [**Intuitive**](https://glare.helio.app/define/user-needs/intuitive)) 4. Navigation should minimize taps, scrolling, and load times to help users move quickly. (Navigation should be [**Efficient**](https://glare.helio.app/define/user-needs/efficient)) 5. The navigation should be designed so everyone, including those with disabilities, can fully participate. (Navigation should be [**Accessible**](https://glare.helio.app/define/user-needs/accessible)) These five ensure mobile navigation feels simple, predictable, and inclusive, making it easy for users to get where they need to go. **Business Goals** Here are the five most important business goals for mobile navigation: 1. **Increase Engagement** – Encourage users to explore more features and content through seamless navigation. 2. **Improve Retention** – Reduce churn by making it easy for customers to consistently find value on mobile. 3. **Boost Feature Adoption** – Surface new or important features in logical places so they are more likely to be used. 4. **Reduce Friction & Support Costs** – Minimize frustration and confusion that lead to drop-offs or customer service inquiries. 5. **Gather Navigation Insights** – Collect behavioral data on navigation patterns to refine menus, IA, and design strategy. These goals help the business drive engagement, reduce friction, and strengthen loyalty through effective mobile navigation. * * * ### **Choose Metrics to Test Your Mobile Navigation** For Indiana University’s mobile navigation, a design stack of three UX metrics was chosen to measure how well the menu supports prospective students in finding key information. This stack — Usability, Success, and Satisfaction — was established by mapping user needs directly to measurable outcomes: - [**Usable**](https://glare.helio.app/define/user-needs/usable) **&** [**Intuitive**](https://glare.helio.app/define/user-needs/intuitive) **→** [**Usability**](https://glare.helio.app/define/ux-metrics/behavioral-metrics/usability)
 Students need a navigation that feels simple and predictable. Usability measures whether participants can operate the menu easily and understand how it’s structured. - [**Findable**](https://glare.helio.app/define/user-needs/findable) **&** [**Efficient**](https://glare.helio.app/define/user-needs/efficient) **→** [**Success**](https://glare.helio.app/define/ux-metrics/behavioral-metrics/success)
 Visitors should be able to quickly locate key actions like costs, applications, or campus culture. Success evaluates whether participants can find the right destination on their first attempt. - [**Accessible**](https://glare.helio.app/define/user-needs/accessible) **→** [**Satisfaction**](https://glare.helio.app/define/ux-metrics/attitudinal-metrics/posttask-satisfaction)
 The navigation should be inclusive and work smoothly across mobile devices. Satisfaction reflects whether participants describe the experience as clear, easy, and stress-free after using it. * * * ## **Establish Hunches to Direct Your Testing** Mobile navigation is a critical part of helping students explore programs, understand costs, and find support services. By starting with hunches about where usability or clarity may break down, we can then form questions to validate those assumptions with users. **Example: Indiana University Mobile Nav**

Hunches

Questions

UX Metric

Important cultural/contextual content like Campus Life is pushed to the bottom, so users may overlook it when trying to learn about the school.

“Where would you click to learn more about the culture and student experience at this university?”

Success

The navigation mixes high-priority tasks (Admissions, Cost & Financial Aid) with general info sections (Research, About), which may cause students to hesitate or mis-click.

“Was it clear where you should go first if you’re considering applying to IU?”

Success

The expand/collapse arrows may not clearly indicate that multiple options exist under each category, leading to missed navigation paths.

“Did you notice there were additional pages under Academics and Admissions?”

Success

The utility CTAs at the bottom (“Request Info,” “Apply,” “Give”) may be too subtle to attract attention, lowering conversion for the most critical actions.

“How easy was it to find the option to apply?”

Usability

Overall structure may feel long and overwhelming on mobile, causing friction in quickly finding what matters most (e.g., majors, tuition, deadlines).

“How easy or difficult was it to find the information you were looking for?”

Satisfaction

These hunches help uncover whether the mobile nav meets user needs for being usable, findable, intuitive, efficient, and accessible, all of which directly impact engagement and conversions on mobile. * * * ## **Turn Hunches into Test Questions** Turning these metrics into participant questions transforms design assumptions into measurable signals. Each metric uses a specific question type paired with a clear example from Indiana University’s mobile navigation: - [**Success**](https://glare.helio.app/define/ux-metrics/behavioral-metrics/success) **(Click test directive)**
 *Question type:* Task-based click test.
 *Example:* “Where would you tap to find information about tuition and fees?” [Image] - [**Satisfaction**](https://glare.helio.app/define/ux-metrics/attitudinal-metrics/posttask-satisfaction) **(Likert scale)**
 *Question type:* Satisfaction scale.
*Example:* “Overall, how satisfied are you with the ease of finding information in this mobile menu?” (Very Dissatisfied → Very Satisfied) [Image] - [**Usability**](https://glare.helio.app/define/ux-metrics/behavioral-metrics/usability) **(Average success across tasks)**
 *Question type:* Multi-task click test.
*Example:* “Where would you tap to explore undergraduate programs?” followed by “Where would you tap to access student resources?” (Success rate is averaged across tasks) [Image] * * * ## **Calculate UX Metric Scores from User Feedback** We tested Indiana University’s mobile navigation with 100 online college students, and their responses were measured and converted into UX metric scores on a 0–100% scale. Each metric in the design stack was scored using task completion rates and survey questions, then rated against the following benchmarks: - **Very Good** = 90% and above - **Good** = 70% to 89% - **Average** = 50% to 69% - **Poor** = 30% to 49% - **Very Poor** = below 30% Once the individual UX metric scores are calculated, the average of those scores are used to determine the overall score for the user experience. Here’s how the mobile navigation performed: - [**Success**](https://glare.helio.app/define/ux-metrics/behavioral-metrics/success) **(88% — Good):** Most participants successfully found the key pages and actions they were tasked with, though some friction points remain with certain lower-priority navigation items. - [**Usability**](https://glare.helio.app/define/ux-metrics/behavioral-metrics/usability) **(76% — Good):** The navigation layout and structure are generally clear, helping users move efficiently, but a few participants noted extra taps were needed to reach some pages. - [**Satisfaction**](https://glare.helio.app/define/ux-metrics/attitudinal-metrics/posttask-satisfaction) **(87% — Good):** Users rated the mobile navigation experience positively, often describing it as straightforward and easy to use. [Image] These results produced an overall test score of 84%, Good. Indiana University’s mobile navigation enables students to reach important content with confidence and ease, while leaving a positive overall impression. Continued refinements to reduce extra steps and surface lower-engaged links more effectively could help push performance into the Very Good range. Click here to check out the [raw survey data and UX metric scores for Salesforce's landing page](https://my.helio.app/report/01JF90WE33GW39H8VTQ5QF474R). * * * ### Draw Signals from Your Design Stack Here’s how signals were surfaced from Indiana University’s mobile navigation test results by following these five steps: 1. **Focus on poorly scoring metrics** [Image] Although the overall scores for SUCCESS (88%), USABILITY (76%), and SATISFACTION (87%) landed in the Good range, closer inspection reveals a weak spot: only 42% of participants successfully identified the Campus Life page as the destination for learning about school culture. This result falls well below the expected 70% success benchmark, pointing to a navigational gap. 2. **Identify patterns across metrics** [Image] Patterns show that Indiana University’s mobile navigation works well for high-priority functional tasks (costs, applications), but struggles to guide users to exploratory or cultural information. The discrepancy suggests that while core paths are designed effectively, secondary or less direct goals may not be as discoverable. 3. **Determine if user needs are being met** [Image] - [**Usable:**](https://glare.helio.app/define/user-needs/usable) *Met.* Strong satisfaction scores and simple layout show users found the navigation clear and easy to operate. - [**Findable:**](https://glare.helio.app/define/user-needs/findable) *Partially met.* While costs and applications were easily located, Campus Life content was much harder to find, with only 42% success. - [**Intuitive:**](https://glare.helio.app/define/user-needs/intuitive) *Partially met.* The structure matched expectations for key transactional tasks but failed for cultural content, indicating inconsistencies in intuitive flow. - [**Efficient:**](https://glare.helio.app/define/user-needs/efficient) *Met.* High success on priority tasks like costs and applications demonstrates quick, low-effort navigation. - [**Accessible:**](https://glare.helio.app/define/user-needs/accessible) *Met.* Layout simplicity and ease of use support accessibility across user groups. **4\. Compare outcomes to your business goals** - **Increase Engagement:** Limited — cultural content like Campus Life is under-discovered, reducing engagement beyond core tasks. - **Improve Retention:** Supported — strong usability for cost and application tasks reduces friction for critical journeys. - **Boost Feature Adoption:** Weak — lower success in finding Campus Life content limits exposure to secondary features. - **Reduce Friction & Support Costs:** Supported — clarity around costs and applications minimizes confusion for prospective students. - **Gather Navigation Insights:** Limited — friction around Campus Life weakens insights into student interest beyond transactional actions. **5\. Surface signals & establish a direction Signals derived from the data:** 1. **Cultural content is hidden from users** — Campus Life’s low discoverability shows students miss key engagement opportunities. 2. **Core transactional tasks are a strength** — high success locating costs and applications ensures essential flows are supported. 3. **Satisfaction remains high despite gaps** — users appreciated the navigation’s overall simplicity and clarity, even if not all needs were met. **Direction based on business context:**
 To align with Indiana University’s goals of increasing engagement and boosting feature adoption, design priorities should focus on: - Improving visibility of Campus Life and cultural content without disrupting navigation for transactional tasks. - Adjusting hierarchy and placement of secondary links to align with user expectations. - Preserving the straightforward layout that underpins strong usability and satisfaction. Based on the signals and design direction, we created an updated version of the design with the expected UX metric improvement: [Image] The direction is clear: *Indiana University's mobile navigation supports key transactional flows but underserves cultural discovery. Elevating visibility for Campus Life content will strengthen engagement and better align the navigation with long-term retention goals.* * * *