01
The challenge
Find what made the new CARD site hard to navigate or trust, and give the team a clear list of content and usability changes — without organizational bias.
UX research case study
Testing the newly launched NIH Center for Alzheimer’s and Related Dementias site with internal staff and researchers
NIA asked IQ Solutions to test the recently launched Center for Alzheimer’s and Related Dementias (CARD) website. I ran moderated sessions with CARD staff and researchers to check site-wide usability and key flows — then turned those sessions into findings, content and IA recommendations, and a phased next-step plan.
01
Find what made the new CARD site hard to navigate or trust, and give the team a clear list of content and usability changes — without organizational bias.
02
Four 60-minute Microsoft Teams sessions, a drafted moderator’s guide, and research questions on findability, comprehension, and confidence to collaborate.
03
Eight recommendations across imagery, information architecture, and collaboration — plus a roadmap to revise mockups and implement updates with CARD.
4
Participants
CARD staff and researchers
60 min
Session length
Moderated on Microsoft Teams
8+
Ease of use
Every participant rated 8–10
8
Recommendations
Content and usability, unranked

N = 4 of 5 planned
CARD staff recruited four internal participants. I drafted the moderator’s guide, outlined goals, and ran 60-minute sessions. The work surfaced priorities, internal pain points, and barriers to using the live site.
Find · understand · apply
Could people find content and features through search, top nav, side nav, and breadcrumbs? Was copy long, short, confusing, or missing? After a visit, could they describe CARD’s mission and feel confident collaborating with staff or researchers?
Supporting data & analysis
Most participants wanted the homepage hero — and images sitewide — replaced. The lecture-hall photo felt like architects at a drafting table, not neurons, lab work, or the mission in the hero copy. The Mission and Philosophy button was still the first thing people wanted to click, and everyone understood where it went.
Participant voice
“Not a big fan of the picture, this looks more like architects designing or drafting. Scientists don’t all gather around and look at illuminating tables.”
Supporting data & analysis
Once people scrolled past the hero, the Collaborate cards restated the same destinations as the top nav. That made the section feel redundant. Spotlight and CARD News were the parts people wanted higher — Spotlight especially, over Collaborate.
Participant voice
“Is this the same or is it different than the top navigation? I expected it to be something different.”
Supporting data & analysis
Data Science and Data Resources sounded like raw datasets. People found tools (CRISPBR, GenoML) useful, but they were unsure which nav item to trust. “Program” read like a degree track. Long-read Sequencing sat next to Data Science in Research Programs, which made the difference between a method and a program unclear.
Participant voice
“This isn’t data — it’s things to help me manage my data. As a new employee, I may want to know where all the data is stored.”
Hero and research photos felt off-topic; people asked for brains, neurons, lab work, or figures.
Collaborate with CARD mirrored the top nav, so the purpose of the section was unclear.
Two nav items overlapped. Users preferred Data Science and expected raw data that was not there.
Long-read Sequencing was hard to place next to Data Science; “program” sounded like training.
People would forward URLs, but wanted a share control or a group contact on research pages.
CARD News was easy to use, but people assumed research highlights and papers would live there.
Align each page’s image with the topic. Real lab or figure imagery would carry CARD’s collaborative and scientific message better than a generic hall.
Stop repeating top-nav categories. Cards for visiting scientists or recent developments would give people a reason to scroll.
Call it Data Resources, fold or move Data Science, and drop “program” when the page is a set of tools.
More than five programs in the nav will get heavy. A landing page can hold Long-read Sequencing, AutoTAC, and future work without flattening methods into the same list.
It was last in the nav and first in the hero. Pair it with About, or move it up so importance matches the click path.
Add share, contact, and read-more actions so collaboration is not limited to copying a URL. Keep training pages long — people wanted requirements up front.
Evidence-based next steps
Every participant rated the live site at least 7 for explaining who CARD is, and at least 8 for ease of use. The gaps were imagery, repeated IA, and unclear data labels — not a broken mental model. IQ Solutions took those eight recommendations into the annual roadmap, revised mockups, and planned implementation with CARD.