Wetravel
Opportunity: Research, User testing, Task Flow, UX/UI Design
Challenge: Create a payment system for vendors
Role: Product Designer
Wetravel is a payment platform for travel organizers and vendors to collect payments securely and manage bookings efficiently.
Description
Currently, there is no payment system implemented for vendors through the Wetravel website.
Problem Statement
By building the vendor payment channel from zero to one, we hope to:
- Develop an onboarding platform for the vendors
- Develop a dashboard allowing users to review and make transactions
- Develop user flow
Goals & Metrics
The Research Process
RESEARCH
Competitive Analysis
The initial step of our research was to understand successful patterns in current products and missing gaps in unique values. We explored 14 different products, and narrowed down to 4 competitor payment platform, and 4 vendor management platform. We analyzed the pros and cons of each competitor, and performed our points of analysis on: payment management, on-boarding, and transaction.
User Testing
We identified there are two use cases for Wetravel. Use case 1 are the people who sent payment, in most cases, it is the organizers sent payment to the vendors. Use case 2 are the receiving money. Organizers receive payment from the vendor.
Learning Goals
We came up with some learning goals to figure out what we want to to learn from two different use case.
Write here…
SYNTHESIZE
User Findings
We synthesized in respect to use case one and two. our findings under 2 categories below in order to create a more solid frame and foundation for our design moving forward.
Prioritizing Values
The findings from our research were then organized on an affinity map to better understand their relationship to each other and to determine our priorities moving forward in the process.
Ideation
BRAINSTORM
Userflow
Prior to coming up with solutions, we spent some time developing the task flow for onboarding the vendors, and vendors requesting payments. We created a task flow that connects the key interaction with the users and the product.
Wireframe
We fleshed out the UI sketches, created lo-fi wireframes, and got down the clickable prototype for validation testing. We conducted validation testing with 7 users, and found out there were a couple issues with wording on the dashboard. Users couldn’t exactly understand what the pending future means. For example, we would like to make the clickable CTA as simple to understand as possible.
THE PROCESS
Below is the design process through the ideation phase. As expected, the process was more of an organic journey than linear path, consisting of constant revisit of the previous steps and reiteration.
Solution
Overview
User Flow
Request Payen
Onboarding
Validation
We conducted validation testing of the clickable prototype with 5 users for each group. Here is a summary of the findings from the "buyers" testing:
6/6 Seamlessly checked pending transaction and made payment
6/8 Found information on web pages satisfactory and trustable
5/8 Requested for more information on Wetravel security
6/8 Found the product easy to use and navigate
8/8 Understood purpose of each page
After Thoughts
With the complex level and short time frame of this project, it is extremely important to stay focus on the most important areas without going too deep in details. Also, when a problem evolves, it is crucial to react timely and reiterate to come up with a solution that allows the project moving forward. For future improvement, I would like to spend more time looking into the filter system, and badge reviewing system to further improve the clarit