Overview

As acquisitions occur between companies, the products that accompany them also evolve. In this case, a new workflow derived from an acquired product was raised as a great fit into the existing user flow for network operators. As a result, I was brought on to design and deliver this end-to-end experience of onboarding, to managing, and finally, to querying recording devices.

Restricted Information

Due to the nature of the redesign, I am unable to publicly share the entire design process of the project. If you would like to learn more about this project and the design process, please reach out to me.

Release Date

This project was released for as a beta for Arista users as of mid-2024.


Role - Lead UX Designer

As the sole UX designer, I was in responsible for the creative direction, from user research and concept development to prototyping and implementation. I also worked closely with cross-functional teams, including product managers, developers, and stakeholders, to create a collaborative and inclusive design process.

Tools Used
Figma
and Adobe Illustrator were primarily used throughout the design process.


Modified Final Designs

Workflows and mockups below have been slightly modified to show ONLY relavent mockups created by myself, and have remove any sensitive information and interactions pertaining to the other parts of the product.

Query Workflow

Below are snippets of the Querying workflow, allowing users to identify details of traffic within a specific time range, and within their specifications.

Empty State

Query Modal

Query Added

Items populating both Active Query and Query History tables

 

Dashboards

Dashboards created to monitor the health and status of the Recorder Node Device.

 

Capture Session

Below are snippets of the Packet Capture Sessions, highlighting the status of each device being recorded and other essential details.


Validation

As previously noted, direct customer access to user testing and feedback was a difficult avenue. As a result, the main guidance for validation of both direction and design comes internally, from the Sales Engineers, as well as other internal stakeholders.

Confirmation with Sales Engineers
Throughout the design process, outreach to the Sales Engineers for feedback was essential in better understanding and validating design assumptions that were made by the team. As a result, a lot of our guidance depended on first-hand feedback and direction from those directly involved with our end users. Despite not being able to directly user test with users, constant feedback and input from the Sales Engineering team proved to be a suitable replacement.

Confirmation with Project Managers and Developers
Due to the nature of the domain and the extensive knowledge that is required to properly understand user workflows, requirements, etc. I highly depended on the team to properly guide me through the more intricate workflows and thought processes. As a result, their knowledge regarding user requirements, workflows, were only second to the Sales Engineers due to the years of experience both from Arista and the networking domain as a whole. Alongside this, validation regarding feasibility and scope definition was assisted from the team as well.

Confirmation with Designers
Being the only UX Designer on the Product, reaching out to the designers from other product teams was imperative in assisting in exploring other avenues of visual design. The designers provided valuable critique in both visual design as well as high level workflow avenues that may already exist in Arista as a whole, leading to a more cohesive product suite under the Arista umbrella.

 

More information regarding design process and success metrics can be shared in interviews.

Other projects