Embedded Files
Kadet is a crypto wallet extension whose goal is to simplify cryptocurrency-related tasks for users.
Role: UX Designer
Client: Tech Fleet DAO
Duration: 8 weeks
Tools: Figma, Userberry
Context
Currently, the world of crypto is complex, and there is no standardization. Hence, creating easy-to-use wallets while preventing users from losing crypto by mistake is important. As part of the second phase, my team and I took the previous team's work from phase 1 and utilized it as a foundation for our designs, with constant feedback from our stakeholder, users, and research team.
Goals
Address usability tests from phase 1 and iterate on the existing flows accordingly
Help users avoid losing crypto through human error
Improve the way users get free test coins on a testnet
Develop an NFT feature ( view and send flows)
Ameliorate usability of the wallet for users new to crypto
For this case study, I wanted to bring to your attention three hurdles my team and I helped to overcome in the Kadet project.
Onboarding
The stakeholder wanted to make the onboarding suitable for users who knew nothing about crypto. The design team was concerned that people new to crypto were not our target audience. Through probing questions to the stakeholder, it was decided that a customer experience diagram would be beneficial to identify potential users of the wallet extension. The CX diagram revealed that users new to crypto would probably not use our product. It showed that people unfamiliar with crypto would probably start with some "entry-level crypto apps".
Our assumptions were confirmed by the research team. The research also showed that one of the two types of users likely to use our extension would need onboarding. So we started brainstorming ideas for the new onboarding.
A competitive analysis of different types of onboarding was performed, which prompted us to combine the 'learn in context' and 'choose your journey' approaches in order to prevent users from becoming overloaded with information.
Here you can see the "Onboarding flow" we ended up with.
Secret recovery phrase (SRP)
A Secret Recovery Phrase (SRP) is a combination of words used to recover a crypto account to which a password is lost.
I found a couple of feedback comments on a competitor site in which users expressed their frustration because they were not aware of the importance and unrecoverable nature of the SRP. This prompted us to ensure that our users would understand these qualities of SRPs.
Before
After
That's why the UX design team, in collaboration with the UX writing team, came up with the solution to place the agreement on a separate screen. By placing only one sentence on a separate screen, we reduced the users' cognitive load, thus increasing the importance of that message. Asking users to tick the acknowledgment also added to the awareness of the users and forced them to read.
There was a debate between the harm of an increased number of pages and the importance of the message to stand out. Understanding the importance of keeping the SRPs in a safe place is critical for the users and can lead to loss of money if not addressed; we agreed that adding one more page yielded more benefits.
SRP confirmation
During the second usability test, these main issues were identified:
The first was that users were unsure of how to confirm their SRP.
The second was that certain combinations of words made it challenging for users to verify their SRP, e.g., feather and father; when used in the same SRP, confused the users as these words are too similar.
V. 1
33% success rate
V. 2
No testing was done
V. 3
66% of success rate
V. 4
75% of success rate
We were trying to balance the need to ensure that users knew their SRP and make this task as intuitive as possible for them. We realized that the first instinct was not to read the instructions. Hence, we tried using models that people were familiar with, such as games.
Several sessions of 'how might we' were held, and the following solutions were created:
To make sure users knew what they were expected to do, we minimized the number of words seen on the screen. By giving users only one word they could interact with at a time, we minimized the cognitive load for the users and increased the clarity of the task.
Our biggest issue was that the given SRP had 2 words that would start with the same letter, which caused a lot of confusion. The solution was to eliminate the possibility of getting words that began with the same letter.
Retrospective
This was an extremely challenging project since I came into a team with no knowledge of crypto. By studying hard, I was able to exceed my team leader's expectations. I was happy to face such a challenge and grow. I learned how teams work in an Agile environment and why collaboration is key.
As for the project, there were many things we were able to tackle fast and effectively, but there were some that we struggled till the end. I understand there isn't a perfect or right solution all the time; there are many discussions and research that help teams choose the right path.
"You are not the user" - was one valuable lesson I learned. When creating the flows for the "send token", the team created a prototype with many pathways users may take. However, the majority of users tried an unexpected option for us that we didn't prepare for. I was glad we were able to test it and iterate our flows.
There are many more great ideas that our team wasn't able to develop due to the lack of time. Those early-stage concepts will be passed to phase 3 for another team to handle. Also, I hope that research will be able to answer questions that arose from phase 2.
If you want to hear about this project in detail, don't hesitate and contact me!
Google Sites
Report abuse