OpsCompass

Amazon pioneered the first path to the public cloud with AWS. With a full set of features to build and manage cloud applications, it’s still one of the best engineer platforms available. Although AWS has been here the longest, organizations share risk with anything implemented in the cloud. Changes open you up to risks in compliance, security, and unexpected costs, so better visibility is needed.

The new account onboarding flow was antiquated, and didn’t maximize the current features that were available to our users. Through working tirelessly with Cloud Engineers, DevOps, and Data Science teams I was able to create and implement a flow that allowed for full control and awareness throughout the process.

Step 1

Identify the Problem

Users could not properly add Cloud accounts without help from the team onsite, this caused support tickets, calls, and user frustration at the first touchpoint of the product. I created a series of aggregated user video recordings to ascertain where the problems occurred, and how to fix this for our users.

Step 2

User First Approach

Once the user flows were created and the engineering team could support the design on the coding side I tested the product with a small group of users that volunteered to be in a hosted session. This allowed access to insights not previously known and ultimately increased the products value by fostering user needs into business goals.

Step 3

Design Solutions

Through NPS & CSAT scores we refined the approach within the larger group and then released our new flow to the product on time and under budget. The leadership team then began showcasing this to biz dev meetings and through these product led examples showed a 5x increase in sign ups with this user centric approach.