Available now·Austin, TX·Remote, hybrid or onsite·11+ years of experience
60%faster model-validation cycles
62%fewer developer errors
30%higher developer-tool adoption
Paused · Muted
Selected work
Four projects. Each states the official role, the team relationship, and how the outcome was measured.
Fannie MaeShippedJul 2023 — Aug 2026
MUSE — enterprise model risk management
Model registration, validation and sign-off lived across disconnected tools, so no one could prove a model was reviewed, current and approved for its stated use.
Role · Lead UX Designer · sole product designer for MUSE
MUSE model-validation lifecycle: ~60% faster validation cycle across a five-stage process
Developers stalled mid-integration because the portal, documentation and tooling each described the same task differently. A separate workstream addressed authorization decline diagnostics for merchants.
Role · Senior Product Designer · design lead for the portal and documentation experience
U.S. monthly developer-portal visits: 45K pre-launch baseline → 160K in the quarter after launch
Administrators dreaded cluster upgrades. A wrong compatibility call or an invisible exception could turn a 'zero downtime' upgrade into an outage, with no guided way to see readiness, monitor progress, or recover.
Role · UX Designer · primary designer for UX, UI and research
A guided administrator experience shipped in Jira Data Center spanning readiness, compatibility, live upgrade monitoring, exception handling and completion.
Private clients wanting to give appreciated crypto to humanitarian causes were routed through serial signature chains built for paper, so gifts took months and advisors could not see where a transfer had stalled.
Role · Senior UX Designer · design lead, advisor and private-client experience
~$49M moved via Bitcoin across the first cohort; 15 private clients onboarded
Each figure includes its baseline, measurement context, and my contribution.
Fannie Mae · a heavy approval path, compressed
~60%
Faster model-validation cycle
Fannie Mae · MUSE
Five sequential validation gates each had to clear before a model could advance. Reframing which approvals genuinely had to block turned that chain into a much shorter path.
PayPal · a fragmented journey, connected
45K → 160K
Monthly U.S. developer-portal visits
PayPal · developer.paypal.com · U.S. market
Developers moved between the portal, documentation, and their own tooling to finish one task. Reorganising the information architecture put those steps on a single integration path.
How I operate
Each statement names what I actually did: led, decided, recommended or facilitated.
Led
Design as the sole product designer
Served as the sole product designer for MUSE, setting product design direction across the model lifecycle while partnering with product, engineering, validators and model-risk governance.
Facilitated gate-ownership negotiation with model-risk governance and presented direction to Director, Senior Director and VP stakeholders.
A disagreement I lost, then partly won
Tension
Model-risk governance wanted all five validation gates to stay blocking, so no model could advance without a completed sign-off at every stage.
My call
I recommended that two of the five gates become non-blocking with mandatory evidence capture, because the queue data showed those gates almost never changed an outcome — they only delayed it.
Result
The released gate accounted for most of the cycle-time reduction. The retained gate stayed, and I designed a parallel-review pattern so it stopped serializing the whole lifecycle.
Read the full trade-off
Evidence I used
Workflow telemetry on gate dwell time and reversal rate, twelve validator interviews, and a line-by-line read of the internal validation guideline to confirm nothing required those two gates to block.
The decision that was made
Governance kept one of the two gates blocking and released the other, with an audit trail requirement I had not proposed.
None. Sole product designer for MUSE at Fannie Mae. Decided design direction and functional platform definition. Model-policy approval remained with risk governance. Presented to Director, Senior Director and VP stakeholders.
Four stages I run on every regulated or AI-enabled product
01
Frame the system
Map the policy, the roles and what the model is actually accountable for.
02
Define accountability
Name who decides, who reviews and who can override — before any screen exists.
03
Design the human-AI decision
Confidence, lineage and override paths staged for the moment of judgment.
04
Measure the outcome
Instrument cycle time and error rate against a baseline agreed up front.
About, briefly
I design for people who have to answer for their decisions. Most recently I was Lead UX Designer for MUSE at Fannie Mae, serving as the sole product designer on the platform.