Rapid7 SOAR Product Redesign
Project Overview: Rapid7 is a leading cybersecurity firm based in Boston, MA. We were tasked with working on one of Rapid7’s SOAR (security orchestration automation and response) workflow builders called InsightConnect. By working with Rapid7 designers and engineers, we iterated on existing features & built out new features for InsightConnect. Because of the high value of InsightConnect, our team did not have direct access to the product.
Logistics: 3 week timeframe | Group project - team of 4 | Consultancy
Components: UX/UI Design, Research, User Interviews, Competitive/Comparative Analysis, Contextual Inquiries, User Testing

Research
We began the research process by speaking to UX designers, developers, & project managers from the InsightConnect team. Because we did not have direct access to the product and none of us had any background knowledge of cybersecurity, we spoke multiple times with each interviewee so that we could gain a foundational knowledge of the product’s uses, users, & KPIs.
Once we had a better understanding of the workflow builder, we conducted several contextual inquiries with engineers & developers from other teams within Rapid7 to identify pain-points and areas that could be improved upon.
Synthesis
Within one week of conducting contextual inquiries and user interviews, we identified 17 different features we could either iterate on or create for the workflow builder. In the below epic, these features are categorized under one of two user stories:
Creating a better user experience for seasoned users
Crafting a more user friendly experience for new users

Design
Due to the large quantity of features we decided to work on, we divided the work up amongst our group. Two features that I worked on that I will discuss in this case study are: ‘improving zoom functionality’ with UX tactics & ‘restructuring of the import process’ using IA tools.
Improving Zoom Functionality
One of the first functionality issues we noticed through our contextual inquiries and user interviews was the zoom function. In the current workflow builder, the only way to zoom in & out is with the trackpad on a laptop or the wheel on a mouse. For users using trackpads, the zoom in/out is smooth, but for those using a wheel, the zoom change is drastic and unhelpful.
To remedy this, we added a permanent sliding zoom bar in the bottom corner so that all users can zoom in or out in a controlled and gradual manner. When zoomed out, some information such as the action of the step is not visible. When the user zooms in, this information becomes legible.
The second aspect of the zoom addition is the magnifying glass tool. This feature allows users with especially large workflows to quickly run through their flow without constantly zooming in and out.
As the user runs their cursor over the zoomed out workflow, a zoomed in version appears next to it. When the cursor is directly over a single step, it becomes highlighted and shows the name of the step.
**See “further iterations” for final version of magnify**
Restructuring Import Process
Throughout our contextual inquiries, it became evident that there are inefficiencies present in the import process of the workflow builder that breed confusion. To remedy this, I split the process into two separate paths for the two different types of users, experienced and new. This way, the experienced users don’t have to go through the instruction-heavy, but timely configuration and the new users get a comprehensive, less daunting import experience.

The beginning of the separate user flows for the two different types of users begins with the import dropdown button

The user can either configure all steps in the template before importing or they can skip the mass-configuration to get straight to the workflow builder and manually input the info they want in each step.
Depending on how many steps are in the template, configuring each one separately can be a time-consuming process for an experienced user and an almost impossible task for a new user. Although the configure process (shown below) may seem like a delay to the ‘meat’ of the product, it walks the user through a complete configuration so that their workflow is fully functional once they arrive at the builder. The goal is that new users feel as calm and capable as possible and that they arrive at their workflow templates in the builder with zero errors. To achieve this, we remove as many confusing options as possible.
Alternatively, if the user is experienced and wants to just have a quick look over the template within the builder, they can fully skip the configuration process and go straight to the builder.
The important distinction that this change makes to the current flow is that it gives both users a route that is designed specifically for them. In the current site, when the user clicks ‘import,’ they are automatically brought to the first configuration page which deals with plugins. However, once they get to the second page, they are presented with the option to skip the rest of the process. To a new user, they may not know how vital the rest of the configuration is, and choose to skip with the hopes that they will save time. However, it is critical that new users fully complete these three pages so they are met with a functional workflow when they get to the builder, so the option to skip halfway is removed. On the other hand, experienced users that would intend to click the skip button are also facing inefficiencies because they still have to go through the plugins page to reach the skip button. That is ultimately why I moved the skip button the dropdown of the import button.
Further Iterations
Towards the end of our project, we had several design reviews with the Rapid7 UX team as well as a meeting with one of Rapid7’s engineers to discuss the validity of our proposed features.
Current Layout
Proposed Layout
We learned from our meeting with their engineer that the process of creating a magnify function would be extremely time-consuming and costly. In response to this, I found a way to to make the feature more valuable, and thus, worth building out.
Through early user interviews, we realized that it is cumbersome to open and close the side modal (left image) to get detailed information about each step. Knowing this, I decided to gather the most important information from the side modal and add it to the magnify function to completely eliminate the use of the side modal in these cases, ultimately reducing the number of clicks and saving the users time.
To determine exactly what information from the side modal to add to the hover feature, I conducted two additional user interviews and found that, in the late stages of their work, they usually want to check only the input and output of each step.
As a result, the final iteration of the magnifying glass feature both allows the user to quickly scan through their workflow and see the most important information of each step with zero clicks.
Conclusion
By the end of the three-week period we:
Held a 3 design reviews with the UX team, a senior engineer, and project managers
Handed off a 50+ page document detailing all 17 features, their iterations, and the research behind them
Formally presented our work to the stakeholders