Moody Rooster Design
appoptics.png

AppOptics: Onboarding

Product Design, UI/UX
AppOptics: Onboarding

AppOptics: Onboarding

AppOptics is a new SaaS product that helps DevOps teams effectively monitor their infrastructure and applications. The product is a combination of several complementary brands seamlessly combined to offer a more comprehensive cloud solution.

The Goal

The Goal

I was charged with helping to define the onboarding process for new users. The goal was to help new users get to a dashboard with meaningful metrics in the cleanest and quickest manner possible.

This may seem standard, but in many cases traditional onboarding of monitoring products would allow users to skip the installation process (without installing an agent) and arrive at an empty dashboard. 

After reviewing with engineers, product managers and product leads it was agreed that this approach was not fulfilling to the user. Though it might mean less new users technically onboard, we felt the best experience would be to make a successful installation of an agent mandatory to completing the onboarding process. Value from the product is derived from gaining insight into your metrics and if you don't have anything hooked up the product is useless and a trial period will not serve it's purpose. 

The Challenge

The Challenge

Instrumenting your environment can rapidly become a very complex process. Traditional installation processes would dump all relevant information you might need for any configuration at one time and it was laborious, cumbersome and heavy to take in at one time as a user.

Multiple operating systems, languages, environments, teams, permissions and a black hole of issues relating to AWS integration meant we needed to be as simplified as possible and give the user a digestible path to success.

 Additionally, much of the UI and legacy interaction we used as a starting point was based on a collection of previous products that were being combined. We had very strict time constraints and therefore opted to leverage reusable components from existing installation infrastructure and make a few key tweaks to improve the flow and be more streamlined.

Additionally, much of the UI and legacy interaction we used as a starting point was based on a collection of previous products that were being combined. We had very strict time constraints and therefore opted to leverage reusable components from existing installation infrastructure and make a few key tweaks to improve the flow and be more streamlined.

 To do this we created an "installation process of elimination" by making users choose options that would allow us to eliminate related options that wouldn't be applicable. By eliminating these broad overarching variables in the beginning it allowed us to display a more consumable amount of installation information in smaller relevant tidbits to the user. This really helped build a feeling of accomplishment and momentum with checkpoints in comparison to dumping all possible information and hoping for the best with an option to skip out of frustration.

To do this we created an "installation process of elimination" by making users choose options that would allow us to eliminate related options that wouldn't be applicable. By eliminating these broad overarching variables in the beginning it allowed us to display a more consumable amount of installation information in smaller relevant tidbits to the user. This really helped build a feeling of accomplishment and momentum with checkpoints in comparison to dumping all possible information and hoping for the best with an option to skip out of frustration.

05.gif