Nha Pham
User Experience Designer
Category:
Human-Centered Design
Project type: End-to-end mobile app (UX research, interaction design, and high-fidelity prototype)
Role: UX/UI designer and researcher as part of a 4-person team — conducted 3 interviews, led persona development, consolidated user data, facilitated usability testing, and created the final interactive prototype
Industry: Personal Finance / Group Expense Management
Tools: Figma, FigJam, Zoom, Notion
Duration: January - March 2025
is a case study that explores group expense maangement
Project type: End-to-end mobile app (UX research, interaction design, and high-fidelity prototype)
Role: UX/UI designer and researcher as part of a 4-person team — conducted 3 interviews, led persona development, consolidated user data, facilitated usability testing, and created the final interactive prototype
Industry: Personal Finance / Group Expense Management
Tools: Figma, FigJam, Zoom, Notion
Duration: January - March 2025
Project type: End-to-end mobile app (UX research, interaction design, and high-fidelity prototype)
Role: UX/UI designer and researcher as part of a 4-person team — conducted 3 interviews, led persona development, consolidated user data, facilitated usability testing, and created the final interactive prototype
Industry: Personal Finance / Group Expense Management
Tools: Figma, FigJam, Zoom, Notion
Duration: January - March 2025
is a case study that explores group expense maangement
The goal was to minimize manual calculations, reduce social tension, and create transparency in group payments.
The goal was to minimize manual calculations, reduce social tension, and create transparency in group payments.
The goal was to minimize manual calculations, reduce social tension, and create transparency in group payments.
As the lead designer and project manager on a team of 4, I created and maintained our sprint roadmap, divided tasks across research and design phases, and facilitated weekly check-ins. With the most experience in Figma, I led the prototyping and design system work, while also supporting teammates with collaborative design tools and version control.
As the lead designer and project manager on a team of 4, I created and maintained our sprint roadmap, divided tasks across research and design phases, and facilitated weekly check-ins. With the most experience in Figma, I led the prototyping and design system work, while also supporting teammates with collaborative design tools and version control.
As the lead designer and project manager on a team of 4, I created and maintained our sprint roadmap, divided tasks across research and design phases, and facilitated weekly check-ins. With the most experience in Figma, I led the prototyping and design system work, while also supporting teammates with collaborative design tools and version control.
The Opportunity: We can ease the emotional burden of splitting expenses in social settings.
The Opportunity: We can ease the emotional burden of splitting expenses in social settings.
Through user interviews and observational research, we learned that group payments often go beyond just math, they’re wrapped in awkwardness, forgotten Venmos, and unsaid tension. The core problem wasn’t just about accuracy, but about comfort, memory, and fairness.
We discovered that the stress of splitting bills was often a byproduct of unclear communication, informal mental tracking, and unspoken social expectations.
Through user interviews and observational research, we learned that group payments often go beyond just math, they’re wrapped in awkwardness, forgotten Venmos, and unsaid tension. The core problem wasn’t just about accuracy, but about comfort, memory, and fairness.
We discovered that the stress of splitting bills was often a byproduct of unclear communication, informal mental tracking, and unspoken social expectations.
“I always mean to pay people back, but if no one brings it up, it just kind of fades into the background.”
— user interview, age 26
“I always mean to pay people back, but if no one brings it up, it just kind of fades into the background.”
— user interview, age 26
“I always mean to pay people back, but if no one brings it up, it just kind of fades into the background.”
— user interview, age 26
“We end up splitting things equally just to avoid drama, even if someone clearly ordered way more.”
— user interview, age 29
“I hate asking my friends to Venmo me—it makes me feel petty even though I covered like $50 worth of stuff.” — user interview, age 22
“I hate asking my friends to Venmo me—it makes me feel petty even though I covered like $50 worth of stuff.” — user interview, age 22
“I hate asking my friends to Venmo me—it makes me feel petty even though I covered like $50 worth of stuff.” — user interview, age 22
“I hate asking my friends to Venmo me—it makes me feel petty even though I covered like $50 worth of stuff.” — user interview, age 22
“We end up splitting things equally just to avoid drama, even if someone clearly ordered way more.”
— user interview, age 29
“We end up splitting things equally just to avoid drama, even if someone clearly ordered way more.”
— user interview, age 29
I proposed using Cognitive Load Theory as a guiding framework to inform our UX decisions. Based on our initial interviews and pain point synthesis, it became clear that users were overwhelmed—not just by the task of splitting expenses, but by the mental effort required to coordinate, calculate, and communicate in group settings.
I saw strong alignment between this problem space and the theory’s emphasis on reducing extraneous mental load to support decision-making and follow-through.
I proposed using Cognitive Load Theory as a guiding framework to inform our UX decisions. Based on our initial interviews and pain point synthesis, it became clear that users were overwhelmed—not just by the task of splitting expenses, but by the mental effort required to coordinate, calculate, and communicate in group settings.
I saw strong alignment between this problem space and the theory’s emphasis on reducing extraneous mental load to support decision-making and follow-through.
= More accountability, faster payments, and less group tension
“I feel way less awkward asking friends to pay me back now.”
= More accountability, faster payments, and less group tension
“I feel way less awkward asking friends to pay me back now.”
I proposed using Cognitive Load Theory as a guiding framework to inform our UX decisions. Based on our initial interviews and pain point synthesis, it became
clear that users were overwhelmed—not just by the task of splitting expenses, but by the mental effort required to coordinate, calculate, and communicate in
group settings. I saw strong alignment between this problem space and the theory’s emphasis on reducing extraneous mental load to support decision-making
and follow-through.
Initial Prototype:
Creating a "Split" action
Initial Prototype:
Creating a "Split" action
To support Autonomy and Competence, we designed the request flow to feel clear and customizable. I prototyped features like editable line items, preferred payment methods, and optional reminders, giving users more control over how they split, track, and follow through on payments.
To support Autonomy and Competence, we designed the request flow to feel clear and customizable. I prototyped features like editable line items, preferred payment methods, and optional reminders, giving users more control over how they split, track, and follow through on payments.
This is one idea among many, we had 18 initial prototypes by the end of our long prototyping phase.
This is one idea among many, we had 18 initial prototypes by the end of our long prototyping phase.
Initial Prototype:
Creating a "Split" action
This is one idea among many, we had 18 initial prototypes by the end of our long prototyping phase.
To support Autonomy and Competence, we designed the request flow to feel clear and customizable. I prototyped features like editable line items, preferred payment methods, and optional reminders, giving users more control over how they split, track, and follow through on payments.
What I expected:
intentional, customized payment planning
I designed the request creation flow with the hope that users would take advantage of features like editable line items, receipt uploads, and smart reminders to personalize their split requests. These tools were meant to empower users to track shared expenses with more clarity and flexibility, especially in group settings.
“I’d like to split the sushi dinner, but let me adjust what each person ordered first.”
What I expected:
intentional, customized payment planning
I designed the request creation flow with the hope that users would take advantage of features like editable line items, receipt uploads, and smart reminders to personalize their split requests. These tools were meant to empower users to track shared expenses with more clarity and flexibility, especially in group settings.
“I’d like to split the sushi dinner, but let me adjust what each person ordered first.”
What actually happened:
set it and forget it 🫠
In testing, most users skipped customizations and simply used the default split or relied on memory. Many preferred speed over precision, which led to uneven splits and confusion later on. This revealed that we needed to reduce the effort even further and support fast but accurate behavior through nudges and templates.
“I just want to hit send and be done with it… figuring out exact costs takes too long.”
What actually happened:
set it and forget it 🫠
In testing, most users skipped customizations and simply used the default split or relied on memory. Many preferred speed over precision, which led to uneven splits and confusion later on. This revealed that we needed to reduce the effort even further and support fast but accurate behavior through nudges and templates.
“I just want to hit send and be done with it… figuring out exact costs takes too long.”
What I expected:
intentional, customized payment planning
I designed the request creation flow with the hope that users would take advantage of features like editable line items, receipt uploads, and smart reminders to personalize their split requests. These tools were meant to empower users to track shared expenses with more clarity and flexibility, especially in group settings.
“I’d like to split the sushi dinner, but let me adjust what each person ordered first.”
What actually happened:
set it and forget it 🫠
In testing, most users skipped customizations and simply used the default split or relied on memory. Many preferred speed over precision, which led to uneven splits and confusion later on. This revealed that we needed to reduce the effort even further and support fast but accurate behavior through nudges and templates.
“I just want to hit send and be done with it… figuring out exact costs takes too long.”
What I expected:
intentional, customized payment planning
I designed the request creation flow with the hope that users would take advantage of features like editable line items, receipt uploads, and smart reminders to personalize their split requests. These tools were meant to empower users to track shared expenses with more clarity and flexibility, especially in group settings.
“I’d like to split the sushi dinner, but let me adjust what each person ordered first.”
What actually happened:
set it and forget it 🫠
In testing, most users skipped customizations and simply used the default split or relied on memory. Many preferred speed over precision, which led to uneven splits and confusion later on. This revealed that we needed to reduce the effort even further and support fast but accurate behavior through nudges and templates.
“I just want to hit send and be done with it… figuring out exact costs takes too long.”
