Possible reasons for user drop-off after registration

Problem statement

Problem

Impact

Goals

Research

Methods

  • Journey mapping our onboarding process
  • Competitive analysis of their onboarding process
  • Analysis of Google Analytics data

Key findings

  • After signing up, users were unsure of the next steps.
  • They registered on a platform where our program isn't compatible, and we failed to provide instructions on how to proceed in this situation.

User personas (in short)

  • Marco, an 18-year-old beginner player, aims to become a professional esports competitor.
  • Lucas, a 35-year-old casual player, seeks to spend quality time with friends and have time for his hobbies.

Journey maps

  • We outlined all potential pathways from the registration process to the point where users can start using the AI coach.
  • Additionally, we conducted a competitive analysis of our biggest competitor’s onboarding process.

Ideation

Brainstorming

Concept development

Wireframes

Design

Prototype

Testing

Usability testing

  • We conducted a usability test with the completed prototype in a real sim racing environment.
  • Given that the application is designed for racing simulation games, we rented the esports facility at Széchenyi István University in Győr, equipped with four simulators.
  • We invited 20 participants to test the redesigned registration process and the initial user experience, which included completing at least three laps on a selected track. This allowed us to gather valuable insights into the onboarding flow and first-time user engagement.

Participants

Findings

  • Registration
    • No error message for incorrect email, making it hard to go back.
    • Users didn’t realize a PC was required for the product.
    • Users skipped important post-registration messages.
  • DataLink
    • Many skipped the tutorial and installed the DataLink incorrectly.
    • Users weren’t sure if the DataLink was ready and searched the FAQ.
  • First session
    • Post-Logging Confusion – Users checked the game or DataLink for session data instead of the web app.
    • Demo Session Confusion – Users struggled with filters and navigation due to lack of guidance.
    • Tutorial Issues – Many rushed through or skipped tutorials entirely.
    • Chart & UI Interactions – Users didn’t realize they could click or drag elements.
    • Reference Data Confusion – Users struggled to differentiate between reference options.

Iterations

Results

Reflections

Lesson Learned

Future Improvements

Check out my other case studies