Kadet Wallet Web Extension Case Study
BETA LAUNCH (PHASE 5)
My Role in the team
UX Writer Co-Lead with 2 apprentices & an overall team of 20+ in product, research, dev, content, design.
Stakeholder
Techfleet Community DAO
Duration
8 Weeks (Agile, bi-weekly sprints)
Tools used
Figma, FigJam
Notion
Slack, Zoom
LettuceMeet
Skills
UX Writing
Team Leadership
Agile Methodology
Project Management
Microcopy
Project Context
What is Kadet Wallet?
What does it solve?
A multi-chain web extension that supports Kadena, Ethereum, Polygon, Binance etc.
It allows users to store crypto tokens and NFTs, with features designed for both beginners and experts in the crypto space.
WHERE WERE WE?
What was our milestone?
What was my role?
We aimed for Phase 5 Beta launch, but the Dev team found code issues, and the Design team spotted gaps in the design system and user flows.
My role as Lead UX Writer was to address these problems and ensure a smooth Beta release.
TEAM WORK
How did we tackle this?
Forming our team
My co-lead and I formed our UX writing team by interviewing over 12 candidates and selecting 2 apprentices within a week based on time zones and skill.
Team Collaboration
We held bi-weekly sprints, regular team meetings, and all-hands sessions with 20+ members. We reviewed previous UX handoff materials and sought guidance from other teams to clarify our scope and roadmap.
Image: FigJam All hands meeting
Let's delve deeper into the design problems our team encountered and the solutions we implemented.
THE DIRTY BUSINESS
Problems + Design Solutions
Problem 1:
We had no guideline…
So,
We created a style guide and voice chart to showcase our branding and writing style. This wasn't prompted by feedback but served as a valuable warm-up exercise for the writing team.
Problem 2:
User confusion…Blockchain Knowledge?
You get it…basically our users were confused and underconfident with the vocabulary in the app. We found this from the previous phase’s usability testing.
Let’s dig further and see who really are our users…
Image: Initial State of Affairs AKA issues
Image: User Personas from Phase 4
What are NFTs?
Click on the image to zoom
Image: Preliminary definitions
…and narrowed it down to these
In order to familiarize users with blockchain terminology & based on Design & Research Team recommendations, we developed a test token tooltip. We conducted desk research and team workshops to create copy options, preparing two solutions for testing.
FAQ Articles
Image: Testnet & Test Token tooltips options
Problem 3: **Twist in the plot**
“
Outcome: We handed off testing items to the UXR team, but the testing never happened.
How did we test effectiveness? We didn’t. Despite having everything ready, the Research team never conducted the testing. A complete standstill.”
Problem 4: Review and edit FAQ
We filtered top FAQs from Phase 4 and online research to match the product’s tone and needs.
To be added as accordions on the landing page for a clean look.
Are cryptocurrency transactions reversible?
Image: Filtered top FAQ from Phase 4
What is a private key?
What to do if I lose access to my wallet or private key?
We also defined Wallet vs Account and if there's a functional difference between the two.
…Sadly, none of the above changes could be put into testing during this phase, because of the time constraints and lack of motivation & clear goals from the Research & Product Strategy team. This will be the main priority in the next phase…
How do I look finally?
THE IMPACT
Finishing off Phase 5- Reflections & Learnings
Prior phase analysis showed users had to leave NFT wallets to trade and buy NFTs. This led to development of Kadet Wallet, enabling in-wallet NFT transactions, making Kadet a market leader.
Did we have challenges? Off course!
Project Clarity
Lack of clear goals, unclear roadmap, coupled with time zone differences, caused confusion, low motivation, and poor team collaboration.
LESSONS
Learnings for future
Time constraints
Tight timelines prevented us from completing FAQ articles, proofreading designs, and drafting copy for the Chrome Web Store.
Consistent Ambiguities
This led to research team not pursuing the usability testing, leading to uncertainty and an overall ambiguity in this phase design.
Mid-Phase Check-Ins
Implement regular check-ins for each team to monitor progress and address any issues promptly.Availability Updates
Regularly update and communicate team members' availability to ensure smooth collaboration and resource planning.Clear Communication
Emphasise the importance of clear communication, structured planning, and continuous updates to enhance project goals, workflow and project outcomes.Proper Documentation
Ensure thorough documentation and handover processes for seamless transitions to the next phase.