Initial research from leadership reported a high new user drop-off rate of 66.7% since the start of 2023. To investigate and remediate this, my product manager and I were given ownership of the new Onboarding area.

By facilitating design research methods and synthesizing results, we successfully created a roadmap of projects that address issues client's face when onboarding to the Level Access platform.

TeamProduct Designer (me!)
Product Manager
UX writer
Lead UX Researcher
Director of UX Research and Strategy

Time FrameSept. 2023 - Jan. 2024

OrganizationLevel Access

How might we improve the onboarding experience to engage users with features earlier and increase the number of new users added to our platform?

Taking action: Following the research process

The research process is never linear, especially when working in agile product development.
Nonetheless, I tried to divide the stages the product manager and I addressed while going through researching the onboarding product area.

Goals + Hypothesis: Why are we addressing this problem?

Onboarding focused on ensuring external and internal users have the tools they need to onboard clients and keep them retained.

Hypothesis:
By supporting users during onboarding, we will increase the number of customers that engage with and continue to engage with the product.

Methods: Forms of research collection

Research Methods

Current state analysis: Understanding the workflows of internal teams

There are several stakeholders who work with customers during the onboarding process. We interviewed internal team members to establish the current process of onboarding new clients.

I had the opportunity to shadow communication calls with net new clients to hear these pains first hand.

Developing a Research Plan: Filling information gaps

To address the gaps in information outlined by the journey map, I created a research plan to create alignment and plan out user recruitment.

User Recruitment & Interviews


6 external interviews & 2 internal interviews

Recruitment requirements:

Qualitative research questions:
  • When did you sign with us/what was the process?
  • Tell me about how it went from there; how’d you get familiarized with the platform? --> Where did you start?
  • Was there anything you found confusing?
  • What were the most critical parts of our software/services for you guys to get set up first?
  • How did you educate or understand these services?
  • Is there anything you know now that would’ve made you approach it differently if you could go back in time?

Journey Mapping: Creating one source of truth


All of the findings and quotes from the user interviews were recorded in confluence. However, it was difficult to search and find specific pains from pages and pages of notes.

The journey map was created to synthesize all of our findings and to create one document to reference throughout future ideation.

Identifying Opportunities: Affinity mapping the pains to discover solutions


After updating the journey map, with mentorship from my design team lead, I organized the pain into three themes. Affinity mapping not only helped us establish opportunities but, made it easier to communicate to leadership.

All of the projects were mapped to the user pain points to ensure we are solving and reating value at every step of the way.

Scroll through affinity mapping diagram.

Outcome: Turning opportunities into projects

This initiative was the basis for all the projects not only I but, other product teams continue to work on at Level Access. The result was a year-long roadmap that was received positively by leadership.

Out of all the projects, building a checklist, improving empty page states and adding descriptions were direct results of this research.

Onboarding Checklist

To guide users to key tasks in the platform and address pains in understanding those tasks and features.

Empty Page States

To encourage independent set-up by taking users to their first action.

Descriptions

To provide context to features, screens and tasks.

Testing & Refining: Validating possible solutions with users

Implementation: Adapting the design process to the agile software environment

Onboarding checklist


Originally, this experience was designed to be in product but, after discussion with the research team, we released an MVP through Pendo, a third-party pop-up application to collect feedback before implementation.

Empty Page States & Descriptions


Implementing these screens were a breeze. The plan was to slowly improve empty states in each feature of the platform by implementing with each sprint and release. We added them to sprints where our scrum team had room to work on an additional project/had story points to spare.

Impact: How did we measure success?

This research initiative resulted in 12+ items on the roadmap, 8 new features launched and honestly, a better relationship with our new customers. Each of the projects succeeded in addressing key issues in onboarding resulting in the following metrics: