Options seem to plague our daily lives. I once heard that " don't manage your time but manage your energy." That being said, choices that we encounter all day depletes our energy that most of the time we earmark for something more meaningful. I started this project with excitement and I jumped right away in investigating anything about choices and authentication. Gathering and formulating the key hypothesis that I know the product could benefit. Our process in Capital One trained us that empathy is the foundation of every great user experience. User's perspectives, pain-points, and insights should guide our craftsmanship.
As I start creating the experience, I placed myself in the user's mindset, I visualize the experience where the user looks at authentication in the lens of a door or a portal to their house. This visual narrative that played in my head gave me a different perspective to how users perceive digital authentication and security. User's objective is to enter an authentication experience / a door, get presented by a lock / UN&PW, and finally be at their final destination.
If you offer users a key, what is the fallback? We found that users always duplicate their keys in case their primary key got lost. If the password is the fallback key, are we communicating it clearly?
Additional questions that surfaced were, If choices and alternatives bogged customers, would that sentiment be true for digital products and financial security? Key user insights: Users hold their financial information, situation, and credentials near and dear to their heart. They will write their password and lock it in a safe. They will not even download a financial app to their mobile device because some of them find it unsafe or vulnerable to hacking even though they placed strong UN&PW on those financial apps. These sentiments emerged in our research, and incorporating them in walkthroughs, learn more's and other teachable interactions is a huge benefit for both the product and the users.
Iterate, test, iterate....
1. How do we offer the options, specially if we are introducing it in an onboarding experience? 2. How would they like to manage their security options (Sureswipe, Passwords, TouchID)? Settings - Maybe. Should we educate them there?
3. What other aspects of alternative authentication can we communicate in this space?
These were just a few questions that we want to elicit to our users.
Our user research provided us guidance to what kind of interaction the user wants. That also inform us how to position the options in the right part of the onboarding screen. Bold main options were appropriate in this scenario.
As the user choose the appropriate key or sign in option that fits them, they do not know what is the other option's set-up experience. For them, the only thing in their mind is the choice they made and the task it presents. TouchID definitely fits the convenience but provides questions around security. Sureswipe is nice because it is very specific like a password.
When redirected- the UX needs to be clear on the specific request and message. Frustration is just around the corner, and it may cause abandonment. The direction you provide the user is critical here. You just suddenly throw the user out of your app or existing experience and ask them to do something, in user perspective, they will start asking- "how can I come back?", "how can I continue?"
Also, paying attention around button blindness specially in an onboarding task made sense. The user can get continue/trigger happy around buttons. Are we providing enough context for them to make the right decisions? Are they aware of the decision they made? Here, driving a contextual and succinct message works.
I am very fortunate I got to work with great and talented Capital One designers, their guidance and collaborative energy made this experience a success: Beth Shoup, Jason Bryant and Sabrina Ngai.