Network Monitor

Designing a product to help users monitor their complex digital environments.

By visiting users, we were able to learn about their day to day lives and how they currently manage their networks.

01

Defining Pain Points

Network Monitor is a SMB solution for IT Pros, created to help them manage their internal networks through early alerting when their core infrastructure goes down. Setting out to determine what the largest issues with the current application were I studied our usage data, performed contextual inquiries, user interviews, and affinity mapping and was able to determine that the main issues on the app were was that the navigation didn't match the users' mental models, they had too little control over their alerts, and that we had a huge dropoff occuring during initial set up.

02

Wireframing Solutions

My initial discussions with users led me and the product manager to the discovery that we needed to rework the feature that allowed for users to configure their email alert thresholds, create a maintenance scheduler that allowed for users to be able to turn off alerts on a schedule, and create basic on boarding for the first time users. With this information, I began designing these features by creating low-fidelity prototypes that I would test with users often, to get as much feedback as possible.

03

Feedback and Iterations

As I talked with users about early stage prototypes I was able to determine where they were getting confused, and what changes should be made. A major change was making the decision to show live data on each alert setting, so that the user had an idea of what range they needed to move the slider into. This change was decided because users often did not have an idea of how far they would need to go to really affect the alerting, and would often flip between pages in the app to see what the current data was. After making this change, users immediately stopped going to other pages in the app to help set their alert thresholds and were able to make more informed decisions on where these thresholds should be.

User testing helped guide our iterations until the users found the new features simple and easy to use.

04

Final Implementations

The final implementations of this project included a new alert settings page, onboarding experience, and scheduling tool. Users were excited about being able to better manage when they receive alerts, as well as being able to schedule off times for the alerts. With the implementation of the onboarding, we saw a 10% increase in users installing the app and logging in past the first session.

BackNext