Data Map

Introduction

This post is about the work I did with Symmetry Systems. Symmetry Systems is a rising player in the data and cybersecurity world.

What is it?

The Data Map is a visualization tool that allows users to intuitively visualise the access paths that exist between resources in their cloud environments. Instead of rummaging through charts and tables, the map offers users a fresh, visual-first approach to explore their environments.

Value Proposition

Outside reducing the learning curve for users to start taking action on their data, the Map also serves a few important functions

Problems

Being a sophisticated tool to engineer, the map could not be built with the same tools used for the rest of the product. In its current form, the graph:

• ...is mainly an exploratory tool
• ...has no defined usage patterns
• ...visual language doesn’t match rest of the product
• ...is difficult to use for users with lower technical proficiency

The Opportunity

The current state of the map leaves more to be desired. Its full potential remains untapped, and the disconnect from the rest of the product poses a major usability issue.

How can we seamlessly integrate the Data Map into the rest of the product, focusing on ease of use and allowing users to discover powerful features?

Process

Instead of showing a typical process that covers user flows, information architectures, and other run-of-the-mill elements, my aim is to provide glimpse into the high-level thinking and diverse thought processes that shaped the project. Given the Data Map’s unique position as a tool within an already established product, we had to try our best to leverage already existing usage patterns and provide a natural segue into the Map.

Next, we had to make sure that the Map enabled users to perform the same workflows that they usually carry out on data-heavy dashboards. When users switch from these dashboards to the Map, they shouldn’t feel a disconnect, and be able to pick up where they left off.

It’s especially important to consider the types of users that would use the Data Map, since the team would need to make sure it meets a wide range of use cases.

Understanding Users

User Flows

Unifying with the product

Visual Design

Outcomes

Once the all-new Data Map was shipped, we were met with a ton of great feedback and appreciation. Our decision to put the Map in focus and declutter the UI was recieved well by our customers. Most importantly, the Map had changed from being an intimidating tool to being something that excited people. The idea of having a tool to visually explore a cloud environment was appealing to our users. This resulted in some great conversations, and a lot of feature requests that continue to keep the team busy.

Learnings

Revamping and shipping this feature felt like operating a start-up within a start-up. Beyond learning new technologies, I’d have to say that my biggest takeaway was adopting a “ship-fast” mentality. This is crucial for small product teams, where constant feedback and multiple cycles of iterations help refine the product into something well-rounded. The team had many great ideas along the way, but I learnt to prioritize ones that are crucial to ensure a strong baseline user experience. Since we would be completely revamping this feature, we had to balance innovation with familiarity. Maintaining a connection between users’ expectations and mental models ensured that the revamp would be well recieved, and not cause a disruption.

Future Scope