Concept artists want to pause and resume their virtual workstations instead of starting fresh every day. When they terminate a session, they lose their personalized settings and customizations. Keeping a session running for a long time increases the risk of problems like corruption. To fix this, we plan to automatically create a backup of their work to the cloud at regular time intervals. This way, they can easily restore their customized setup and data whenever they need it.
Below are important research findings from the PRD Quip document shared by my project manager. These user needs and pain points come from a combination of user research and feedback received from customers through SIM tickets.
This feature caters to two main user groups: artists and console Administrators. Artists utilize the portal to choose and restore backups, while console Administrators configure and activate the auto backup functionality in the AWS console. I am specifically responsible for the console-related aspects of the project, while another designer focused on the artist/portal component. I was given this persona as part of the project, and I did not contribute to the user research or the creation of this persona.
*I did not create this image; it was provided for reference.
We had two choices for implementing this new feature: integrate it into an existing side menu or create a dedicated menu specifically for it in the side navigation.
I developed two task flows: one for the standalone version and another for the embedded version. Both iterations underwent multiple revisions following meetings and discussions.
To implement this new feature, we had two options: integrate it into an existing side menu or create a dedicated menu in the side navigation exclusively for it. To provide stakeholders with a clear view and allow them to make a decision, I proceeded simultaneously in both directions.
Although the PM and developers leaned towards the embedded version, my intuition felt that the stand-alone version offers better discoverability and usability. To determine the customers' actual preferences, I opted to conduct an user preference test.
The results revealed that target users unanimously favored the stand-alone version. Here are a few key findings derived from the test result:
After the AB Test, the design went thru several iterations based on engineering constraints, technical requirements, and stakeholder feedbacks.
Despite the user preference for the stand-alone version, coding difficulties and time constraints prevented us from implementing it before the launch date. Therefore, as a group, we collectively decided to opt for the embedded option for the initial release.
Following the PM's decision, we decided to merge the root volume and auto backup into a single section. To accomplish this, I worked closely with the designer responsible for the root volume project, the UX writer, and other important stakeholders. Together, we collaborated to revise the design, and the outcome of our collective effort is presented below.
2 additional columns were added in the launch profile table to improve the visibility of system status and feedback. After the IT admin enables auto backup in a launch profile, the status in the auto backup column will change from off to on. Same goes for turning on and off of persistence storage.
After several rounds of iterations with the PM, developers, UX writers, and QA engineers, the design went live on Dec. 20, 2022. It was also showcased during AWS re:Invent 2022.
To enable auto backup, the IT admin needs to activate persistent storage. Initially, the feature remains hidden until persistent storage is turned on. Once the admin checks the "Turn on auto backup" checkbox, additional options become visible. These options allow the admin to adjust the maximum number of backups per streaming session, with a default value of 6. After clicking the "Update Launch Profile" button, auto backup is enabled. As a result, the persistence and auto backup cells in the launch profile table will change their status from "off" to "on".
Both the IT admin and the artist have the ability to restore from a previous backup. However, the streaming session must be in the stopped state to proceed with the restoration process. This precaution is in place to prevent accidental shutdowns and data loss. To restore from a backup, the IT admin should follow these steps:
In order to enable auto backup, the IT admin must check the “I understand that streaming session storage backups incurs a cost. Go to the Nimble’s pricing page for more information about pricing.” check box. This is to ensure that the user knows this feature is not free. We don’t want to surprise the user with an unexpected bill.
This feature achieved instant success, as confirmed by my project manager (PM). The feedback from users and results from user testing were outstanding. Every week, there was a growing number of new adopters. Within the initial 6 months, approximately 75% of our existing EBS customers had enabled backup. Here are some estimated key performance indicators (KPIs).
The final outcome of the feature was well received by both upper management and the end customers. Although we had to make compromises due to technical and time limitations, the result turned out to be a resounding success. This experience has taught me valuable lessons about making informed decisions with a cross-functional team and maximizing the available resources. Despite the positive reception, I acknowledge that there is always room for improvement. Taking this into consideration, the project manager and I have agreed to explore the stand-alone option for the next iteration, aiming to deliver even better results.
