Wingocard.

Small steps towards a better experience.

Overview

Wingocard empowers teens in the US to become smart with money through its teen-first banking app, a Visa debit card and financial content.

At Wingocard the team was in constant search of balance between building table-stake features, delighter features and incremental features to keep our teen and parent users satisfied.

This is a collection of a few of incremental features that I got to lead as a product designer. Following the “ship fast and often” approach each of these features were defined, designed and shipped within 1-2 week timeframe. I see them as a testament to how efficient collaboration between product, design and engineering can bring beautiful results and solve user problems fast.

My role

I was a primary product designer for these features and collaborated with PMs, BE and mobile engineers to find the simplest versions possible that would be enough for our customers to feel the difference.

Teen direct deposit
Background

Wingocard’s teen users range in age from 13 to 18 years old. Through user feedback we found out that older teens didn’t only rely on money from their parents. They also worked seasonal, gig, or part-time jobs and were expecting to receive money from their employers on their Wingocard accounts.

Challenge

To be able to receive money from outside of Wingocard ecosystem any user would require to pass the “Know Your Customer” (KYC) verification.

While we did support automated KYC through a 3rd party for parents we couldn’t rely on it with our existing vendor. Teens don’t have foolproof verification IDs, such as an SSN and automatic checks would have returned too many false negatives costing us money without generating results.

Solution

In order to deliver the project fast and test the idea we decided to rely on manual verification and Dropbox for business in our first iteration.

Since account details is a sensitive information which can be used both for sending money to a person, but also by scammers for unauthorised deductions we built friction for first-time users into the sharing flow for details.

Results

check

The feature was designed, developed and launched within 2 weeks.

check

Within a week since launch we got our first teen through KYC and they received their first paycheck on Wingocard on December 23rd, right before Christmas.

check

Having teens pass KYC enabled us to open more lanes for teens to receive money from outside the Wingocard ecosystem in the future.

Parent KYC flow improvement
Background

When registering for a Wingocard account parents act as sponsors for their teens and have to pass the “Know Your Customer” (KYC) verification. Some of the users that couldn’t get verified through their SSN have to upload additional documents to pass KYC.

Challenge

Document collection and verification is handled by a vendor. To redirect parents to the vendor we were generating an email detailing the process and providing parents with a unique link. This meant parents were pushed to leave Wingocard, switch to a mail app, click on the link and complete the process.

This resulted in a 72% drop off.

How could we keep the parents inside the app and allow them to upload documents easily without building a complex API based solution?

Solution

We added a prompt to upload documents inside the app that would simply open a in-app Safari view and load the user’s unique link inside.

To the parents that would look like a seamless experience. For developers this meant almost no additional effort.

Results

check

The feature was designed, developed and launched within 1 week.

check

This change increased the document upload rate by 29%.

Teen usernames
Background

Wingocard launched a feature that allowed teens to transfer money to their friends on Wingocard. However, the only way they could search for their friends was through phone contacts.

Teens used to social apps were expecting to be able to set up usernames and so their friends could use these to find them.

Challenge

Wingocard already had a number of teens that went through the registration process and were using the app without usernames. We had to find a solution that would serve both new users and existing users without creating separate experiences.

Solution

For new users the prompt to set a username was added to the end of the onboarding flow and kept optional so we wouldn’t risk dropping conversions.

To motivate users who skipped setting a username during onboarding we added usernames as a requirement to unlock certain features.

We kept the experience for new users, existing users and those who skipped the step in the onboarding the same, but customized copy so each type of user would have more context into the feature.

Results

check

The feature was designed, developed and launched within 3 weeks.

It hasn’t been promoted to public availability due to Wingocard being acquired by another company.

More work