UX Design

Resolver is a financial web application for internal employees and external business partners involved in the management of financial settlements.

After one year working under the Senior UX Designer, I inherited all UX responsibilities and led a major visual design upgrade.

Due to the software's proprietary nature, this is an abstracted overview.

A photo of a phone and a laptop running Resolver, a web-based financial application.An diagram that illustrates various stages of collaboration for a settlement case.


Legacy Concerns

Modernizing the internal software user experience was a huge opportunity to increase accessibility, usability, efficiency, and overall value for the company.

I joined the Resolver dev team shortly after its MPV release under the guiding visions to:
  1. Replace the legacy system
  2. Improve business practices
  3. Pursue growth opportunities

My Role

I started as support for the lead UX designer—taking notes during moderated interviews, analyzing recordings, wireframing, creating research presentations, etc.

One year later, I accepted the leading UX position to carry forward work in progress and continue developing the UX path for the next three years.


Two of our biggest challenges:
1) achieving parity with legacy software without disrupting operations and 2) persuading legacy users to adopt updated business workflows.

Usability & Design

Variability & Scalability

With positive and negative feedback on the MVP, I led a major visual design upgrade to satisfy the variability and scalability of enterprise operations. As a proficient graphic designer, I knew how to capitalize on layouts, colors, and typography.

In close collaboration with the product owner and all developers, we were able to iterate on our design system and define reliable UI patterns.

Validation & Feedback

With the industry expertise of the product owner, our assumptions consistently addressed ~70% of users' needs; however, I relied on remote moderated usability tests to confirm development ideas, ask for immediate feedback, and—most important—find operational blind-spots.