

Organization

WEX
My role
Product Designer,
Corporate Payments Team
Timeline
8 Weeks (2025)
At WEX, I worked on multiple design initiatives for WEX's Corporate Payments' line of business. This particular initiative entailed designing a solution for the notifications system, serving WEX business payment customers. I primarily worked on research and design system efforts, supported by our design, research, PMs, and stakeholder teams.
DESIGN SYSTEM COMPONENTS
Notification-system components handed off with fully customizable properties.
UX WRITING DELIVERABLES
Copies handed-off for notifications and different categories of alerts.
PROTOTYPE TURN-AROUND
Weeks of moving from ideating and iterating, to prototyping in Figma.
My first product design internship!
My summer was full of amazing firsts: presenting my work to corporate teams, learning fintech flows, and trying out rope courses in Maine. On top of this being my first PD internship, I was also my team's first design intern!
THE PROBLEM
Finance workers juggled email and in-app details.
Controllers rely on timely alerts to review transactions and resolve payment issues. However, urgent items were being missed and workflows didn't feel optimal.
Users are juggling too many tabs manually for their workflow
Teams needed to track important information on different platforms, leaving workers feeling inefficient and slow.
As you read, it's worth knowing: This is my first time in fintech…

RESEARCH AND DISCOVERY
Prior user interviews and research had been conducted before I joined this project. To reopen and kickoff this project, I focused on synthesizing our existing efforts and data in order to discover improvement opportunities, current strengths, unseen pain points, and deeply understand our finance teams.
"How are customers currently working with alerts?"
USER JOURNEY MAP
To understand the bigger picture, we closely analyzed the physical and emotional journey of their workflows.
Maintaining open communication with the research team, I mapped their insights onto a user journey map in order to pinpoint successes and limitations of their current workflows.

KEY INSIGHTS: FINANCE CONTROLLERS
We concluded that our users were confused and mentally overloaded with the separation of "email-alerts" and "platform-actions."
PAIN POINTS
"As a user, I'm frustrated that:"
PRODUCT: Important items are too easily forgotten or delayed.
Finance controllers checked emails for alerts, but had to log into the WEX platform to investigate issues
Risks: sensitive finances, delayed responses, and missed urgent items
PROCESS: Recording important information relied on controllers' DIY solutions.
Had to manually record it elsewhere for future use, no centralized place for older alerts
ACTIONABLE INSIGHTS
"As a user, I want to:"
Review issues in full details immediately
Easily take relevant action after being alerted
Conveniently track and revisit alerts
COMPETITIVE ANALYSIS: INDUSTRY PATTERN EXPLORATION
To circulate different ideas into our process, we analyzed notification design patterns in the fintech industry.
Through signing up for demos and discovering patterns from fellow fintech companies, we analyzed the strengths and weaknesses of their patterns, informing our ideation, visual cohesiveness, and future direction.

DESIGN FOCUS: USER NEEDS + GOALS + CONSTRAINTS
As effective guidelines for success, I illustrated the priorities that should be reflected in our future solution.
To ideate an effective design solution, it was important to see the full picture. Bringing in what I learned from our research, I carefully mapped our user needs, business goals, and technical constraints to guide my ideation.
To make sure I was aligned with the team, I discussed with our stakeholders and PMs what our desired outcome of this project may look like, which also helped me accomodate longer-term future goals.
IDEATION + OPPORTUNITY
We saw an important opportunity to ease the transition between "awareness" and "taking action."
IDEATION: WIREFRAME SKETCHES
After establishing our goals and focus, I began freely sketching my ideas on paper.
I set up a timer for 10-minutes and began sketching away. Once I finished, I added notes and sought feedback by discussing my thought process and expanded the conversation by applying considerations to constraints and goals.
Then after contextualizing the problem, I suggested we go with the 'Inbox' idea.
By benchmarking our key insights, user journey map, interviews, and design focus, I was able to advise to stakeholders that an 'Inbox' may be most suitable. The 'Inbox' addresses workflow needs, industry patterns, and as a bonus, aligns with technical backend constraints. (Ideally, I'd create low-fi digital prototypes to test and validate, but there were deadline priorities that needed to be adhered to.)
PROTOTYPING: MID-FI PROTOTYPES
After aligning with the team, I iterated and refined to create mid-fi prototypes.
As a team, we ensured open communication and checked in with one another, so that the designs remained consistent and on-track.
After completing multiple iterations and receiving feedback, like refining positioning and adding necessary elements, I turned my wireframes to mid-fi prototypes; we were then given the greenlight to move forward with testing.

UX WRITING
Assuring users stay on top of their finances easily and clearly.
Following the effective principles of UX writing and researching how competitors write their alerts, I focused on communicating the urgency and clarity of the content without fearmongering.


TESTING: STAKEHOLDER + PM FEEDBACK
Validating usability & uncovering blindspots

Contribution Highlights
Final Deliverables















