introduction
Venmo is a mobile fintech app that allows users to make secure payments to one another. Users can send and receive money with ease. Venmo also has their own credit card and debit card and allows business accounts as well. Venmo also allows users to buy crypto currency through their app.
Problem:
While Venmo is widely used and well known, there is no easy way to split an itemized bill. Venmo currently allows for users to split payments equally but we wanted to implement a feature to allow users to split by items.
While Venmo is widely used and well known, there is no easy way to split an itemized bill. Venmo currently allows for users to split payments equally but we wanted to implement a feature to allow users to split by items.
Scope:
We had to design this product within 80hrs. The final deliverable was a high fidelity prototype to hand off to developers.
We had to design this product within 80hrs. The final deliverable was a high fidelity prototype to hand off to developers.
Constraints:
• 80hr time limit to complete project
• We must follow Venmo's current branding guidelines and product flows
Tools:
• Figma
• Adobe Illustrator
• Adobe Photoshop
• Maze
• 80hr time limit to complete project
• We must follow Venmo's current branding guidelines and product flows
Tools:
• Figma
• Adobe Illustrator
• Adobe Photoshop
• Maze
time to start research
Goals
We will be adding a feature to Venmo allowing users to split check/bill items within the app. Currently Venmo allows payments/requests among multiple users, but these are all assuming the split is even. This new feature will allow users to split payments accordingly with bill items.
While there are other check splitting apps out there, the goal is to eliminate having to use multiple apps in order to get a task done. Because Venmo is well known already for sending/receiving payments, we decided that this feature would be most effective on this app.
While there are other check splitting apps out there, the goal is to eliminate having to use multiple apps in order to get a task done. Because Venmo is well known already for sending/receiving payments, we decided that this feature would be most effective on this app.
Comparative Analysis
We compared 4 different check splitting apps. These included Tab, Splitwise, Settle Up, and Splid. We compared their overall UI, features, strengths, weaknesses, opportunities, and threats. Overall they were similar in purpose but different in UI and included features.
User Interviews
• There were 5 participants with an age range between 26-35 years
• 30 min interviews were conducted over a phone or Zoom call
• 30 min interviews were conducted over a phone or Zoom call
what did we find?
Interview Results
Observations:
• All participants have used Venmo for 9+ years
• All participants only use Venmo for transactions among friends
• All participants do not use Venmo’s other features (credit/debit card, crypto)
• All participants would use an itemized tab feature
• All participants enjoy the convenience of Venmo
• 3/5 said they would want the transaction to be populated through a photo of the bill
• All participants have used Venmo for 9+ years
• All participants only use Venmo for transactions among friends
• All participants do not use Venmo’s other features (credit/debit card, crypto)
• All participants would use an itemized tab feature
• All participants enjoy the convenience of Venmo
• 3/5 said they would want the transaction to be populated through a photo of the bill
User Goals:
• Easy way to split check among friends
• Quick transactions when paying/receiving
• Easy way to split check among friends
• Quick transactions when paying/receiving
Pain Points:
• All participants are concerned with security regarding payment apps
• None of the participants use Venmo’s features outside of transactions
• 2/5 participants dislike downloading multiple apps to achieve one goal
• All participants are concerned with security regarding payment apps
• None of the participants use Venmo’s features outside of transactions
• 2/5 participants dislike downloading multiple apps to achieve one goal
Conclusion:
The research overall provided insight on reasons users have Venmo. Our initial problems are supported by this data and we can move forward to solve these user’s issues. The users’ general needs are a trusted, well-known app that allows for easy tab splitting. These users prioritize security when it comes to payment apps and want a simple app that allows for this feature.
The research overall provided insight on reasons users have Venmo. Our initial problems are supported by this data and we can move forward to solve these user’s issues. The users’ general needs are a trusted, well-known app that allows for easy tab splitting. These users prioritize security when it comes to payment apps and want a simple app that allows for this feature.
Affinity Mapping
We used affinity mapping in order to organize our findings from the conducted interviews. Within these interview results we found very clear themes among the users and were able to organize this information very quickly.
Our themes:
• itemized bill feature opinion
• Venmo usage
• bill splitting logistics
• Venmo likes
• Venmo dislikes/unused areas
• ideal payment app
• other payment apps used
• itemized bill feature opinion
• Venmo usage
• bill splitting logistics
• Venmo likes
• Venmo dislikes/unused areas
• ideal payment app
• other payment apps used
Personas
We created one persona to encapsulate overall general traits we found from the interviews. This persona includes goals, needs, interests, motivations, and challenges.
let's plan out how to add a feature to Venmo's app
Site Map
We made a small change to Venmo's sitemap to show where our new bill splitting feature would go
Task Flows
time to start building!
Low-fidelity Wireframes
We start with low-fi wireframes and mocked up the full task flow for splitting a bill. Before adding in branding and details we want to make sure the flow is clear and fits in with Venmo's structure.
Our wireframes show the complete flow of splitting a bill via items. We chose to have the user add the party members involved first to adapt to the current flow of paying/requesting money currently in venmo. Then the user can scan a photo of their bill receipt to populate the split with their items. The user will then assign items to the party members and proceed to add tax/tip, review the final spit, and send the payment requests.
Our wireframes show the complete flow of splitting a bill via items. We chose to have the user add the party members involved first to adapt to the current flow of paying/requesting money currently in venmo. Then the user can scan a photo of their bill receipt to populate the split with their items. The user will then assign items to the party members and proceed to add tax/tip, review the final spit, and send the payment requests.
High-fidelity Wireframes
With the same low-fidelity flows, our high-fi wireframes include Venmo's branding elements.
UI/Visual Design
Because we're following Venmo's current branding guidelines, we had to make sure our additional screens for our feature mirrored the existing UI. We see the same buttons, fonts, checkmarks, and more. We were careful to not implement any new designs that did not fit.
Prototype
Using our high-fidelity wireframes, we built a prototype to link the task flow screen together.
but how do users react to this new feature?
User Testing
There were 14 participants, unmoderated tests were conducted via Maze.
Goals:
• Verify if simple tasks are achievable and clear to the user
• Observe user flows and identify any pain points or areas of confusion
• Assess the clarity of copy within the flows
• Verify if simple tasks are achievable and clear to the user
• Observe user flows and identify any pain points or areas of confusion
• Assess the clarity of copy within the flows
Task flows:
1. Splitting a bill by items
2. Adding members to a party
3. Capturing and assigning items to party members
2. Adding members to a party
3. Capturing and assigning items to party members
Results:
• 93.4% direct success rate overall
• 32.4% misclick rate
• Some misclicks were on the camera screen where people would click the middle of the camera instead of the shutter button
• Some misclicks were users attempting to edit the tax/tip despite directions noting they were uneditable
• 21.25 seconds was the average time spent on full task flow
• 10/14 participants rated this task a 4 and up
• 32.4% misclick rate
• Some misclicks were on the camera screen where people would click the middle of the camera instead of the shutter button
• Some misclicks were users attempting to edit the tax/tip despite directions noting they were uneditable
• 21.25 seconds was the average time spent on full task flow
• 10/14 participants rated this task a 4 and up
Terminology
• 50% participants use “check” most frequently
• 28% selected “bill”
• 21% selected “it depends”
• These users say it depends on the context of how they’re using each word. Didn’t provide further specifics.
• 0% select “tab”
• 50% participants use “check” most frequently
• 28% selected “bill”
• 21% selected “it depends”
• These users say it depends on the context of how they’re using each word. Didn’t provide further specifics.
• 0% select “tab”
Feedback
Positive Feedback:
• 8/14 participants did not have any further feedback
• “Seamless navigation”
• “Order of operations was very clear”
• “What a great idea”
• “Really liked the flow”
• 8/14 participants did not have any further feedback
• “Seamless navigation”
• “Order of operations was very clear”
• “What a great idea”
• “Really liked the flow”
Constructive Feedback:
• 1 participant noted there was a lot of steps, would suggest reducing if possible
• 1 participant wondered about if others in the party disagree with tip amount
• 3 participants noted confusion revolving around adding users to the party
• Participants expressed different areas of confusion within that flow section
• “Confusing seeing Meena’s costs since Meena already paid for everything”
• “List of people in party looks like search results”
• “Wasn’t 100% clear where to add Meena”
• 1 participant noted there was a lot of steps, would suggest reducing if possible
• 1 participant wondered about if others in the party disagree with tip amount
• 3 participants noted confusion revolving around adding users to the party
• Participants expressed different areas of confusion within that flow section
• “Confusing seeing Meena’s costs since Meena already paid for everything”
• “List of people in party looks like search results”
• “Wasn’t 100% clear where to add Meena”
Prioritized Iteration:
• Change our terminology used to “check” instead of “bill”
• We will be rethinking and redesigning the way party members are added and the logistics behind the user paying the full bill and the user starting this split
Areas to answer/solve:
• How to distinguish the party UI from the search results
• Does the user search themselves within the search bar to add themselves or are they automatically included because they’re starting the split feature
• Change our terminology used to “check” instead of “bill”
• We will be rethinking and redesigning the way party members are added and the logistics behind the user paying the full bill and the user starting this split
Areas to answer/solve:
• How to distinguish the party UI from the search results
• Does the user search themselves within the search bar to add themselves or are they automatically included because they’re starting the split feature
Iterations
Our research shows that some users were a bit confused with adding party members and felt like it resembled the search function too closely. Based off the participants' feedback, they all had confusion around the same area of the flow but for different reasons. We decided to rethink this portion of the flow to eliminate any confusion moving forward.
We changed the UI so that it looks like a list of the user's Top People and Friends and they select from this pre-populated list. The user starting the split is automatically selected and may be deselected if needed. This list already exists in Venmo's current UI and is a more seamless way to select people to add to the split party.
Here we see our first iterations before user testing (left) and our changes afterwards.
We changed the UI so that it looks like a list of the user's Top People and Friends and they select from this pre-populated list. The user starting the split is automatically selected and may be deselected if needed. This list already exists in Venmo's current UI and is a more seamless way to select people to add to the split party.
Here we see our first iterations before user testing (left) and our changes afterwards.
the finished featured
Conclusion
Overall adding a new check splitting feature to Venmo was successful. We had few iterations and got very positive feedback and confirmed that users would utilize this feature. We learned how users would naturally navigate and flow through this process of splitting an itemized check and were able to implement an effective and smooth way to add this feature.
Some challenges we came across was brainstorming the logistics behind scenarios of groups of people splitting a check. There were a wide range of potential cases and we had to build this feature to allow for majority of these cases.
We answered questions regarding whether the user is a part of the check split, we questioned about cases where people might disagree on the tip amount. We also thought about how this feature would look like on the other side if a user were to join the check split as opposed to initiating it.
Next steps would be to do a second round of user testing to see if these iterations are clearer and more effective to the user. Afterwards we would build out what it looks like should users choose to split a check evenly instead.
We answered questions regarding whether the user is a part of the check split, we questioned about cases where people might disagree on the tip amount. We also thought about how this feature would look like on the other side if a user were to join the check split as opposed to initiating it.
Next steps would be to do a second round of user testing to see if these iterations are clearer and more effective to the user. Afterwards we would build out what it looks like should users choose to split a check evenly instead.
