INTRODUCTION
The current user verification process on Autodesk Account is not streamlined.
Admins are responsible for managing the entire lifecycle of a subscription — from purchasing to managing software. They need to get users verified and accessing software as soon as possible. However, this verification process continues to cause admins pain, causing more stress in their workload.
Increase in sign-in support case volume since 2023
HOW MIGHT WE…
Inform admins of unverified users and help admins take quick actions on those users?
Breaking down the current user invitation process on Account with primary research.
To delve into this unique problem space, I began my process by conducting an in-depth audit of the invite experience from the admin perspective. Then, I collaborated with a senior UXR to collect 30+ survey responses from admins, conduct 2 contextual inquiries, and interview 5 admins in the monthly customer council to understand sentiments.
Pinpointing the problem — key friction points preventing admins from user verification.
Complete reliance on the end user
The verification process is dependent on end users’ actions. Admins are not notified of problems unless contacted by users themselves and won't check in on Account on their own accord.
Invitation status is stuck in a "black box"
Admins are unaware when pending invites are about to expire, and only learn about problems weeks or even months after the initial invite. The average resend time is approximately 20 days.
Account processes are not efficient
The current experience does not provide support in locating and troubleshooting unverified users, leaving admins unsupported. Autodesk is currently not positioned a partner in admin success.
Competing user management platforms support their admins with features to remain in control.
Based on a competitive audit of 6 competing user management platforms and features, admins experiences in other companies have increased visibility and control over the user verification experience, as seen below.
Microsoft: Admin creates accounts for each end user and can view the time stamps of any previous sign-in attempts.
Atlassian: In Jira system settings, admins can view a log detailing processing information if an invite is pending.
Google: Rather than resending invites, admins reset user passwords and can preview information before sending.
Adobe: Removed the concept of invitations in 2019, but received backlash due to decreased control for admins.
Defining product pillars — locating design imperatives for the solution experience.
Enhanced autonomy
Admins have the needed features to feel in control of verification and don't have to rely on end users for progress updates.
Increased visibility
Admins are aware of all current unverified users on all teams and can quickly locate which users are still pending verification.
Efficient decision-making
Admins have all needed information to make informed decisions, ensuring that pending users get verified as quickly as possible.
Design Decisions — Decomposing our guiding question into smaller design subproblems
Though I had a solution direction, I wanted to break down my larger design question into smaller problems, so I can understand and evaluate how to best reconstruct the user flow from an end-to-end perspective.
SUBPROBLEM #1
HOW MIGHT WE…
provide admins with enough user information to make informed actions?
Breaking Down The Current User Card
Currently, users are grouped together in a single table, with each row containing relevant information. However, one significant limitation of the current UX is that lack of insight into the status of pending invites.
Evaluating Iterations Against Principles
With this in mind, I explored various approaches to redesigning the card. Throughout this process, I spearheaded workshops with my mentor and PM to get feedback on the designs' alignment with three product pillars.
Low familiarity: Five column layout does not align with other card experiences in Account
Medium visibility: Provides admins with minimum processing information to make decisions
High efficiency: Process information can be accessed easily, minimal loading time
High familiarity: Four column layout aligns with other card experiences in Account
High visibility: High detailed information for admins to understand current obstacles
Low efficiency: No existing API in back-end to collect this processing information
High familiarity: In-line layout exists in the design system (e.g. email in the "Name" column)
Medium visibility: Provides admins with minimum processing information to make decisions
High efficiency: Process information can be accessed easily, minimal loading time
Nuances in Language
Before finalizing this approach, I collaborated closely with a Senior Content Designer to understand how language can influence behavior and how we can evoke a sense of urgency for timely troubleshooting.
Experience Review — How are invited users currently displayed on Autodesk Account?
One of the biggest pain points faced by admins is the lack of visibility into unverified users. In the existing user flow, admins have to manually click on "Account Status" to view all unverified users together.
SUBPROBLEM #2
HOW MIGHT WE…
enhance the visibility of unverified users to increase admin awareness?
Explorations & Conversations
The goal of this design enhancement is to surface unverified users from the rest of the team, creating a clear visual distinction between these two types of users and encouraging quick troubleshooting by admins.
Lack of scalability: Layout requires complicated API call-back, causes problems with pagination
Clear distinction: Table layout allows for clear separation between verified and unverified users
Limited to two-role teams: End user can be more than verified/unverified (e.g. primary admin)
Ease of implementation: Feasible engineering-wise, UI matches with an existing pattern in Account
Scalable & Universal: Aligns with other ongoing initiatives within Core Admin Productivity team, scalable to more filter options in the future
Balancing Engineering Constraints
Given the project's deadline and the stressed importance on feasibility of implementation, I spearheaded regular workshops with my engineering lead to understand engineering limitations early in the process — this informed how I evaluated each iteration above. By involving stakeholders in early conversations, I ensured that my designs not only addressed user needs but was realistic in the desired timeframe.
Experience Review — How do admins currently troubleshoot problems with unverified users?
For my final design subproblem, I needed to tackle one of the biggest admin friction points — the lack of efficient workflows. In the current experience, each user needs to be reinvited individually. For admins that manage teams of hundreds of users, this task become extremely tedious.
SUBPROBLEM #3
HOW MIGHT WE…
streamline the resend invite process, minimizing the time needed to troubleshoot?
Evaluating Actions with Concept Testing
Because it's essential to understand how my solution would integrate into existing admin flows, I scheduled 5 semi-moderated testing sessions to measure usability. During these sessions, I tested three different actions.
Option 1: Individual Resend Action
Option 2: Bulk Action Bar
Option 3: External Action Button
Understanding Admin's Mental Models
Observing directly how admins interact with the different flowers was extremely insightful and challenged my previous conceptions. From this process, I derived two key insights to inform my design decisions.
INSIGHT #1
Though being able to make quick actions is important, admins value having the choice between bulk action and individual troubleshooting based on situation or preference.
INSIGHT #2
Mental models influence behavior
Admins are familiar with existing flows on the platform. Because of this, they have been trained to expect certain results based on behaviors (e.g. clicking the bulk action bar).
I decided to proceed with the bulk action bar. This approach aligns with the users' mental models and existing behaviors, making it more intuitive for them. By leveraging the bulk action bar, we not only provide admins with the flexibility they need to manage invites efficiently but also maintain a consistent experience that aligns with their established workflows — aligning with the two key insights from user testing.