This image captures the competitive research phase of the Ledn Transfer project, showcasing a careful analysis of peer-to-peer payment services. It highlights key interfaces from various competitors, focusing on identifying best-in-class features.
Research
Industry Benchmarking
Conducted an extensive review of best-in-class peer-to-peer payment services in the crypto industry.
Identified leading features and practices that set industry standards.
Platform Analysis
Performed a comprehensive evaluation of the existing Ledn platform.
Identified current offerings and pinpointed user pain points and areas for improvement.
Competitive Analysis
Analyzed competitors to understand their strengths and weaknesses.
Used insights to inform the development of a unique and competitive peer-to-peer transfer feature for Ledn.
This image shows the ideation session for the Ledn Transfer project, with boards of organized purple post-it notes capturing the team’s brainstormed ideas.
Ideation Session
Core Objectives
Prioritized understanding the key goals: fee-free global transactions and expanding the user base.
Focused on creating an accessible service for both current and prospective Ledn clients.
Workshop Dynamics
Initiated workshops with a clear articulation of our objectives on FigJam.
Analyzed top features from industry leaders to inform our feature set.
Emphasized a wide-ranging brainstorm to foster innovation and inclusivity.
Leveraged FigJam for real-time collaboration, allowing for an inclusive idea-sharing environment.
Encouraged a free exchange of ideas, documenting all suggestions for consideration.
The image captures a prioritization workshop for the Ledn Transfer platform, where stakeholders on the left evaluate user goals and feature relevance, and on the right, an impact-effort matrix is utilized to classify features for the MVP development.
Feature Prioritization Workshop
In the strategic phase of our project, we conducted a prioritization workshop to meticulously refine the feature set for the Ledn Transfer MVP:
Collaborated with stakeholders to assess the array of features proposed during the ideation phase.
Utilized an impact-effort matrix to evaluate and rank each feature's importance and implementation complexity.
Divided features into essential 'Must Have,' important 'Should Have,' and beneficial 'Nice to Have' categories, establishing a clear roadmap for MVP development.
Feature Consolidation
Must have
💲Fee Transparency: Demonstrating potential fees to highlight the platform's cost-efficiency.
📱 Interactive UI: Facilitating amount entry with a full-screen keyboard interface.
😊 Enhanced User Experience: Adding personal touches like emojis and notes to transactions.
👤 User Verification: Smart identification of whether an input is a handle, email, or phone number.
🌐 Global Entry Point: Ensuring seamless fund transfers from various app interfaces.
📋 Transaction Visibility: Displaying balance and transaction values in multiple currencies.
👥 Contact Management: Streamlining the process to add or select transaction recipients.
Should have
📈 Incentivization: Introducing rewards to promote the peer-to-peer transfer feature.
🔒 Security Options: Providing a toggle for time-lock features to secure transactions.
📕 Address Book Integration: Simplifying the process of adding and choosing contacts for transactions.
Nice to have
📈 Incentivization: Introducing rewards to promote the peer-to-peer transfer feature.
↔️ Request Money Feature: Allowing users to solicit funds, driving engagement within Ledn.
This image displays the evolution of a user journey map for the Ledn Transfer platform
Journey mapping
In shaping the Ledn Transfer user journey, I dove into mapping out the entire flow, carefully considering different user needs. This step was crucial for plotting a clear path forward. Alongside the team, we refined this map, making sure it reflected our collective vision and the key features we'd decided on earlier. I then walked our leadership and legal teams through the journey, ensuring everyone was on board and ready for the next steps.
This image showcases version 1 of the Ledn Transfer prototype, featuring six distinctive flows
Prototyping
Following the journey mapping phase, I developed an initial prototype, translating our conceptual flows into a tangible experience for Ledn Transfer. This prototype served as the first concrete version of our envisioned experiences.
This image presents the research plan along with five distinct user interface flows.
User TEsting
For the Ledn Transfer project, my approach to prototype testing and user feedback was structured and efficient:
Prototype Development: Created five user flow prototypes, each tailored to different user scenarios.
Research Plan: Developed a targeted research strategy to test these prototypes.
Collaboration with CS Team: Partnered with the Customer Service team to identify clients fitting our target user profile.
Client Recruitment: Successfully enlisted seven clients from our targeted group for UXR sessions.
Session Organization: Coordinated and scheduled one-hour sessions for in-depth user testing.
Facilitation and Feedback: Led these sessions, focusing on gathering actionable insights from participant interactions with the prototypes.
User Testing Findings:
Main Feedback Themes:
Ease of Use: Difficulty with crypto terminology; need for a glossary or tooltips.
Security Concerns: Desire for more transaction security assurances and error handling mechanisms.
Design and Layout: Readability issues in dark mode; suggestions for improved contrast.
Functionality Expectations: Requests for features like transaction notes and detailed histories.
Observed User Behaviours:
Help Seeking: Frequent search for guidance, indicating the need for accessible educational resources.
Verification Checks: Regular rechecking of recipient information; potential for an address confirmation step.
Trial Transfers: 'Test' transactions indicate a need for clearer transaction confirmations.
Transaction History Checks: Post-transfer reviews of transaction history.
Improvement Opportunities:
Educational Resources: Inclusion of in-app guides or tutorials on crypto transactions.
Security Enhancements: Features like two-factor authentication and transaction confirmations via email/text.
UI Adjustments: Address dark mode readability, offer font size options.
Additional Functionalities: Features for payment annotations, frequent contacts list, and detailed transaction insights.
Feedback Mechanism: System for real-time user feedback.
Final Experience
The image above captures the culmination of our design process in a comprehensive Figma file, which serves as a pivotal resource for the entire development team. This file contains the finalized experience designs, meticulously crafted to align with the validated concepts and project vision. It also includes detailed documentation and guidelines, ensuring that project managers, front-end, and back-end developers have a clear reference point to accurately bring the digital experience to life. Additionally, this file incorporates the definitive copy for the experience, providing a complete package for a seamless transition from design to development.
Developer Documentation
The image shows part of the detailed documentation for the Ledn Transfer project, with annotated examples explaining when screens should appear and error states should trigger. This guidance is crucial for the front-end team to display each screen accurately, ensuring the final product is true to the original designs. These images are select examples of the comprehensive documentation that supports the correct build-out of the experience.
Post MVP Follow Ups
FAQ Page Development:
Collaborated with the customer support team and project manager.
Created an extensive FAQ page for the Ledn Transfer project.
Aimed to provide clear, accessible information for users.
Marketing Push Assistance:
Supported the marketing team with essential design elements.
Contributed to the global launch campaign for Ledn Transfer.
Ensured effective reach and impactful messaging to the target audience.
Streamlined documentation was key, enabling a clear build process for the large team of developers. Detailed notes for each aspect of the interface ensured that everyone was on the same page.
Early stakeholder involvement is crucial. Involving departments like legal early on, especially before workshops, would streamline later stages by preemptively addressing needs such as disclaimers.
Positive outcomes included the front-end team's effective build-out thanks to the elaborate documentation and early engagement of the design system engineer, which provided time to develop new components for the developers' use.
