Redesigning the Login.gov Help Center

Experience
Content

Background

In late 2024, I joined Team Annie at Login.gov with the goal of redesigning the Login.gov Help Center. At the time, user satisfaction with help articles was low (averaging 48%), leading to an increased burden on the contact center team due to a higher volume of calls.

Project Overview

In my role as UX designer, writer, and researcher, I spearheaded a complete overhaul of the Help Center to improve online support for users facing authentication and identity verification issues.

The Challenge

How might we ensure Login.gov users can easily and quickly get the right information at the right time, enabling successful task completion without needing additional support? Here's why it matters:

The Help Center of 2024

Outside of help article additions and updates, the original Help Center has not had a design update since its inception in 2021. The video below demonstrates a user attempting to find a solution to an authentication issue using the original site.

To find their specific help topic, they have to know whether it's under one of the five categories. Then we hope they even notice the right side navigation where their article may be. Once they're in the help article they might have to scroll through a large amount of content before finding relevant troubleshooting information.

Comparative Analysis

To get some inspiration, I performed a detailed comparative analysis of 10 industry-leading help centers including Google, Apple, Paypal, ID.me, Microsoft, Amazon, FedEx, Wealthfront, Dyson, and Samsung. Below are some of the best practices I identified from my analysis.

1. Popular questions and FAQs are displayed upfront

9/10 help sites featured popular issues or FAQs prominently at the top of the page. 5/10 framed these as “Popular topics”, “FAQ”, “Common questions”, or “Trending Topics”.

2. Question-based article titles over technical titles

7/10 help sites framed user issues through first-person questions like "What do I do if..." or "I can't sign in..."
The original Login.gov help center used second-person language like "Add or change your authentication method" or impersonal titles like "Help with agencies".

3. Progressive disclosure reduced cognitive overload

6/10 help sites utilized the principle of progressive disclosure through collapsible accordions or paginated, step-by-step processes.
This makes it easier for users to process information and make decisions to find solutions on their troubleshooting journey.

4. Left side navigation was standard

8/10 help sites featured a persistent left side navigation or related articles section within the context of a help article.
It was doubly important that we switched over to a left side navigation since it was a U.S. Web Design Systems standard.

Designing Prototype B

This design prototype prioritized speed and scannability by highlighting the most likely issues on the landing page, nesting detailed information within accordions, and creating navigation subsection links.
Popular topics on the landing page: By using the first-person question framing, the user should have an easier time finding the specific help article related to their issue.
Accordions contain additional detailed information: Longer help articles could be broken up into smaller sections using accordions to help with scanning.
Left side navigation with anchor links to subsections: Users can easily scan and quickly navigate to the relevant section of the article by clicking on the subsection titles in the navigation.

Designing Prototype C

This design emphasized granularity by segmenting troubleshooting into a step-by-step diagnostic process. Users would be asked a series of questions and be given simple instructions before taking them to a longer form help article.
This approach was inspired by Dyson and Amazon's conversational approach to troubleshooting, thus making the experience less overwhelming for users.

Usability Testing Results

We conducted a remote moderated A/B/C usability test with 12 participants on desktops, comparing the existing help center (A) against the two prototypes (B and C). Participants were split into four groups: A/B, B/A, A/C, and C/A. This was done to reduce potential recency bias.

Finding #1: Framing articles as user questions improved clarity and speed

"I feel like I’m on the right page because I see that this is my question."
Takeaway: Titles like “I’m having trouble with face or touch unlock" helped users find the right article faster than generic titles like “Authentication methods.”

Finding #2: Accordion layouts improved scannability

"I like the ability to collapse... looking through 5 or 6 dropdowns makes it easier."
"Long pages are overwhelming—I just scroll and hope something jumps out."

Takeaway: Users preferred content broken into collapsible accordions (Prototype B), which reduced cognitive overload and helped them zero in on relevant solutions.

Finding #3: Users wanted step-by-step troubleshooting, not just definitions

"It’s telling me how to set it up, but not how to troubleshoot."
"What action do I take if I’m having trouble logging in? It just says what it is, not how to fix it."

Takeaway: Users would mistakenly land on irrelevant definitional articles when looking for solutions. Users wanted troubleshooting content to be more prominent and distinct from informational articles. Prototype C had the added benefit of being a dedicated diagnostic flow that users.

Finding #4: Visual aids increased comprehension

"This is the clearest guide I’ve seen for how to take photos of your ID."
"The green ‘do’ and red ‘don’t’ made it super obvious what to do."

Takeaway: Image examples labeled with "Do" and "Don't" captions were well received by participants. Visual communication is especially helpful for users with limited English or digital literacy.

Finding #5: Left side navigation matched user expectations

"It seems funny that all of these topics are on the right side. I’m used to seeing them on the left."
"Left side nav makes it easier to scan and jump between sections."

Takeaway: The live site’s right side nav was often missed. Left side navigation aligned with USWDS patterns and user mental models.

Finding #6: Both prototypes were preferred over the current experience

"It was easier. You're taking me through the steps to solve my problem instead of leaving me to figure it out."
"I like that I’m not just set free on a website—I’m being guided."

Takeaway: 10 out of 12 users favored the prototypes, noting quicker task resolution and improved ease of use. These insights demonstrated clear advantages of the redesigned prototypes over the existing help center, validating our design hypotheses.

Implementation

After the usability study, the team decided to implement Prototype B's design since it performed the best and could be more easily rolled out in stages.
The redesigned Login.gov Help Center is set for partner preview and phased release in August 2025. Team Annie will look to continued refinement based on user satisfaction scores, clickthrough rates, and any fluctuations in contact center calls by topic.
This redesign let me lead deeply across content strategy, interaction design, and user research. Our comparative analysis and usability testing enabled us to make targeted improvements that helped users get to their answers faster, feel more confident, and reduce the burden on support teams.

Interested in collaborating?
Schedule a free consultation.