top of page
Frame 1.jpg

Discovering & Monitoring with Intelligence

Web, B2B, Hybrid Cloud Content Management, Onboarding
One Sentence User Story

As a Tools Administrator, I want to discover all my hybrid cloud resources and apply monitoring without friction so that I can move to the solution & remediation of incidents to start troubleshooting and collaboration as fast as possible.

User Research
In order to define the target user and understand their needs so that the product is developed to create real customer value, qualitative user research was conducted involving both internal team members like sales engineers and external clients.
User Persona
 
  • Nate NOC, the NOC Operator – Those on the front line in IT Operations environments. They respond to issues and work to quickly remediate which may involve engaging others.
​
  • Tim Tools, the Tools Administrator (Target User) – Those that deploy monitoring solutions, have access to subnets, can provision virtual machines, configure thresholds, and perform any other foundational tasks that ensure the success of the other personas. 
​
  • Sam SME, the IT Infrastructure Expert  / DevOps – They want visibility into their environment health, understand dependencies. They have a deep understanding of their environments and may assist or lead in resolving complex issues.
​
  • Melissa Manager, the Managers / Exec – They want to gain visibility about what is happening and understand trends and insights about their operations environment.
Problems
From the user perspective, platform complexity in key areas critical to onboarding is tedious and difficult to set up. As a result, the core hybrid-cloud value proposition is not intuitively presented to the user due to the tedious onboarding process. â€‹
Group 938.jpg
From the company perspective, OpsRamp often masks platform complexity by relying on in-house gurus to setup these core areas, which requires a lot of repetitive manual labor inside the company.
Goals
From the user perspective, provide users a frictionless basic onboarding experience that aims to cut onboarding time from days to minutes. â€‹
​
From the business perspective, build an automated basic onboarding process that increases onboarding efficiency and more importantly introduces the key value proposition to customers as early as possible. â€‹
User Journey Map
user journey.jpg
Before this user journey was created, I went through the old design step by step, talk to the internal colleagues to collect background info (legacy issue/technical challenge/poor ux design) and verify my assumptions.
Screen Shot 2020-03-20 at 4.08.55 PM.png
Example: Onboard on-prem resources - one of the 7 steps in the old design
With all the valuable info at hand, I created a user journey map to summaries the key steps, actions, pain points, and potential solutions accordingly. â€‹I shared this journey map to all the stakeholders in order to collect feedback and general agreement before I go any further in design.
High Level Flow Proposal
high-level flow.jpg
I explored 2 directions in order to solve the problem, and used this to initiate an internal discussion on the pros and cons of these 2 options. After weighing multiple factors involved, Option 2 was selected to be the high-level direction to explore further.
Wireframes
option1.jpg
Option 1: Sequential flow mixed up Integrations(API based + V Center typed of Integrations) and Agent&Gateway type of resources
​
Pros: All types of resources get good exposures on the first screen
Cons: Can not multi-tasking in the sequential flow which may greatly increase onboarding time
option2.jpg
Option 2: Three Parallel tabs separating API based, V Center typed, Agent&Gateway resources 
​
Pros: 1) Enabling multi-tasking, shortening onboarding time 2) resources under each tab are mutually exclusive
Cons: There are very few numbers of V Center typed resources available, so it may not worth owning a separate tab only for this kind of resource, also making the flow and visual a little bit busier than fewer tabs.
option3.jpg
Option 3: Two Parallel tabs separating Integrations (API based + V Center typed) and Agent&Gateway resources 
​
Pros: 1) Enabling multi-tasking, shortening onboarding time 2) Less visual friction
Cons: Very few resources under the Integration tab has a slightly different flow than other resources under the same tab
After weighing the pros and cons, Option 3 was chosen to proceed because this option successfully balanced out the goal of shortening onboarding time and creating a frictionless experience in flow and visual design.
wireframe5:2.jpg
Onboarding flow
reuse_for_current_screen.jpg
Reusing the new layout and components for discovering more resources after onboarding flow ( 1st row: current page, 2nd row: new layout )
prototype.png
Wireframe Prototype
UI Design and Details
Due to confidentiality reasons, more details available upon request.
bottom of page