Go to top of page

Kadet Wallet

Giving future UX designers an easier way to research as they learn

Volunteer Project

The Team

Project Strategy

Design

Research

Development

My Role

UX Researcher

Timeline

2 Months

Stakeholder

Tech Fleet Community DAO

Background

The Kadena blockchain is a proof-of-work based that is scalable and secure along with featuring a gas station that would help pay transaction fees.

Tech Fleet DAO is an apprenticeship agency and a UX community that does work with nonprofits and impact-driven organizations. Part of Tech Fleet's mission is to create opportunities for professionals who's transitioning into UX or bootcamp graduates to work in real world.

My Role

As one of the UX Researchers on the team, I collaborated with my other UX researchers to design and conduct interviews and usability tests. We also analyzed the results in order to be able to create recommendations for the next team.

Scope

Tech Fleet wants to create a cross-chain wallet in the mission that would be accessible for people who are new to Kadena and cryptocurrency in general.

The team came to the project with the stakeholder having already listed out their vision for the project in a Medium article for the team to read beforehand.

As the research team, we had 8 weeks to understand the problem space of cryptowallet users and find the trends in the results to send to the rest of the teams.

How might we make it easier for users new to the Kadena chain to use a crypto wallet?

New Team Struggles

As the first team to work on this project, there were a lot of hurdles that we as a team needed to overcome.

Lack of industry knowledge

The majority of the team had no experience or familiarity of cryptocurrency at the beginning of the project cycle. A "crypto bootcamp" was required, which took up 2 of our week sprint.

To make sure future teams save time, when we were working on the handoff, I advocated for new members to read "Story of the Blockchain" and created an FAQ page based on the crypto bootcamp to give future phases a jumping off point.

Time Zone differences

None of my team members were in the same time zone as I was - some even on the other side of the planet. When it came to for some of us it's the start of the work day and for others it's midnight and they would be exhausted.  

To combat this, we kept up a constant line of communication online and even found a way to meet twice a week outside of the regular work sessions for research team meetings. We also created a database that made it easy to keep up with the meetings.

This kept our team connected, close, and up to date with any developments, no matter what time it was.

Discord in the Team

There were issues involving communication in the team and throughout the main team, which resulted in stalled progress as our lead was not communicating with the rest of the team. We felt like the other teams were not using the research we conducted and instead did their own research.

Despite this, we stuck together as a team, we didn't lose any team members (which is common in a volunteer project), and we supported each other and hyped each other up.

The biggest challenge - communications

LET ME TELL YOU

At the beginning of the project we had a completely different lead from the one we ended the project and it was for GOOD REASON.

Our first meeting together as a research team had all of us apprentices together on one meeting after we split off from the main work session and our lead on a completely different call from the rest of us. We decided on that, because it was important for us to define our first steps into research, we would work on a research plan.

The next time we all meet up as a team she had not only not looked at our research plan, she had an entire interview script based on what she believed was the best step and assigned us all to find someone to interview. No plan for recruitment, no discussion, just that we had our assignments. When we asked questions around what the goal of certain questions were, she did not answer. Naturally, we all felt that we were not being listened to and decided to do our own thing to ensure that. This pattern escalated until we decided as a team that we would stage a mutiny and chose one of our own to become our lead, airing our worries to the project lead. As a result, we were able to change our lead and became a more cohesive team. Because of the habits that she had perpetuated, the llead's newness around leading, and the general agreement to not make it a big issue, communications between teams were not upheld and confusion only became worse until we as a team had a meeting to reset expectatiosn around communications.
At the start of the project, we had a Research Lead who, despite multiple attempts from us apprentices, had major difficulties in coordinating with us and other teams. We would have created a plan, decided steps that we were going to take, or made decisions on our direction as a team that we made public to the team, and they would have their own predetermined path for the team with no input from us or any reason that they could share with us in how it benefited the project.

This pattern escalated to a point that, as a team, we wanted to accept a new lead, specifically one of us who went above and beyond in keeping us together as a team. With assistance from the project lead, we were able to make that change with little fuss or change to our productivity and a great improvement to our cohesiveness as a research team.

However, because we had decided to make the change without an announcement to avoid potential friction between the former lead and the team along, it was never clearly communicated with the rest of the team and communications between teams were not upheld. As a result, other teams made decisions to work on certain tasks with no actual research input.

In order to get on the same page, I led a meeting with the entire team to solidify what the team needed to focus on and what steps we can take to make sure that we were communicating with each other. As a result, the whole team became more transparent in sharing what they needed from each other and we finished off the phase strong.

Along with this, I learned the importance of having a lot of communication with the other teams. When I became the Research Lead of The Serious Type, I made sure that it was an expectation to have all of the leads meet once a week to make sure that we are all on the same page from the beginning.

Phase 1: Starting Research

Talking to the stakeholder

Prepping for the interview

While we had the vision article created by the stakeholder himself to reference, we still had questions around the project, from what the stakeholder expected by the end of the project to how he would define success for this project. Working together with the Product Strategy, Design, and  Development team, we put together a collection of questions that we asked the stakeholder.

Important Insights from the Interview

  • High level goal: first incubated product for TF; open source and eventually will be an application we maintain as a community
  • Our target audience - New users to cryptowallets
  • Goal of the current phase:
  • 8 successful sprints of research and design
  • Two flows
  • Sending/receiving and holding tokens
  • Set up user as a new user and have them start using applications on the Kadena blockchain and make it as simple as possible

Creating the plan

Once we had a better understanding of both the project expectations and the industry, we were ready to start planning our research. While the design and product strategy teams worked on the competitive research, the research team broke off to prepare the research plan. This was our opportunity to align our goals in what we were looking for in this phase.

We decided that we wanted to focus on recruiting more experienced cryptowallet users to understand the problem areas they dealt with when they worked with cryptowallets as a starting point. We were also looking for opportunities that our competitors created for us to iterate off of, based on these users' experience with the wallets.

Balancing what we needed to know + the stakeholder's Wants

While we wanted to do some exploratory research, our stakeholder wanted us to jump out of the gate with conducting usability tests using a prototype he created off of MetaMask, a popular open-source cryptowallet.

To accommodate for both party's needs, we decided to split the team into two teams - half of us would be focusing on exploring users' experiences with cryptowallets while the other half of us conducted usability tests.

Conducting the tests

Usability tests

We conducted 4 moderated tests and 4 unmoderated tests through Maze using the stakeholder's prototype to understand:

  • The user's impressions, thoughts, and questions on the current dashboard design based on Metamask
  • How the user would send a Hype token using the current prototype
  • How the user would progress through the sign up flow

Exploratory interviews

We also conducted 5 exploratory interviews in order to understand the user's general experience with:

  • How crypto wallets are currently used
  • Any problems or frustrations users had with existing wallets
  • The user's general knowledge/experience with the Kadena blockchain

Round 1: Synthesis

Finding the trends and issues

After we were all done with the tests, we compiled all of our data together into an affinity map that would make it easier for us to see all of the finds together and find patterns in our results.

results

Exploratory Interviews

  • Users are hungry for an “all-in-one” solution that’s simple and easy to use
  • None of the users we spoke to had actually used Kadena, but many of them have heard of it
  • A majority of users used their wallet to stake idle assets/earn passive income, and send and receive tokens to/from others or decentralized exchanges
  • Users are frustrated by the lack of assistance during onboarding and would like more info in the form of info bubbles/coach marks/FAQs/chatbots - inaccessible to newcomers
  • All of the users mentioned security as a primary concern or criterion while choosing a Wallet. One of the users mentioned more steps/“Signing Transactions” helped him feel secure.

Usability Testing

  • Users overall enjoyed the prototype and stated that it had all of the basic parts needed for a cryptowallet
  • However, users expected to be able to buy tokens within the app and were surprised when they couldn’t
  • The transaction summary screen overwhelmed users with too much data
  • Users were confused by Send chain breakdown screen and what it represents
  • Users wanted to be able to manually do the breakdown across the chains
  • There were details, such as "Send Percentage", where the usefulness or clearness was not understood

Proto-Persona

Based on the results from this phase, we started to work on creating personas. While we hypothetically believe that we could have created at least three different personas, only one truly came out fleshed out based on the research. We decided that the other personas would become more fully fleshed out in the next phases.

The Investor

The Investor works in Stem who wants to use the crypto space to maximize profit, so needs the best wallet available for their needs. They utilize multiple strategies to achieve their goal, but is worried about losing money by a lack of transparency or scams.

Phase 2: Shifting focus

Changing target audience

Our stakeholder, in this phase, specified that they want to focus on getting users that were new to crypto to use this wallet, with their first chain being Kadena. Despite that, based on not only our discussions with crypto users in our last phase but also talking to members of the team familiar with Kadena, we found that Kadena is a blockchain with an audience of mostly cryptocurrency enthusiasts which means that the users most likely available to use this wallet would most likely not to be brand new to cryptowallets in general.

Therefore in this round, we would focus on users transitioning to Kadena from other blockchains as our 'new users'.

Divide and conquer

With this pivot in our user focus, we wanted to conduct a new set of exploratory interviews. Along with this, the Design team had tasks that they wanted us to test in the prototype with new users. However, at this point in the process, we were left with only a short period of time to prep, conduct, and analyze the data brought in.

Therefore, we changed tactics when splitting the work for this round. We combined the usability test and interview into one session for half of the team to conduct and had the other half of the team focus on synthesizing the recordings and notes as sessions with participants were done.

This allowed us to compress two weeks of work into one week while keeping up with synthesizing the data.

Usability tests

We conducted 7 moderated sessions using the updated prototype to understand:

  • Design Team's revisions to the Create/Import Wallet flows
  • Users' general understanding of Secret Recovery Phrases
  • What users expect to see in the transaction history
  • Whether users preferred the light or dark color scheme
  • What users thought of the current branding
Open Prototype in New Tab

Exploratory interviews

We also conducted 5 exploratory interviews in order to understand the user's general experience with:

  • Entering the Kadena community
  • Frustrations when managing assets on the Kadena blockspace
  • The user's general knowledge/experience with the Kadena blockchain

results

Usability Testing

  • All of the users had trouble with creating a secret pass phrase
  • They were thrown off by the secret pass phrase requiring reentry to check that the user had written down the phrase.
  • Users move too quickly and don't follow the directions given in the prototype
  • Users did not like the visual design and color palette
  • They preferred a solid background with a pop of color.
  • All users were very interested in the potential for NFT support
  • Most users found it helpful to have the price increase/decrease on the cards on the dashboard screen

Exploratory Interviews

  • Majority of users learned about Kadena first from the community
  • Main sources - Kadena's sites, Medium articles, Twitter, and Youtube
  • Users found the onboarding experience into Kadena difficult, specifically with understanding the multi-chain infratructure
  • Many users favor using only a few chains and don't use other chains due to a lack of understanding of the multi-chain concept
  • All users were excited about a new Kadena wallet because there are so few options and it will raise visibility of Kadena
  • All users strongly believed that multiple chain functionality of Kadena allows it to scale really well and allow cross-chain interoperability.

Round 2: Synthesis (Delete?)

Working Prototype

*Works best on desktop

Finishing Off the Phase

Handoff

By the time we had completed the second round of research, we were at the end of our seventh week, which meant that we had only one more week together for this phase. We debated on whether we would try to squeeze in one more round of research.

In the end, however, reflecting on the trouble we had with starting this phase, we decided that it would be more beneficial to work on a handoff document that would outline what we did, important findings, some of the troubles that we had along with our solutions, and tips that we think new apprentices coming on would appreciate to know. This way, we hope to streamline  the next phase's first few weeks as we know the project lead wants to recruit apprentices with no experience in crypto like in our team.

Proposed next Steps

  • Our team was planning on testing the updated send and history flows the Design team had been improving on from the first round, but they did not make it into this round.
  • The Design team had also started working on NFT support, but the the research team still needs to dedicate some time into researching what users need and expect, along with testing incoming designs.

What went well

  • Taking Initiative
  • As a team we took steps when our roles as researchers were becoming unclear to communicate our role in the big picture.
  • Speaking Up
  • Throughout our time together, we were proactive in addressing issues both in our own team and within the larger team.
  • While it wasn't easy or comfortable, having these difficult and open conversations made the project run so much smoother for everyone.
  • Working Together
  • We made it a priority to meet multiple times in the week as a team.

My final thoughts

First "real" project

This was my first project where I worked with a stakeholder and a cross-functional team. Having a whole group of people I'd need to check in with and collaborate with on a project was a complete change from me being a sole designer on my past projects. I've learned how important it is to keep lines of communications open between all teams from the start in order to avoid confusion in the team and keep the project going.

Pushed out of my comfort zone

While my team struggled with the issues that cropped up during the first half of the project, the challenges allowed me to gain confidence in my skills as a researcher and a member of the team. There was no room for imposter's syndrome if this team was to succeed. As a result, I became stronger in defending the choices I and my team made and speaking up when I had questions or worries that came up in our research meetings.

This ultimately gave me the confidence to become a Research Lead myself in the next project I would be involved in.

View Deliverables

Connect with me!