PROBLEM CONTEXT
I noticed people new to the US credit system struggle to get their first new credit card and start their credit journey.
This is a net loss to the users as well as business (credit card issuers).
I designed a solution that benefits both users and business.
ROLE
Solo Designer.
End-to-End Product Design.
DURATION
2 months
FINAL SOLUTION
Credito is an app designed to help people get their first credit card and start their credit journey in the US.
OUTCOME
When I presented the final solution in front of users…
Understanding user pain points ( Full details here)
Mapped out the personas and their current user journey to find opportunities to improve the UX
😓 Aggregators simply redirecting and not applying on the user’s behalf
Here I make an assumption that a 3rd party app can apply directly without having to fill in forms again.
The reason this is a valid assumption is that Apple was able to do it with a Goldman Sachs credit card.
😓 Too many forms to fill
Users frustrated going to multiple banks have to fill in the same information.
😓 User abandoned upon rejection
The gaps are when the user is rejected for a certain card or needs an SSN or required details.
The apps don't guide users on the next steps.
This leads to a lot of churn and user frustration.
If our product has any chance of competing the market, these factors are non-negotiable
😀 Self contained, 1 form for multiple applications
Users should only provide their details once and then we take over as their matchmaker
😀 Provide alternatives upon application rejection
Balance user needs with business partner needs.
😀 Leverage virtual cards, apple pay and notifications
Latest tech allows us to offer even lower time to value for the user
Envisioning a future user journey
This gives us a baseline. I use this to explore, test and iterate.
Testing with wireframe clickable prototypes reveals dropoffs and other UX challenges.
All potential dropoff points are addressed by creating alternate paths that eventually put the user back on the path to acquire a credit card.
Explorations to address Dropoff
Skip SSN (for now)
Pro
Get all other details while we have the user.
More likely to value our app after they have shared some details
Con
Initial excitement -> disappointment -> losing trust
Inline instructions
Pro
User has step by step instructions
Con
UI Feels crowded no matter what the placement is.
UI will feel intrusive for people who already have their SSN
Embed video
Pro
Video is well received.
Users pay more attention
Con
Users have to rewatch video to note things down
UI will feel intrusive for people who already have their SSN
Combining the best features
A flow which works for both a user with and without SSN.
Nudging the user with notifications/ email to the exact next step they need to take. Reduce dropoff.
Explorations to address minimize friction / time to value
Users see value at 1 key moment -> When they are successfully approved for a card.
Only if there was a business or technical constraint, I collected the data before providing value.
Otherwise it was pushed off until after user sees value.
Combining the best features
A flow which works for both a user with and without SSN.
Exploring presenting credit card options
The primary goal here is to get the user to pick a card.
I went with option 4 because it represented the right balance of visual interest and functionality.
Handling moment of truth experience
Elevate peak moments - makes it memorable for user.
Guide the user towards activation - In this case it is adding card to wallet.
In case application is rejected, we handle it gracefully redirecting to our partner bank.
Our partner bank offers a secured credit card.
By gracefully guiding them towards it, we create a win-win situation for users and business.
Multiple states
When the user hasn't and has established credit history.
The banner stands out visually to inform user why they dont see numbers and what they need to do next
All "in progress" indicators stand out visually in the UI
Monetization
Several ways to monetize throughout the app.
Here is one example. The App actually cannot store details of the virtual credit card.
I turn this technical/ legal constratint into a revenue source for business by bringing more customers to our partner bank's app.
How I would measure success…
✅ Task completion rate → How many users who download the app end up applying for a credit card? A high % value would indicate that users find the flow easy to navigate.
✅ Churn → How many users are able to provide necessary details after going through the education flow? How many are coming back after the to-do list? A high drop-off indicates that a to-do list does not activate users.
✅ Bank app downloads → What % of people are downloading the bank's app? This is a source of revenue for our business.
Outcome and Conclusion
Credito is the first App design I have come across that marries “user education” and “vendor integration” to solve the problem.
When I presented the final solution in front of users…
Thank you for taking the time to read my case study. I’m grateful to the people who participated in the interviews and usability studies to help me collect insights on this problem. I hope to do more of these.