Overview
PROBLEM
The process of requesting a Riot Sign On (RSO) Client was inaccessible to third-party developers and time consuming for producers on the team.
OUR APPROACH
Our goal was to reduce the long communication process faced by external developers and Riot Producers, as well as increase the integration of RSO. We wanted to provide external developers with the opportunity to request an RSO Client, which will reduce the amount of back-and-forth communication with the team and the time it takes to get a Client integrated.
PROCESS
Understanding Users' Needs
Our users consisted of two groups of people: External developers and Riot Producers - each with different goals.
PROCESS
User Journey Mapping
I crafted three different user journeys detailing the current user experience, future-state (before automation), and future-state (after automation). These outlined the user actions, as well as pain points in the journey and where improvements could be made.
PROCESS
User Flow Mapping
I created flow maps to detail out the steps and flows we would need to account for as we started design work. Afterwards, I held collaboration sessions with my cross-functional team to review user maps in order to foster alignment and make sure that we accounted for every aspect of the user journey. These user flows were also instrumental in feature prioritization.
APPROACH
Design Goals
Faster Approval
Reduce the total time to API access request approval for external developers by automating parts of the external dev RSO client request process.
Designing for Support
Minimize common points of confusion for external developers with supportive content and interaction design.
Increased Efficiency
Increase efficiency of the Dev Relations team so that they can spend more of the time on emergent issues and troubleshooting.
DESIGN
Early Explorations
I started off with exploring different form displays and navigation for the client form, such as breaking down the form so it is more digestible, and utilizing a progress indicator to navigate through the form.
Because the form didn’t have too many fields, we decided to keep it simple with a scroll navigation.
