In this speculative project, Venmo wants to offer more features to increase their market share and optimize user experience. Identify a pain point and design a seamlessly integrated feature to address it.

-Design a feature that allows users to repeat payments and schedule recurring transactions.

-Build out the appropriate screens alongside existing Venmo design to integrate the new feature

App Design, Icon Creation, interaction design logo design

Figma, Pencil & Paper

4 weeks

UX Designer (Research, Visual Design, Interaction Design, User Testing)

SECONDARY RESEARCH

Mobile payments are an increasingly normal part of life in the 21st century, and Venmo is one of the apps leading the charge. In order to design a feature that continues the app's pioneering spirit, I conducted research with the following objectives: to gather detail on key competitors, and collect insight to inform empathy mapping and persona generation.

Here's a bit of what I learned from the first step, secondary market research:

1. 14% of adult Americans use Venmo for P2P transactions (Balancing Everything)
2. The most common uses of mobile banking apps included paying rent, splitting utility bills, sharing meals and gifting (MarketWatch)
3. Users average 5 transactions a month (Business of Apps)

COMPETITIVE ANALYSIS

Venmo's market share is respectable, but there are several peer-to-peer/transaction apps that offer similar similar experiences as well as additional features. Completing this competitive analysis provided me with a basis to further define Venmo's station in the industry and how other similar apps develop their interfaces. Venmo stands out as an app that has a truly simple interface without rerouting to one's bank- even as Venmo expands their services, the interface without going to the menu is much simpler than other competitors.

HEURISTIC EVALUATION

Working on an existing app gave me the opportunity to critically scrutinize details of Venmo's design. In this heuristic valuation, I could admire how the aforementioned simplicity helps their usability as defined by Nielsen's heuristics, but noted several aesthetic inconsistencies to be wary of while moving forward with this project.

USER INTERVIEWS / EMPATHY MAP

Using the provisional personas as a basis for recruitment, I found 5 Venmo users to interview to learn more about their behaviors. I asked several questions about their usage; here are just a few:

1. Tell me a bit about what you use Venmo for.
2. Can you describe what one of your typical interactions
with Venmo would be step-by-step?
3. Are there any other financial applications you use?

Using the interview transcripts, I noted every comment made during the interviews and grouped similar ones to synthesize the interviews into common sentiments. This is illustrated through this empathy map:

CREATING A PERSONA

With the research stage complete it was time to start narrowing in on the problem I'd solve for. Using the the insights, needs, and general behaviors found during the research phase, I developed a persona to ground the solutions I'd develop in the user's needs. Matt Robertson reflects the goals and motivations of a core Venmo user, and he shares several of the pains as the interviewees. Using this persona ensured that I was taking actual users into account as I designed- you'll notice that his needs are those uncovered in the previous stage.

POV STATEMENTS / HMW QUESTIONS

POV statements encapsulate users' needs, and HMW questions transfer them to the designer's remit. By literally asking 'how might we do so-and-so?", I can start generating potential solutions to the needs uncovered in empathy research. The insights and needs from empathy mappng comprise the first two columns in this diagram, and the last two is where they are formatted into actionable statements.

USER & BUSINESS GOALS

Having learned more about the user's goals, it was worthwhile to account for those of the business- especially as this project involved working off of an existing digital product with an established ethos. This diagram provided a basis to see if the potential solutions to user needs addressed business goals as well.

FEATURE ROADMAP

After brainstorming answers to the HMW questions, I started defining viable solutions to address the needs from the research stage.

This roadmap ennumerates these solutions within the Venmo app, and also includes their priority level as defined by my confidence in delivering them within the project timeframe and the amount of effort.

The 'must haves' comprise the feature I would endeavor to create: an option to repeat transactions and schedule recurring ones.

APP MAP

The ideate stage for this particular project was not just about designing a feature, but also its placement within the app at large. This sitemap is an exploration of the information architecture of the current app, with the additional screens that comprise the new feature.

TASK FLOW

The aforementioned navigation within the app map's structure can vary in myriad ways- but this task flow grounds the proposed flows to the user's needs. The below tasks address the three needs uncovered in earlier stages: storing, discussing, and locating content.

USERFLOW

The two journeys in the task flow were then combined and expanded on to comprise this userflow. It shows not only the above flows, but the various options users can take at several points in the same tasks, like searching for a previous transaction instead of using their personal history tab.

LOW-FIDELITY WIREFRAMES

I knew what interactions the user would make in the recurring transaction feature, and it was time to visualize how they would actually look in the interface. Low-fidelity sketches carry minimal risk, but still provide an effective way to understand how the user will access the design. It was paramount to follow Venmo's established design patterns to not only insure that the new feature would fall in line with the business goals, but also so it's functionality comes naturally to users. The sketches reflect how I designed the scheduling of recurring transactions to mimic the pattern Venmo use's to change a transaction's privacy settings.

HIGH-FIDELITY WIREFRAMES

Using the low-fi wireframes as direct reference, I built out high-fidelity wireframes of the new feature and key screens of Venmo required to illustrate the entire flow. This was a continuation of my objective to adhere to the app's existing patterns, seen here through the iconography, color selection, spacing, and- notably- the use of radio buttons (which are very prevalent throughout the app; they eschew dropdowns and other patterns in most instances).

PROTOTYPE

Once the wireframes were complete, I could link them together into a usable, testable prototype. This was particularly exciting as it's the actualization of not only the sketches at the beginning of the design stage, but also ideas generated after research.

USER TESTING

Once the prototype was complete, it was necessary to test it with Venmo users to determine usability, unforeseen issues, and also whether the concept was a worthwhile addition to the app. This was accomplished through virtual testing with 5 millennial participants attempting three moderated tasks:

1. You’re Matt. You paid your portion of the rent back to your roommate, Jay Patrowski, in December, and now you want to set up a recurring payment. Find this transaction and schedule this payment to repeat on the 1st of every month.

2. You just started a new job writing copy for Eden Bothman’s social accounts. You’re getting paid $65 a week. Schedule a recurring weekly request on Mondays to Eden for $65 as your invoice.

3. Find your list of transactions that you’ve set up to repeat.

TEST FINDINGS

Testing provided important quantitative data:

Task Completion Rate: Task 1 & 3 had a completion rate of 100%. One participant was unable to complete Task 2 without prompting due to a prototyping issue.

Error Free Rate: 96%.

Notably- no users made the more significant errors I expected, like being unable to close the scheduling windows, or being unable to find the icon/label to schedule the repeat.

AFFINITY MAP

Much like the empathy map, this affinity map shows how I noted observations and comments from each user test and then consolidated common stickies into groups. These categories were each synthesized into an insight, and negative insights informed recommendations for improvement.

Notably, 4/5 participants expressed that this feature is useful. Creating a recurring transaction was easily repeatable, and the icon/label location was rememberable after intial discovery.

RECOMMENDATIONS IN ACTION

This is before and after the implementation of the first recommendation "Include a short onboarding message above the calendar asking the user to input the date of the first/only payment". Adding a message to provide a little bit of onboarding is a relatively easy change to make, but can make the entire process feel easier and safer to users.

REFLECTIONS

‍This project allowed for my growth as well the opportunity to understand and appreciate Venmo's interface. The former came about through the process of generating ideas in the context of an existing app: it wasn't just about creative problem solving, but doing so with very specific guidelines.

For example, Venmo's transaction builder doesn't have any scrolling capability. The screen dimensions of the user's device were my real estate, which makes adding any kind of feature a game of refinement and simplicity.

Regarding Venmo's interface, aesthetic inconsistencies within the visual design became abundantly clear at the time of this project's completion. It appeared Venmo's visual design was growing faster than the app itself. It's a reminder within my own work to bear in mind that inconsistency can be a mammoth issue to fix, and should be prioritized early. ‍

Overall, in setting out to design a feature that adds value to the Venmo experience, I think I succeeded. 4/5 users directly said that the recurring transaction feature was useful in general, and specifically useful to them.

NEXT STEPS

Were this project to continue, I'd look forward to testing changes made with these recommendations, and building out the feature in the following ways: cancelling recurring transactions,designing the notification system for when the transactions recur, and integrating external calendars.