Information Architecture
Defining information architecture
Information architecture (IA) is the practice of organizing, structuring, and labeling content in an effective and sustainable way. This guide is intended to help designers and content maintainers make content within the VA mobile app usable and findable to Veterans.
Information Architecture principles
The following guiding principles are used to help Veterans find information and complete tasks within the VA Health and Benefits app:
- Considers the larger VA system: The app’s IA and navigational language consider VA touchpoints, properties and programs outside of the mobile app (digital and physical), with each thing working together as an omnichannel system.
- Consistent sense of place: The app uses multiple wayfinding approaches to communicate where users are now in the app and where they can go from there. Examples of this are displaying global navigation on every screen in the hierarchy, screen names that are unique and descriptive, using common screen transitions to communicate a screen's position in the hierarchy, and including descriptive back labels on each screen.
- Delivers value at every level: Each screen in the app should contain valuable and/or actionable content—no screens that are just lists of links.
- Extensible: The app’s IA and navigation model leave room to expand its feature set by considering and anticipating future organizational needs.
- Informed by Veterans: IA decisions are based on user research conducted with Veterans, examining their mental models around the organization of common tasks and undertanding of labels, as well as getting feedback on proposed solutions.
- Keeps it simple: Content is prioiritized and includes only what’s absolutely necessary—the fewer elements (number of levels in the hierarchy, number of screens, number of links on a screen) the better.
References: VA.gov Information Architecture (IA) team Best Practices for IA on VA.gov VA.gov Design principles
When to think about IA
- Launching a new feature in the VA Health and Benefits app
- Adding a new category or subsection to the VA Health and Benefits app
- Rewriting content and needing to split or merge an existing screen
- Looking to improve the findability of an existing feature and/or screen
- Removing a feature and/or screen
- Changing the UX of global navigational elements (i.e. tab bar/bottom navigation, top bar, including treatments for back buttons, contextual actions and screen titles)
IA documentation
Understanding what’s guiding the app’s current information architecture and make future decisions that are in line with the existing organization, navigation, labeling, and indexing systems.
Sitemap/flow diagram
A sitemap is a planning tool that visually shows how information will be grouped and labeled, where content will be located, and how a user will move through the app. This adaptation of a standard sitemap includes the system display logic for screens that have variants, key actions (buttons, links), common processes and points where it makes use of native mobile integrations. This is the source of truth for the app’s IA.
VA Mobile App - Detailed sitemap 2.0 (FigJam)
Taxonomy description
The VA Health and Benefits app’s IA contains four top level categories: Home, Benefits, Health and [Payments]. Each category contains at least two features and/or subcategories. Features within each category should be grouped into subsections if the number of features in a category exceeds six.
Top level categories and contents
- Home: The app’s default screen—displays a combined, personalized view of the information (and tasks) most relevant to the individual Veteran from across the VA, plus persistent access to general VA info (ex: contact and location finder) and lesser used features like Profile and Settings.
- Profile (Subcategory): Infrequently updated items like personal information (such as contact information, military information, DOB) that isn’t specific to a single category and app settings.
- Health: All health-related features and statuses.
- Features: Appointments, Prescriptions, VA vaccine records, Messaging (future: Medical records).
- Benefits: All benefit-related features and statuses that are not health-related.
- Features: Disability rating, Claims, VA Letters (future: Education)
- Payments: A unified section for managing financial information from across the VA.
- Features: VA payment history, direct deposit information (future: Medical copays, Bills, Travel reimbursements).
Adding new items to the app’s Information Architecture
- A feature’s placement within the app’s navigation and taxonomy should take user mental models, business goals, and the feature type into account. Determining Navigation and Information Architecture Placement for New VA Mobile App Features is a guide intended to help teams decide where a new feature belongs in this app’s sitemap and navigation model.
- Always try to find a placement in an existing category first before proposing a new top-level category for a feature. Confirm new category names and contents with card sort research before adding to the app.
- Within a category, keep the hierarchy as flat as possible in terms of screens (limit the levels it’s possible to drill down through in order to get to child screens), but without inlcuding too many options on a single screen.
- If there are many features within a category, group the features and label the groups at category level before introducing additional levels into the screen hierarchy—this helps avoid cognitive overload.
- All features in the VA mobile app should have a primary placement within the app’s taxonomy, even if there are multiple entry points for it at different locations within the app (example of secondary entry points: personalized home screen content, cross-references within other sections).
- When content outgrows the current category structure, conduct card sort research to determine new category names and contents (Avoid using “hamburger” and “more” menus as primary navigation).
Background
The VA Health and Benefits app’s Information Architecture and navigation model are based on the findings and output from a multi-stage, collaborative and cross-functional design and research process: Information Architecture and Navigation - High Level Project Summary
- Phase I: Two rounds of card sorting (open and closed) with Veterans
- Phase II: Navigation model design exploration, audit and comparative analysis
- Phase III: Evaluative testing with Veterans, including a usability study of the proposed navigation model and sitemap reflected through a low-fidelity prototype