<– Back
Learning Management System
TrainingMug, Internship ––June '23
My Role
UX Lead — Interaction Design, Visual Design, User Flows, Rapid Prototyping
Team
Austin Fisher, UXE Dean Whillier, UXE Bryan Coutch, SWE Ben Whittaker, SWE Christina Lee, PM
Timeline & Status
2 Months, Launched in January 2023
Overview
Following the announcement of Stadia’s shutdown, questions remained on what would happen with the platform’s Wi-Fi proprietary controller — whether they could still be used wirelessly, or become e-waste. I led the end-to-end design direction of the web experience for enabling Bluetooth on the controllers and played a pivotal role in defining the update process. The website's launch was met with outstanding public sentiment from the community and publications, alongside 1 million+ successfully updated controllers.
HIGHLIGHTS
An end-to-end update experience for enabling Bluetooth on Stadia Controllers to preserve their wireless functionality post-sunset.
VIDEO LOOP
0.1
Homepage motion concept
Type
Exhibit #
Desc
Type
Exhibit #
Desc
Type
Exhibit #
Desc
Type
Exhibit #
Desc
CONTEXT
An opportunity to go out with a bang.
The message was loud and clear.
Enabling Bluetooth on the Stadia controllers was the biggest request from the community. Above all else, it was the right thing to do, and an opportunity to overdeliver.
Type
Exhibit #
Desc
Type
Exhibit #
Desc
THE PROBLEM
This wasn't going to be your typical firmware update.
A pile-up of constraints.
Firmware updates were usually delivered automatically. However in our case, this was not possible because the size of this update was too large and that the platform was shutting down.
The decision was made to build a first-party website as the update tool — which came with its own set of unique constraints and challenges:
A two month deadline, because we had to launch before the sunset date.
Hardware access nuances. The controller had to be put into a rare "boot menu" mode.
Clunky by design. Hardware security access wasn't intended to be user-facing.
Limited to a static website. No way to dynamically verify controller input during update process.
THE CHALLENGE
Take an otherwise highly unorthodox update process and package it into a website to be as intuitive, error-free, and desirable as possible.
North Star design principles:
Concise Clarity
Clear, informative, and straight-forward instructions.
Concise Clarity
Clear, informative, and straight-forward instructions.
Concise Clarity
Clear, informative, and straight-forward instructions.
Type
Exhibit #
Desc
UPDATE FLOW
The backbone of the project.
You gotta start somewhere.
The hardware team provided me with a list of mandatory update instructions on a static website which included an unorthodox Chrome dialog interaction (Figure 3.0).
Type
Exhibit #
Desc
Finding structure amidst the chaos.
To make sense of an otherwise unconventional set of instructions, I started by exploring ways to foster a perceived sense of progress.
Shown in Figure 3.1, categorizing instructions into four stages helped mitigate the cognitive load of seeing all the instructions at once.
Additionally, overly-technical terms were revised to better cater to a general audience.
Type
Exhibit #
Desc
Finding structure amidst the chaos.
To make sense of an otherwise unconventional set of instructions, I started by exploring ways to foster a perceived sense of progress.
Shown in Figure 3.1, categorizing instructions into four stages helped mitigate the cognitive load of seeing all the instructions at once.
Additionally, overly-technical terms were revised to better cater to a general audience.
Type
Exhibit #
Desc
Concise Clarity
Clear, informative, and straight-forward instructions.
Concise Clarity
Clear, informative, and straight-forward instructions.
Concise Clarity
Clear, informative, and straight-forward instructions.
Concise Clarity
Clear, informative, and straight-forward instructions.
Concise Clarity
Clear, informative, and straight-forward instructions.
Concise Clarity
Clear, informative, and straight-forward instructions.
Finding structure amidst the chaos.
To make sense of an otherwise unconventional set of instructions, I started by exploring ways to foster a perceived sense of progress.
Shown in Figure 3.1, categorizing instructions into four stages helped mitigate the cognitive load of seeing all the instructions at once.
Additionally, overly-technical terms were revised to better cater to a general audience.
Type
Exhibit #
Desc
Concise Clarity
Clear, informative, and straight-forward instructions.
Concise Clarity
Clear, informative, and straight-forward instructions.
Concise Clarity
Clear, informative, and straight-forward instructions.
Concise Clarity
Clear, informative, and straight-forward instructions.
Concise Clarity
Clear, informative, and straight-forward instructions.
Finding structure amidst the chaos.
To make sense of an otherwise unconventional set of instructions, I started by exploring ways to foster a perceived sense of progress.
Shown in Figure 3.1, categorizing instructions into four stages helped mitigate the cognitive load of seeing all the instructions at once.
Additionally, overly-technical terms were revised to better cater to a general audience.
THE CHALLENGE
Take an otherwise highly unorthodox update process and package it into a website to be as intuitive, error-free, and desirable as possible.
Type
Exhibit #
Desc
Finding structure amidst the chaos.
To make sense of an otherwise unconventional set of instructions, I started by exploring ways to foster a perceived sense of progress.
Shown in Figure 3.1, categorizing instructions into four stages helped mitigate the cognitive load of seeing all the instructions at once.
Additionally, overly-technical terms were revised to better cater to a general audience.
Type
Exhibit #
Desc
UPDATE FLOW
The backbone of the project.
You gotta start somewhere.
The hardware team provided me with a list of mandatory update instructions on a static website which included an unorthodox Chrome dialog interaction (Figure 3.0).
Type
Exhibit #
Desc
Finding structure amidst the chaos.
To make sense of an otherwise unconventional set of instructions, I started by exploring ways to foster a perceived sense of progress.
Shown in Figure 3.1, categorizing instructions into four stages helped mitigate the cognitive load of seeing all the instructions at once.
Additionally, overly-technical terms were revised to better cater to a general audience.
Type
Exhibit #
Desc
Type
Exhibit #
Desc
Concise Clarity
Clear, informative, and straight-forward instructions.
Concise Clarity
Clear, informative, and straight-forward instructions.
Concise Clarity
Clear, informative, and straight-forward instructions.
Concise Clarity
Clear, informative, and straight-forward instructions.
Concise Clarity
Clear, informative, and straight-forward instructions.
Concise Clarity
Clear, informative, and straight-forward instructions.
The Chrome dialog layout — breaking the rhythm.
The primary CTA was relocated to help bring focus to initiating the Chrome dialog interaction when it was required.
Disabling instinctive progression actions also further pushed the necessity of the interaction.
Type
Exhibit #
Desc
INTERACTIONS
It didn't have to feel like a static website.
Process of unlocking — failure prevention vs. ease of use.
Unlocking the controller to access the “boot menu” had inherently clunky origins by design. My initial approach was focused on failure prevention, through walking users through each micro-action one after another.
Though it appeared intuitive in theory, it was actually unnecessarily cumbersome in physical practice with actual hardware (Figure 5.0).
I made the pivot to an approach more conscious of hardware interactions and ease of use (Figure 5.1).
Type
Exhibit #
Desc
Type
Exhibit #
Desc
Concise Clarity
Clear, informative, and straight-forward instructions.
Concise Clarity
Clear, informative, and straight-forward instructions.
Concise Clarity
Clear, informative, and straight-forward instructions.
Concise Clarity
Clear, informative, and straight-forward instructions.
Concise Clarity
Clear, informative, and straight-forward instructions.
Concise Clarity
Clear, informative, and straight-forward instructions.
Concise Clarity
Clear, informative, and straight-forward instructions.
The Chrome dialog layout — breaking the rhythm.
The primary CTA was relocated to help bring focus to initiating the Chrome dialog interaction when it was required.
Disabling instinctive progression actions also further pushed the necessity of the interaction.
Type
Exhibit #
Desc
The Chrome dialog layout — breaking the rhythm.
The primary CTA was relocated to help bring focus to initiating the Chrome dialog interaction when it was required.
Disabling instinctive progression actions also further pushed the necessity of the interaction.
Type
Exhibit #
Desc
Type
Exhibit #
Desc
Concise Clarity
Clear, informative, and straight-forward instructions.
Concise Clarity
Clear, informative, and straight-forward instructions.
Concise Clarity
Clear, informative, and straight-forward instructions.
Concise Clarity
Clear, informative, and straight-forward instructions.
INTERACTIONS
It didn't have to feel like a static website.
Process of unlocking — failure prevention vs. ease of use.
Unlocking the controller to access the “boot menu” had inherently clunky origins by design. My initial approach was focused on failure prevention, through walking users through each micro-action one after another.
Though it appeared intuitive in theory, it was actually unnecessarily cumbersome in physical practice with actual hardware (Figure 5.0).
I made the pivot to an approach more conscious of hardware interactions and ease of use (Figure 5.1).
Type
Exhibit #
Desc
The Chrome dialog layout — breaking the rhythm.
The primary CTA was relocated to help bring focus to initiating the Chrome dialog interaction when it was required.
Disabling instinctive progression actions also further pushed the necessity of the interaction.
Type
Exhibit #
Desc
Type
Exhibit #
Desc
The Chrome dialog layout — breaking the rhythm.
The primary CTA was relocated to help bring focus to initiating the Chrome dialog interaction when it was required.
Disabling instinctive progression actions also further pushed the necessity of the interaction.
Type
Exhibit #
Desc
The Chrome dialog layout — breaking the rhythm.
The primary CTA was relocated to help bring focus to initiating the Chrome dialog interaction when it was required.
Disabling instinctive progression actions also further pushed the necessity of the interaction.
Type
Exhibit #
Desc
The Chrome dialog layout — breaking the rhythm.
The primary CTA was relocated to help bring focus to initiating the Chrome dialog interaction when it was required.
Disabling instinctive progression actions also further pushed the necessity of the interaction.
Type
Exhibit #
Desc
Type
Exhibit #
Desc
The Chrome dialog layout — breaking the rhythm.
The primary CTA was relocated to help bring focus to initiating the Chrome dialog interaction when it was required.
Disabling instinctive progression actions also further pushed the necessity of the interaction.
Type
Exhibit #
Desc
The Chrome dialog layout — breaking the rhythm.
The primary CTA was relocated to help bring focus to initiating the Chrome dialog interaction when it was required.
Disabling instinctive progression actions also further pushed the necessity of the interaction.
Type
Exhibit #
Desc
The Chrome dialog layout — breaking the rhythm.
The primary CTA was relocated to help bring focus to initiating the Chrome dialog interaction when it was required.
Disabling instinctive progression actions also further pushed the necessity of the interaction.
Type
Exhibit #
Desc
FINAL DESIGNS
It didn't have to feel like a static website.
Process of unlocking — failure prevention vs. ease of use.
Unlocking the controller to access the “boot menu” had inherently clunky origins by design. My initial approach was focused on failure prevention, through walking users through each micro-action one after another.
Though it appeared intuitive in theory, it was actually unnecessarily cumbersome in physical practice with actual hardware (Figure 5.0).
I made the pivot to an approach more conscious of hardware interactions and ease of use (Figure 5.1).
Type
Exhibit #
Desc
Type
Exhibit #
Desc
Type
Exhibit #
Desc
Type
Exhibit #
Desc
The Chrome dialog layout — breaking the rhythm.
The primary CTA was relocated to help bring focus to initiating the Chrome dialog interaction when it was required.
Disabling instinctive progression actions also further pushed the necessity of the interaction.
Type
Exhibit #
Desc
The Chrome dialog layout — breaking the rhythm.
The primary CTA was relocated to help bring focus to initiating the Chrome dialog interaction when it was required.
Disabling instinctive progression actions also further pushed the necessity of the interaction.
Type
Exhibit #
Desc
RETROSPECTIVE
It didn't have to feel like a static website.
Process of unlocking — failure prevention vs. ease of use.
Unlocking the controller to access the “boot menu” had inherently clunky origins by design. My initial approach was focused on failure prevention, through walking users through each micro-action one after another.
Though it appeared intuitive in theory, it was actually unnecessarily cumbersome in physical practice with actual hardware (Figure 5.0).
I made the pivot to an approach more conscious of hardware interactions and ease of use (Figure 5.1).
THE CHALLENGE
Take an otherwise highly unorthodox update process and package it into a website to be as intuitive, error-free, and desirable as possible.
Type
Exhibit #
Desc
Type
Exhibit #
Desc
Type
Exhibit #
Desc
Project Takeaways:
Concise Clarity
Viewing constraints from different perspectives helped brew new approaches to tackle other constraints.
Concise Clarity
Google's design resources were near unlimited — knowing where to find them and when to use them saved immense time and overhead.
Concise Clarity
It ensured that the project was progressing holistically — effectively accounting for content strategy and technical feasibility early.
Concise Clarity
If an added extra step led to a more intuitive and error-free experience, it was worth the additional manual effort.
Next Project:
CONTENTS
Overview
Highlights
Context
The Problem
Update Flow
Layout
Interactions
Visual Design
Final Designs
Retrospective
