NVIDIA External Benefits Website

Overview

From June 2024 to September 2024, I interned on NVIDIA's Benefits Team, helping to align their communication strategy with the goal of enhancing benefits communication, including information about programs and policies, monthly events and annual open enrollment, internal websites regarding specific programs.

The Benefits Team manages NVIDIA's external-facing website for current and prospective employees to learn about the benefits the company offers. This website's navigation was cluttered, with users unable to see all the menu items in the main navigation unless they zoomed out to at least 65% on their web browsers. Disorganized website navigation led employees to be confused about how to find the information they needed.

Similarly, many of the pages on the site had not been updated in three months, leading to outdated information. In addition, the language on the site was complex, resulting in employees not fully understanding benefits programs.

Main Navigation Reorganization

I reorganized the main navigation by following UX design best practices, namely:

• Navigation tiers: I used flyouts to create more tiers of navigation, making it so all the menu items are visible when the user's browser zoom is at 100%.

• Alphabetized navigation: For menus with more than 20 items, it's a best practice to alphabetize the menu items.

I used Google Sheets to iterate through different options for how to reorganize the navigation, which helped maintain comprehensive documentation of my work, and documented my rationale for design decisions on a Google Doc for effective project communication. Following UX design best practices helped me effectively organize the main navigation so it's more user-friendly, while also garnering stakeholder approval.

The homepage of the NVIDIA U.S. benefits website. At the top is the reorganized main navigation.

Webpage Updates

The team maintained a Google Sheet to track updates to the external benefits website. Using this spreadsheet, I kept track of when pages had been updated, who I worked with to review and finalize edits, and the status of the page.

Here is an overview of the process I used to update over 15 different web pages:

1. Make edits to the Google Doc template of the webpage, highlighting my changes in yellow and coloring the text bright red for visibility and ease of collaboration with the Web Development Team.

2. Reach out to the appropriate program manager (i.e. the team member in charge of managing the program the page discusses) to schedule a meeting to review my edits. Log the date of review on the Google Sheet tracker.

3. Review my edits line-by-line with the program manager, aligning on the edits that will be published. Log the date of finalization on the Google Sheet tracker.

4. On a weekly basis, socialize all the pages I updated, whether pending synchronous review by a program manager or greenlit for publication, with the project manager to send the pages for updating by the Web Development Team.

Being proactive in editing pages, communicating with stakeholders, and organizing project materials and schedules helped me efficiently update over 15 different external web pages. This in turn helped employees learn more about their benefits programs and related policies.

Conclusion

My structured, user-friendly approach to content design enabled employees to more efficiently look for information on their benefits, and empowered them to learn about benefits programs—a task that was especially important with the upcoming open enrollment period in November.

If I were to redo the main navigation reorganization, I would want to conduct user research—in particular, card sorting, to get a sense of users' mental models for how they search for information on the external benefits website. With card sorting data, I could align the design of the main navigation with their mental models, ensuring a research-backed approach to greater user-friendliness.