# UX Research Analysis & Synthesis **Project:** Cross-border B2B Payment Tracking & Invoice Management Mobile App **Research Goal:** Understand friction during international wire transfer setup and identify causes of drop-off at bank verification and onboarding stages. --- # STAGE 1: DATA ANALYSIS (Extraction & Coding) ## 1. Verbatim Quotes & Behavioral Patterns ### Pattern A: Fear of Financial Errors & Loss | Verbatim Quote | Behavioral Signal | | ----------------------------------------------------------------------------------- | ---------------------------------------- | | "I panicked a bit. Like, what happens if I type one digit wrong?" | Anxiety caused by irreversible actions | | "Will my $3,000 just vanish into space?" | Fear of financial loss | | "There was no reassurance on the screen." | Missing trust-building mechanisms | | "I just need to know my money is safe and where exactly it is at any given second." | Strong need for transparency and control | **Observed Behavior:** * User pauses at high-risk moments. * User seeks certainty before committing. * Lack of reassurance triggers abandonment. --- ### Pattern B: Knowledge Gaps & Financial Jargon | Verbatim Quote | Behavioral Signal | | ------------------------------------------------------------------------- | ---------------------------- | | "It asked for an IBAN, a SWIFT code, and some intermediary bank details." | High information complexity | | "No tooltips explaining what an intermediary bank even is." | Missing contextual education | **Observed Behavior:** * Users encounter unfamiliar terminology. * Users lack confidence in completing the task correctly. * Cognitive load increases significantly. --- ### Pattern C: Trust Migration Toward Familiar Systems | Verbatim Quote | Behavioral Signal | | ----------------------------------------------------------------------------------- | ------------------------------------ | | "I closed the app and opened my desktop banking app instead because it felt safer." | Users revert to trusted alternatives | | "Even though their fees are higher." | Trust outweighs cost savings | **Observed Behavior:** * Users prefer familiar environments when risk perception rises. * Economic incentives alone do not overcome trust deficits. --- ### Pattern D: Poor Error Recovery Experience | Verbatim Quote | Behavioral Signal | | ------------------------------------------------- | ------------------------------ | | "It kept rejecting my company registration PDF." | Workflow blockage | | "It just said 'Upload failed, invalid document.'" | Non-actionable error messaging | | "What does that even mean?" | User confusion | **Observed Behavior:** * User cannot diagnose the problem. * Error message creates uncertainty instead of resolution. --- ### Pattern E: Time Pressure & Efficiency Expectations | Verbatim Quote | Behavioral Signal | | ----------------------------------------------------------------------------- | ------------------------------------- | | "I don't have time to guess what the system wants." | Low tolerance for trial-and-error | | "I ended up calling customer support." | Escalation due to failed self-service | | "If this app is supposed to save me time... it's failing right at the start." | Broken value proposition | **Observed Behavior:** * Users evaluate onboarding through the lens of efficiency. * Delays directly reduce perceived product value. --- ## 2. Thematic Coding | Theme | User Pain Point / Goal | Mental Model / Expectation | | ---------------------- | ------------------------------------------------------- | ----------------------------------------------------------------- | | Trust & Security | Fear of sending money incorrectly | "Financial tools should actively reassure me before I commit." | | Financial Complexity | IBAN, SWIFT, intermediary bank terminology is confusing | "The system should translate banking jargon into plain language." | | Transaction Visibility | Lack of confidence in money movement | "I should always know where my money is." | | Error Prevention | Fear of irreversible mistakes | "The app should help me avoid errors before submission." | | Verification Process | Document upload failures without explanation | "If something is wrong, tell me exactly what to fix." | | Efficiency | Support calls and repeated attempts waste time | "The app should be faster than traditional banking." | | Guidance & Education | No contextual help during critical steps | "The product should guide me through unfamiliar processes." | | System Feedback | Generic error messages create uncertainty | "The system should explain what happened and what to do next." | --- # STAGE 2: DATA SYNTHESIS (Affinity Mapping & Insights) ## 1. Text-Based Affinity Diagram ### Trust & Risk Perception * Fear of entering incorrect banking details * Fear of losing money * Lack of transaction reassurance * Switching to traditional banking channels ### Information Architecture & Comprehension * Confusing banking terminology * No explanation of intermediary banks * Lack of contextual guidance * Missing educational content ### Error Handling & Recovery * Generic upload failure messages * No indication of acceptable document requirements * Users unable to self-correct ### Efficiency & Productivity * Lengthy verification process * Support wait times * Repeated upload attempts * Failure to deliver promised time savings ### Visibility & Control * No clear transaction status expectations * Uncertainty about transfer progress * Lack of transparency throughout workflow --- ## 2. Core UX Insights ### Insight 1: Users Are Not Abandoning Because of Complexity Alone—They Are Abandoning Because Complexity Feels Dangerous The transfer flow introduces unfamiliar financial concepts at the exact moment users perceive maximum financial risk. The issue is not merely understanding IBANs or SWIFT codes; it is the fear that misunderstanding them could result in irreversible monetary loss. **Underlying psychology:** * Loss aversion * Risk avoidance * Fear of irreversible consequences --- ### Insight 2: Trust Is Earned Through Transparency, Not Branding Despite higher fees, users returned to traditional banking platforms because those systems provided a stronger perception of safety and familiarity. The competitor advantage is not pricing—it is perceived reliability. **Underlying psychology:** * Status quo bias * Familiarity bias * Institutional trust --- ### Insight 3: Generic Errors Force Users Into Detective Work The document upload flow transfers diagnostic responsibility from the system to the user. Instead of telling users what failed, the system makes users investigate possible causes independently. **Underlying psychology:** * Cognitive overload * Learned helplessness * Decision fatigue --- ### Insight 4: Users Measure Value During Onboarding, Not After It The promise of efficiency is evaluated immediately. Every confusing form, rejected document, or support interaction becomes evidence that the product may not deliver on its core value proposition. **Underlying psychology:** * First-impression effect * Expectation-confirmation theory --- ### Insight 5: Financial Users Need Predictability More Than Speed Users are willing to spend additional time if they understand what is happening and why. Uncertainty creates more friction than duration itself. **Underlying psychology:** * Need for control * Ambiguity aversion * Predictability preference --- # STAGE 3: ACTIONABLE UX ARTEFACTS & ROADMAP ## 1. How Might We (HMW) Statements ### HMW #1 How might we reduce users' fear of making irreversible mistakes when entering international banking information? ### HMW #2 How might we provide immediate, actionable feedback when verification documents fail validation? ### HMW #3 How might we increase users' trust and confidence throughout the international transfer setup process? --- ## 2. User Stories ### Freelancer Persona **As a freelancer,** I want clear explanations for IBAN, SWIFT, and intermediary bank fields, **so that** I can confidently submit an international transfer without worrying about losing money. --- ### Small Business Owner Persona **As a small business owner,** I want precise explanations when a document upload fails, **so that** I can quickly fix the issue and continue onboarding without contacting support. --- ### Financial Manager Persona **As a financial manager,** I want visibility into transfer progress and verification status, **so that** I can monitor transactions confidently and provide updates to stakeholders. --- ## 3. Prioritized UI/UX Recommendations (Impact vs Effort Matrix) ### 🚀 Quick Wins (High Impact / Low Effort) | Recommendation | Expected Outcome | | ------------------------------------------------------------------------------ | ------------------------------------ | | Add contextual tooltips for IBAN, SWIFT, and intermediary bank fields | Reduces confusion and cognitive load | | Replace generic upload errors with specific validation messages | Improves self-service recovery | | Add inline examples and formatting hints | Prevents input mistakes | | Display accepted file types, size limits, and sample documents before upload | Reduces upload failures | | Add trust microcopy ("Your funds are protected and verified before transfer.") | Increases confidence | --- ### 🎯 Major Projects (High Impact / High Effort) | Recommendation | Expected Outcome | | ------------------------------------------------------------------------------ | ---------------------------------- | | Guided wire-transfer wizard with progressive disclosure | Reduces complexity and abandonment | | Real-time banking detail validation (IBAN/SWIFT verification) | Prevents costly errors | | Transfer journey visualization ("Initiated → Verified → Sent → Received") | Increases transparency | | AI-assisted document verification feedback | Improves onboarding completion | | Dynamic risk-reduction UX with educational explanations based on user behavior | Builds trust at critical moments | --- ### 📌 Fill-Ins (Moderate Impact / Low Priority) | Recommendation | Expected Outcome | | ----------------------------------------------- | ----------------------------------------------------- | | Embedded FAQ within onboarding | Reduces support dependency | | Live chat escalation from verification screens | Faster issue resolution | | Save-and-return onboarding flow | Allows users to gather information without restarting | | Educational glossary for international payments | Supports long-term learning | --- # Executive Summary The dominant cause of drop-off is **not usability alone—it is perceived financial risk combined with insufficient system guidance**. Users encounter unfamiliar financial concepts, receive little reassurance, and fear irreversible mistakes. Simultaneously, the verification flow creates frustration through vague error messages that prevent successful self-recovery. The highest-impact opportunities are: 1. **Increase trust through transparency and reassurance.** 2. **Reduce cognitive load through contextual guidance and progressive disclosure.** 3. **Improve error recovery with actionable, specific feedback.** 4. **Provide transaction visibility and validation before commitment.** 5. **Transform onboarding from a compliance task into a guided, confidence-building experience.**