NTAMII: A Document Repository Discovery Shift
Nobody dreams of designing a document repository. But this one held one of the oldest wealth managers' best thinking for its most valuable clients, and almost nobody could find it. In 8 weeks of discovery, I mapped the mess, found the real problem, and designed the structure that had been missing all along.
*This project is under NDA. Some visuals have been withheld or abstracted. Reach out to hear more details about my role.
Role
Lead UX Designer
Team
Creative Director
UI Design Lead
NTAM Product Team
Tools
Figma, Adobe Creative Cloud
Client
Northern Trust Asset Management
Time
2023

What is this?
The Northern Trust Asset Management Investment Institute is where advisors, trust banks and Northern Trust's own wealth teams log in for research, white papers and webinars. For years, every new report, service and event got its own page, built however made sense at the time. Nobody was wrong. Nobody was looking at the whole, either.
The Problem
The Northern Trust Asset Management Investment Institution was publishing a wealth of research that it's most valuable clients never saw
Years of one-off pages had buried the library under inconsistent layouts, repeated content and a search bar that lived in only one place. Northern Trust needed a way to turn a repository people tolerated into one they could explore, without rewriting the content or rebuilding the site from scratch.

What I did
1
Research
Stakeholder interviews
Analytics & survey review
Audience & membership mapping
Competitive analysis
2
Evaluation
51 issues
UX & visual audit
Heuristic evaluation
Severity ratings (1–3)
3
Information architecture
~400 nodes
Current-state sitemaps (7 iterations)
Future-state sitemap
8-template page system
Content cut & combine
4
Design
8 templates
Search & Content Library flows
Wireframes
Hi-fi UI, desktop & mobile
Email template
5
Systems & handoff
Annotated component library for AEM
Clickable prototype
6
Communication
Current- & future-state readouts
Deliverables documented and linked to Figma
51 issues, 400 nodes, and one pattern
The cracks showed fast. One page repeated the same banner three times. The Factor Center showed the same categories four different ways. A menu item called "Alternatives" quietly sent you to another company's website. I logged 51 issues across 10 sections, each tagged by severity, then ran a heuristic evaluation to find the patterns underneath.
When I mapped the IA, breaking every page into its parts and tagging every download, modal, and external link — it had nearly 400 nodes, with almost the entire map linking to the content library. The whole site was a collection of doorways into one room.

The plot twist
Then I looked at how members actually reached their documents.
Most document views came from email. Almost nobody found research by browsing the site.
Members clicked a link in their inbox, read one PDF and left. Relationship managers were giving new members personal walkthroughs just to show them where things lived. Northern Trust was publishing a huge amount of research its members never saw.
That reframed the project. This wasn't a page refresh. It was a discovery problem.
Hundreds of pages, 8 jobs
Then came a simple question: How many different jobs do these pages actually do? The answer was 8. I created 8 sections and built a template for each job with it's own recipe: a colour-coded stack of blocks that created a consistent hierarchal structure. Members get a site that they only have to learn once. Developers build 8 patterns instead of dozens of one-offs.

Search, everywhere.
Search moved out of the library and into the menu on every page. Results split into the pages worth visiting and the documents worth downloading, with the action right there.
The Content Library stopped acting like a file cabinet. Filters mirror the menu and clear in one tap. Grid or list view, and pagination instead of an endless scroll.

The UI lift: making it feel like Northern Trust
Structure gets members to the right page. The visual design decides whether they stay. The audit had flagged the old UI as loudly as the IA: weak contrast, harsh dividers, a different card on every page, and color used for decoration instead of meaning. The site looked like it had been assembled, not designed.
So I set a visual direction with three goals: make it readable, make it consistent, and make it unmistakably Northern Trust.
Going above and beyond
By the end, the work lived in two Figma files, dozens of frames and a pile of notes. That felt a little too close to the problem I'd just solved.
So I organized every deliverable into two written readouts, Current State and Future State, each linking straight to the right page in Figma. Anyone picking up the project could see not just what we designed, but why.
This was not a part of the scope, but documentation is so crucial in order for future teams to easily refer to the work that's already been done.
Keeping it Real
A document repository will never be the flashiest project in a portfolio, and that's what made it interesting. When you can't add anything and can barely remove anything, design becomes about seeing the structure that's already there, and making it visible.
It also showed me how much one finding can change a project. We came in to refresh pages. One look at how members arrived turned it into something better: helping people find what they didn't know was there.
