VALORANT Console
Beta Launch
Led the creation of onboarding and invitation player workflows for VALORANT's console launch event. Coordinated workflows across teams and disciplines from inception through delivery.
Company
Riot Games | VALORANT
Senior UX Designer
Marketing Page
Getting Players Hyped To Register & Play
Clarity around registration process and event details. Make it easy for new players to learn about the game before playing. Leverage community videos to build excitement leading up to the opening. Using a new CMS system, the same information cards existing across the experience created consistency.
Registration Flow
What were the choices made before landing on the final outcome?
The "Perfect Experience" would be something that was simple, safe and reliable, scalable, and gave us the control levers to easily deliver this experience to a huge audience.
I focused on flows that allowed us to reuse functionalities in multiple instances. This reduced the scope of unique logic and one-off situations our engineers needed to build.
Emails To Users
Simple & Clear Branded Email Notifications
Registration confirmation and access notifications were sent by email and included high level information about the event, and additional game experiences.
Console Selection
Pick one platform but not both, cross-play isn't an option.
Users could play on their preferred platform, where their friends are. Each console partner had different requirements, and our flows allowed for new and pre-existing connections.
Invited By Friend
Aligned Content Across Use Cases
We reused as many assets as possible to keep scope in check, so content specific text was the main difference between an initial registration and being invited by a friend.
Redeeming A Friend's Invite
Aligned MVP Solution
Sharing The Invite Code
To make MVP launch dates, the simplest version allowing users to share access codes with friends was landed on. The result was a responsive flow, which provided users access through our system registration, and the ability to share an access code through their chosen method. Had we forced this experience through the console flow, it would limit user options. This solution allowed users to chose their own share path - be that email, discord, or text (as seen below!).
Error Pages
Good Messaging Can Guide & Reduce Frustration
We tried to account for as many potential edge cases as possible, and create the proper messaging to help users diagnose what happened.
