FOR

Project

T&E Card Application in Workday

Roles

PM, Design

Year

2025

CREDIT

This project was a collaborative team effort in which I served as the Product Manager and also took on responsibilities as the de facto UX/UI Designer. I played a significant role (50% or more influence) in all items featured in this showcase. Contributions from other team members are acknowledged beneath the respective items.

OVERVIEW + IMPACT METRICS

At Mastercard, new hires often faced a slow, cumbersome corporate card application process—forcing them to use personal cards for business expenses. This Workday extension embeds the entire process in-platform, automating internal ticketing and bank applications via APIs for a seamless new-hire experience.

90% decrease in card issuance time (10 days to <1 day).

75% decrease in user actions (e.g., reduced number of clicks).

100% of users in testing preferred the new UX, indicating clear user alignment and improved usability.

RESEARCH + DISCOVERY

We conduced 30+ user interviews and reached the following conclusions:

Finding the card application on the internal SharePoint is tedious.

Card application language is ambiguous.

Card issuance times take upwards of 10 days, but new hires need cards immediately.

Too many user touchpoints are required to receive a card (ticketing platform, email, issuer’s platform).

I conducted ~15 user interviews. I also analyzed each interview and generated key findings, with AI assistance.

JoURNEY MAPPING

I wrote the ideal user journey map and designed flow chart format in Figma. Logan, another PM on the project, wrote the current user journey listed here. The content was informed by learnings in the discovery phase conducted by me and the team.

MVP Prototype

I designed 100% of the prototype, informed by Workday’s UI and pain points identified by me and the team.

SCALING THE SOLUTION

Other companies beyond Mastercard could benefit from embedding their corporate card application in Workday. Mastercard, as a card network, is positioned to develop such a service, but must consider robust API integrations with ticketing platforms and issuers, an intuitive UI, and a scalable backend architecture.

Here’s a snippet of the proposed solution:

I designed 100% of the scaling the solution module, as well as proposed integrations and scalable backend architecture using technologies like Open Authorization 2.0.

Final Presentation

I presented my personal project (on B2B virtual card adoption) and the project described above in two distinct presentations. My personal project presentation is attached below.