Enter the password to continue
.about
I'm a Designer who thrives at the intersection of design, strategy, and team leadership. Over the past decade +, I've partnered with enterprise clients to transform complex challenges into elegant, user-centered solutions.
My approach combines deep user research, systematic design thinking, and collaborative leadership to build products that don't just look good. They solve real problems and drive business value.
.contact
.case-study
MetLife committed to migrating its existing design system library (XD) into multiple new Figma design systems, supporting all global markets.
Impact
100% Figma migration. MetLife updated its mobile and web design systems for all enterprise products.
Team
I worked within a dedicated cross-functional pod: a Scrum Master, a Product Owner and Product Manager, two Design Leads including myself, a pool of three dedicated designers plus borrowed resources when available, and multiple developers. We ran two-week sprints in Azure DevOps, with daily standups, biweekly stakeholder demos, and quarterly PI planning.
As Design Lead, the role went beyond design direction. I built components myself, reviewed every designer's work before it shipped, QA'd every build, and merged and published all four libraries.
File Structure
The system lived across five Figma files. A single token file fed color, spacing, and type into four component libraries: UI, Brand, Conversational AI, and Responsive Web. Every sprint, a relay file handled developer handoff and a demo deck, built from a template, supported the stakeholder demo.
Requirements
The design system was not only being migrated, but also functionally improved and visually updated to anticipate a rebrand.
Problem
Figma's prototyping tools weren't built for the branching logic and conditional states enterprise components needed. Multi-step forms, permission-based views, and edge-case flows had to be approximated with static screens or explained in meeting notes, leaving developers to interpret intent instead of working from an accurate model of the experience.
Solution
Supplemented native prototypes with flow diagrams and a structured walkthrough with developers ahead of each release, mapping every conditional path and edge case so implementation matched intent from the start.
Changes Needed
Designers new to Figma and/or MetLife would need new components, consistent documentation & guidance.
Problem
Communicating micro-interactions and animations to developers was slow on both ends. Static redlines and basic prototype flows couldn't convey timing, easing curves, or nuanced motion behavior, and even a small starting set of 4–6 variations to review and refine could take days to produce, creating a bottleneck before any meaningful refinement could begin.
Solution
Paired dedicated motion tools like Adobe Animate and Jitter with AI-assisted generation in Figma Make, producing 10–20 high-fidelity animation options at the outset instead of a handful. A dedicated interaction review touchpoint with developers, when applicable, was added to align on motion intent before implementation, compressing initial creation from days (potentially weeks) to hours while ensuring micro-interactions shipped with the precision and intentionality the design system required.
Solution
At the time of this project, Variables in Figma had just been released. I used Variables to manage all color changes, improve color control, and reduce component clutter.
I ensured all documentation was stored in the Figma library and in the component itself, for quick access during work and detailed reference when needed.
Problem
One of the many challenges faced while working on multiple libraries was understanding the web publishing environment. Many MetLife publishers rely on Adobe Experience Manager (AEM). AEM interacts with Figma components differently, generally truncating their functionality and use of nested components.
Solution
To overcome this, I scheduled multiple AEM walkthroughs with both publishers and AEM project owners to develop a deep understanding of AEM, specifically the limitations and considerations needed when working with Figma components.
Governance
Once live, all four libraries needed regular audits to catch naming drift, orphaned components, and missing variants before they reached teams.
Problem
Auditing all four libraries by hand meant inventorying every component, inspecting each variant, logging issues, and compiling a report, a process that took about two weeks per pass. AI tools weren't available to speed it up either: MetLife restricts access to Claude and most other AI tools company-wide.
Solution
Requested and received an exception to connect Claude to the live Figma files through the Figma MCP and run the audits directly. Claude walks all four libraries, flags naming drift, orphaned components, and missing variants, and a designer reviews every finding before anything is actioned. The same audit that took about two weeks by hand now takes about 15 minutes.
Same audit, two ways. The manual process on the left took about two weeks per pass. The Claude-assisted version on the right, run through the Figma MCP with a designer confirming every result, takes about 15 minutes.
Accessibility
Also, when an element had a major functional or aesthetic change, I created a separate simplified library.
Instead of changing the core components, I built a separate library of simplified components to prevent mass errors and create a better user experience for non-designers.
.case-study
Modernizing MetLife's 20+ year old plan setup and management systems into a unified, role-based enterprise application.
Impact
Transformed how 80% of MetLife employees manage customer plans and streamlined workflows across multiple legacy systems.
The Challenge
In early 2024, The UX team was brought in to support a large-scale legacy application modernization effort of MetLife's current plan setup and management systems.
The project was deep in progress and had no prior UX. The effort was not only to modernize this particular system but also define a better modernization process for all future MetLife enterprise-level applications.
Problem
This project originally kicked off with zero UX support, entirely dev-driven. UX was brought in 4 months after kickoff, which posed many problems including taking an additional 3 months to complete a proper discovery phase, resulting in UX being 6+ months behind the rest of the team.
Solution
The solution was to work in multiple tracks: perform an audit on what's already been developed and deliver prioritized quick tactical wins (introduced proper font stacks, consistent spacing and layouts, page templates), including a full accessibility audit, as there were no considerations in place, and double-track all new work: deliver MVP assets to be developed while also creating a visionary prototype including a new condensed "Enterprise" design system.
Project Timeline
Four tracks, phased in as the program developed. Development was already underway for over three months before UX joined, so the recovery split into parallel tracks, quick tactical fixes running alongside full discovery and modernization, to close the gap without stalling delivery.
Problem
This was a tremendous modernization project. MetLife was working with a very limited design system, a loosely policed collection of marketing components not ideal for an enterprise application.
Solution
I simultaneously created an entirely new "Enterprise" design system during a 3-month discovery phase. The result was close to 40 new components which would eventually become the foundation of MetLife's entirely new Enterprise UI library.
Research
I identified four primary user roles, each with distinct needs and experience levels:
User Pain Points
Current State
Users' workdays included logging in and out of multiple systems while referencing multiple documents throughout the day, often working with 2 or more sources side by side.
Problem
Due to the size of the application (nearly 10,000 input questions), many questions are no longer relevant (expired products, etc.). Most questions have accompanying contextual help text. Aside from having to identify hundreds of antiquated questions, the writing style and tone of the questions and contextual help was very inconsistent.
Solution
I brought in a content writer to help with a proper content audit. This was extremely difficult as I had to leverage multiple SMEs and product owners to identify antiquated questions. I also had development run queries against seldom or never-answered questions. The deliverable was a writing style template allowing product owners to update questions following the same guidelines.
Solution
The system vision: Bring all systems and outside reliances into one centralized web-based application.
Unifying multiple systems as well as many out-of-system reliances into one centralized application saves all users switching overhead and task redundancies.
Solution
Created a system smart enough to recognize which areas and functionality of the application are specifically needed to meet the needs of each specific role.
The result: Navigation and wayfinding are drastically simplified, presenting a clear, friction-free path to performing daily tasks.
Users now log in and are shown ONLY the functionality they need to perform their job, eliminating overwhelm and reducing the learning curve.
Problem
Over 80% of MetLife employees use the system daily, spanning over 60 roles. I identified and targeted use cases for the 4 core users and 6 secondary-level users. One of the biggest pain points heard during discovery was wayfinding and information overload. Most users were only using a very small percentage of the application's functionality.
Solution
I introduced a much-needed role-based platform, ensuring that users only see the functionality and data needed for their specific role.
Global Impact
This project resulted in the creation of 37 new components, which became the foundation for an entirely new enterprise design system used across MetLife's applications.
Results
The modernized system delivered significant improvements across all user groups, streamlining workflows and reducing training time.
By consolidating multiple legacy systems into one unified platform with role-based access, I transformed the daily experience for thousands of MetLife employees.
.case-study
Freedom Mortgage is a top mortgage lender specializing in mortgages that help clients buy or refinance homes.
Employee/Partner workflow is done through a series of multiple disjointed legacy systems, lacking continuity, modern functionality and aesthetics.
As the sole UX/UI designer, I was responsible for leading all UX and creative workshops as well as all production and presentations of deliverables.
Overview
With no single source of truth and no unified experience, employees and partners were forced to navigate a fragmented ecosystem of legacy tools daily, creating inefficiencies, errors, and frustration at every level of the organization. The goal was to replace that ecosystem with a single, modern portal built around how people actually work.
Problems
Problem
The legacy systems had no documentation and no available power users to consult. This made it extremely difficult to understand existing workflows, business rules, and system functionality that had been in place for years.
Solution
To overcome this knowledge gap, I traveled to the New Jersey offices and sat with users across multiple roles, observing their daily workflows firsthand. These in-person sessions were critical for understanding the nuances of the systems, uncovering undocumented processes, and identifying pain points that users had simply accepted as "the way things work."
Strategy
Research
Deep dive into user research, competitive analysis, and information architecture to understand the problem space and user needs.
Problem
Due to the large number of user types that wanted and needed to be involved in discovery, I had to run many workshops (which would normally be in person) remotely.
Solution
I leveraged UserTesting.com for A/B testing and general prototype feedback, and Optimal Sort for card sorting workshops. A key takeaway was that while using Optimal Sort, I added an open feedback field which became an unexpected and invaluable source of user feedback.
Design
Created wireframes, high-fidelity designs, and interactive prototypes to validate design decisions and gather feedback from stakeholders and users.
Problem
The first few sprints resulted in a lot of rework due to developer pushback. Issues and concerns weren't being surfaced until the final stakeholder demo at the end of each sprint, creating delays and frustration as designs had to be revised after significant design effort had already been invested.
Solution
I introduced a staggered review process. Instead of one all-stakeholder demo at the end of the sprint, I added a developer-only review 2 days before the full review. This gave developers a chance to raise technical concerns and implementation challenges early, allowing me to address issues and make necessary adjustments before presenting to the broader stakeholder group. This significantly reduced rework and improved collaboration between design and development.
Key Feature
One of the most critical features introduced was a comprehensive pricing tool that streamlined the mortgage pricing process for brokers and partners.
This tool eliminated manual calculations, reduced errors, and significantly improved efficiency in the pricing workflow.
Problem
This was a 2+ year project, however Freedom Mortgage wanted to release the new loan estimation tool ASAP. This caused issues because it was entirely new functionality not associated with any of the existing systems.
Solution
I created this as a standalone platform which could be triggered (with proper messaging) from the BPM (their main broker portal). BPM would have the CTA and inform the user that they would be taken to a new system. Once a new estimate is generated, the user is given the option to either return to BPM or, if needed, to continue working on the new loan estimate.
Visual Design
The new portal featured a clean, modern aesthetic that aligned with contemporary UX best practices while maintaining the Freedom Mortgage brand identity.
Consistent UI patterns, improved typography, and thoughtful use of whitespace created a more professional and trustworthy experience.
Results
The redesigned portal successfully achieved its objectives, providing Freedom Mortgage with a competitive advantage in the market.
.case-study
Cloud-Based Business Software: Creating a fully integrated platform for small and medium businesses in the construction industry.
Overview
Through the power of user-centric design, the platform doesn't just deliver data, it delivers information. The platform combines a scalable SaaS application layer with robust user interface controls to provide an experience that delights users with its intuitiveness and transparency, from any device.
The Project
Knowify enables its customers to quickly and easily manage their project workflows across all their devices with a world-class user experience.
My Role
As the sole UX/UI designer, I was responsible for leading all UX and creative workshops as well as all production and presentations of deliverables.
For the first 2 months, I also assumed the roles of Project Manager and Business Analyst, working closely with the founders to define business requirements and the production roadmap.
Pre-Discovery
Build a multi-tenant solution that empowers business owners to harness the power of their business data.
Discovery
Define & Design
Retrospective
Yes, 18+ grueling months in a start-up like environment paid off. This was my first full cycle product and I took away a lot, particularly on the strategy side.
Knowify has since become the leader in modern business software tools for the construction industry and very recently (August 2021) partnered with Intuit QuickBooks.
.case-study
Legal Intranet: Designing the look, feel, and user experience of a law firm's new intranet platform.
Overview
Nelson Mullins Riley & Scarborough LLP requested that I design the look, feel, and user experience of the firm's new intranet.
My Role
Led all phases of UX/UI with stakeholders including:
Process
The Define Phase focused on understanding requirements and creating high-fidelity wireframes through an iterative feedback process.
Process
Following the approved wireframes, the Design Phase brought the intranet to life with visual design that aligned with the firm's brand identity.
Deliverables
The final designs reflected a modern, professional aesthetic that improved navigation and content discoverability across the firm's intranet.
The design system maintained consistency across all pages while providing flexibility for different content types and user needs.
Results
A comprehensive style guide was created to ensure consistent implementation across all pages and future updates.
Close collaboration with developers ensured proper implementation and maintained design fidelity throughout the build process.
.case-study
Incubated by Bank of America Merrill Lynch and Morgan Stanley and launched in 2018, Navian Capital is an independent, multi-issuer electronic platform for structured products and annuities.
UX Audit & Full Redesign: Evaluating and redesigning a financial software platform to identify usability concerns and propose areas of improvement.
Overview
Navian needed to transform a sprawling proof-of-concept set of online tools into a cohesive, integrated platform.
The Project
I provided design and strategy support across the full scope of the effort:
My Role
Research
To deeply understand user needs and pain points, I conducted extensive user interviews through multiple channels.
These interviews revealed critical insights about user workflows, pain points with the existing platform, and opportunities for improvement that directly informed the redesign strategy.
Discovery
Through stakeholder exercises and user research, I identified key areas for improvement and opportunities to enhance the platform's user experience.
Design
Working closely with Navian's development team, I redesigned the Luma platform to address identified usability concerns and create a more intuitive user experience.
The redesign focused on improving navigation, streamlining complex workflows, and modernizing the visual design while maintaining familiarity for existing users.
Results
The result is a SaaS platform built to serve every function and role in Navian's growing business, from training and product creation to sales and support.