Skip to main content
Back to index
/01_AI_PLATFORM // 2023 — Present
AI / MLPlatformDesign Systems

MUSE & DevJoy — AI Platform at Fannie Mae

Model lifecycle governance for institutional banking

MUSE & DevJoy — AI Platform at Fannie Mae
Client
Fannie Mae
Role
Lead UX Designer
Duration
Ongoing (24+ months)
Impact
1 week → hours
/02The brief

Problem

Recoveries, Billing, and Liquidation workflows at Fannie Mae spanned disconnected legacy tools. Case and invoice submission took up to a week; liquidation and reconciliation ran on 8-week cycles. AI capabilities existed in the backend but had no consumable surface — model lifecycle governance, training, and TechOPS lived in engineering scripts, not in product.

/03How we built it

Process

01
/STEP_01

Research & journey mapping

Ran extensive user journey mapping and persona development with operators, model engineers, and ops teams. Facilitated cross-functional FigJam workshops to align business goals with user-centric AI solutions and identified the friction points that, once removed, drove a 62% reduction in user errors.

02
/STEP_02

MUSE — multi-platform architecture

Architected MUSE as a unified model lifecycle governance surface across web, mobile, and connected device interfaces. Standardized complex backend workflows (model creation, modification, TechOPS) into one design system used by every internal AI team.

03
/STEP_03

DevJoy — AI training UX

Designed DevJoy to let technical teams train banking models without leaving the product surface. Translated raw ML configuration into progressive, scalable interfaces — schema-aware, with safe defaults and audit-friendly diffs.

04
/STEP_04

AI chatbot & document automation

Shipped a consumer-grade AI chatbot for institutional banking that approves documents with minimal human intervention. Iterative usability testing and empathy mapping validated high-fidelity prototypes for 100% alignment with user needs before engineering handoff.

/04The result

Outcomes

Recoveries & Billing cycle time
1 wk → hrs
Liquidation cycle (8 wks → 4 wks)
−50%
User errors after journey re-design
−62%
Prototype-to-engineering alignment
100%