Case Study — Freddie Mac

Built for Compliance, Not for People: Redesigning Freddie Mac's Custodian Interface

Consolidating 7 duplicate screens into one dynamic interface, eliminating 5–10 second filter delays and reducing cognitive load for custodians managing hundreds of loans daily.

Company
Freddie Mac
Role
Lead UX Designer
Timeline
2023 – 2024
Team
Product, Engineering, Compliance

A 15-year-old system at its breaking point

In 2023, Freddie Mac initiated a full-scale modernization effort to overhaul Loan Selling Advisor - a core platform used by lenders such as banks and mortgage companies to manage the process of selling loans to Freddie Mac. At the heart of this platform was the document custodian workflow: a critical hub where custodians are responsible for managing, verifying, and certifying hundreds of loans every single day.

I joined as the Lead UX Designer, tasked with redesigning the custodian workflow from the ground up. The existing system was characterized by redundant interfaces, slow search capabilities, and a high cognitive load that actively hindered custodians from performing their tasks efficiently. Every unnecessary click or delayed page load compounded across hundreds of daily interactions, resulting in severe bottlenecks.

Legacy document custodian screen
One of seven legacy screens - each requiring separate navigation to manage a single loan's different states

Three compounding failures

Duplicate Screens
Forced constant context switching and required developers to maintain 7 separate codebases for a single feature update.
5–10s
Filter Reload Penalty
Every filter adjustment triggered a full server-side reload, compounding into hours of lost productivity across the team each day.
High
Cognitive Load
Dozens of unprioritized data fields forced custodians to manually scan dense tables, leading to errors and workflow fatigue.

The legacy architecture forced users to navigate across 7 duplicate screens just to manage different states of a loan. This redundancy confused users and created a massive maintenance burden; the development team had to update 7 different codebases for a single feature enhancement.

Compounding this were severe performance problems. Custodians frequently toggled between data and documentation issues, requiring constant filter adjustments. Every filter change triggered a 5–10 second full-page reload, a penalty that, multiplied across hundreds of daily interactions, resulted in significant lost productivity and workflow frustration.

Seeing the friction firsthand

To design a solution that truly resonated with our users, I initiated a deep-dive research phase, partnering directly with custodians. Through contextual inquiry and shadowing sessions, I observed their daily routines, noting exactly where they hesitated, where they created workarounds, and where the system actively blocked their progress.

Step 01 — Search
Initiating a loan search
User enters criteria and scrolls manually to find matches in a dense, unpaginated table.
No type-ahead or instant filtering — full manual scan required every time.
Step 02 — Filter
Adjusting filters
User filters by documentation status to address a specific issue type.
System locks for 5–10 seconds on every filter change, breaking workflow concentration.
Step 03 — Review
Reviewing loan data
User scans the data table to verify loan details before acting.
Cognitive overload from dozens of unprioritized, irrelevant data fields cluttering the primary view.

"Out of the dozens of columns in the tables, we only really use a few for decision making."

We conducted field prioritization exercises with custodians to understand which data points were actually necessary for immediate tasks. We drew a hard line between "essential for initial review" and "needed for deep investigation", which became the foundation for the new information architecture.

Site map and research artifacts
Click to enlarge
A small portion of the updated sitemap, the full redesign consists of 250+ screens supporting over 100 different workflows. — click to view full size
Primary User Persona
Enlarge
Primary User
The High-Volume Custodian
Document Custodian, Large Lender
Processes 200–400 loans daily. Needs speed above all else - any delay compounds into hours of lost time. Values keyboard shortcuts and minimal navigation.
Secondary User Persona
Enlarge
Secondary User
The Compliance Reviewer
Compliance Officer, Regional Bank
Focuses on audit trails and certification accuracy. Needs clear status indicators and the ability to investigate edge cases without losing their place.
Tertiary User Persona
Enlarge
Tertiary User
The New Custodian
Junior Custodian, Mid-size Lender
Recently onboarded, still building familiarity with the workflow. Relies on clear labels, logical structure, and forgiving error states to build confidence.

7 screens → 1 dynamic layout

The most critical shift was addressing the 7 duplicate screens. Through iterative wireframing, I explored how to condense these distinct views into a single dynamic layout. By decoupling the UI from rigid legacy backend states, we designed a framework where the interface contextualizes itself based on loan status, rather than forcing the user to navigate to a new page.

01
Audit
Cataloged all data fields and features across the 7 legacy screens to establish a complete inventory.
02
Prioritize
Collaborated with custodians in card-sorting exercises to rank data fields by frequency of use and critical importance.
03
Consolidate
Drafted wireframes merging the 7 screens into a single, context-aware dynamic layout separated at Loan and Contract level.
04
Progressive Disclosure
Designed an expandable "Additional Fields" panel to house secondary data without cluttering the primary view.
05
Validate
Tested the new dynamic layout with custodians to ensure no critical workflows were disrupted during consolidation.

The seven screens were separated based on Loan level and Contract level, with fields dynamically swapping between active and inactive states based on Loan Status and Certification Status selection. Removing 6 redundant screens also significantly reduced the developer maintenance overhead for every future feature enhancement.

Consolidated single-screen layout
The new consolidated layout - fields dynamically adapt based on loan status, replacing 7 separate screens with one context-aware interface
Additional fields panel
Expanded "Additional Fields" panel - secondary data available on demand without cluttering the primary view
Dynamic field states
Dynamic field states - active vs inactive fields adapt contextually based on loan status and certification selection
Contract level layout
Contract-level layout - the same dynamic framework applied to the contract tier, maintaining visual consistency across both levels

Eliminating the 5–10 second penalty

With the architecture simplified, I focused on the most painful interaction points: search and filtering. The legacy search required users to type full queries, hit enter, and manually scroll through results. I replaced this with a robust type-ahead search component - as users type, the system instantly surfaces relevant loans, eliminating the need for manual scrolling entirely.

I then tackled the debilitating reload times. Because custodians frequently pivot between resolving data errors and documentation errors, they needed a way to segment their view instantly. The new Quick Filter mechanism allows toggling seamlessly between "Total Loans," "Documentation," and "Data" , with front-end filtering logic that entirely bypasses the 5–10 second server-side wait.

Quick filter component
Quick Filter- instant front-end toggling between Total Loans, Documentation, and Data with zero reload delay

Streamlining high-volume batch processing

Custodians rarely work on a single loan in isolation -- high-volume batch processing is the reality of their workflow. The legacy system buried multi-loan certification deep within one of the seven screens, making it difficult to discover. Users often had to select loans, navigate away from their list, perform an action, then navigate back.

We leveraged the new bulk action slider component from the design system, housing all actions in an accessible, always-visible location. This eliminated the need to navigate away from the primary data table. Available actions now correspond contextually to the active filter selection, with tooltips on hover to surface each function.

Bulk action slider
Bulk action slider- contextually aware actions tied to the active filter selection, without leaving the data table

Record satisfaction following release

74%
Satisfaction rate in Q4 2025
Up 12% from Q2 2025- record high
80%
Found the workflow easy to perform
Up 20% from Q2 2025
72%
Said it was quicker to find loans
Up 23% from Q2 2025

Following the redesign and release of the Document Custodian Pipeline, we surveyed users to assess ease-of-use and areas of opportunity. The results were strong across every measure, particularly around speed and discoverability, the two areas of highest friction in the legacy system.

On the engineering side, removing 6 redundant codebases reduced the overhead for every future feature enhancement; a structural win that compounds with each subsequent release cycle.

Next case study
50% Faster: Redesigning Freddie Mac's Loan Pipeline for High-Volume Lenders