Designed the virtual card experience to help users control online spending and boost security.

​

• Owned design from concept to launch.
• Enabled creation of multiple card types for different use cases.
• Streamlined card management and spend controls for users.
• Focused on security features and ease of use.

​

Resulted in 65% of all online spend on Divvy being processed via virtual cards, driving adoption and user trust.

Divvy's web product was scaling fast, with multiple designers shipping into a shared surface (later carried through the Bill.com acquisition). Without a strong craft bar, the risk wasn't just visual inconsistency. Divvy had a very young team and many of us held strong opinions.

Built Divvy’s initial design system from scratch. Font and type scale were chosen for maximum readability with a tabular style as a bonus for data tables. A color system that was unopinionated and maximized for data-rich compositions. And iconography that was friendly, inviting, and straightforward.

For many of Divvy’s designers it was their first time working within a design system. the general fear that was shared with me as I built the system was that the system would strip designers of their creative freedom. I had to help our design team understand that the system is in place to unify us as a design team and that we are all contributors to the system.

I am a very strong believer that the only way to build and maintain a design system that every designer uses and respects is if they are given the autonomy to contribute to the evolution of that system.

I facilitated a discussion in our weekly design team sync to make sure all designers on the team were aware of this goal. I specifically prioritized 1-on-1 time with a few jr. designers on the team to make sure they had an opportunity to contribute to the design system and feel valued. This personal time also helped young designers elevate their bar for what was acceptable at Divvy.

I spent hundreds and hundreds of hours crafting a system that was attractive and functional and these 1-on-1 coaching sessions with young designers were massive in holding the whole team to that high bar I set for myself.

My final couple of years at Divvy were spent focusing on the design system full-time and post-acquisition I was given ownership over the whole Divvy and Bill.com web products. This was cause for even more alignment and buy-in from the team as I now had to help an existing design team become advocates and contributors to a system that was relatively new to them.

After the merger of the Divvy and Bill.com products the Bill.com brand became the identity but the UI and UX foundation I had established at Divvy became the source of truth and Northstar for the Bill.com product.

When we first implemented the design system at Divvy we had less than 10% token and component coverage. Before acquisition we hovered around 80%. And post acquisition we maintained that high bar of 80% while vastly improving compliance and usability as Bill.com moved us way up market.