Product compliance

The Problem

Sales teams relied on manually curated responses, disconnected spreadsheets, and informal knowledge-sharing to answer product compliance questions. The result was inconsistent information, delayed sales, and

more than $200M in lost or delayed sales in 2022 alone.

My Role

I owned the UX and UI direction for the compliance experience, including competitive research, information architecture, interaction design, Figma explorations, and collaboration with product and engineering.

I collaborated with the team through 1–2 weekly meetings, including regular check-ins with developers to share design progress, discuss implementation, and incorporate feedback.

From research to design

I started by benchmarking 3 competitors: Microsoft, VMware, and IBM to understand how existing products handled compliance information and document downloads.

The analysis revealed four key opportunities:

01  Simplify content
Make compliance information clearer and easier to scan.

02  Reduce cognitive load
Organize related information and limit competing links.

03  Make downloads discoverable
Use clear PDF/download cues and place the action where users expect it.

04  Support flexible downloads
Allow users to download a single page or multiple pages when needed.

Exploring the solution

I sketched multiple approaches in Figma to explore how compliance information could be organized, prioritized, and accessed with minimal cognitive load.

The first explorations focused on different ways of organizing the compliance information. The main challenge was figuring out how to help users find a specific compliance document quickly, and whether the content needed to be grouped in a different way. I explored different layouts and experimented with the filter on the left to see how it could make finding the right document faster and more intuitive.

I make sure to stay closely aligned with stakeholders’ needs by asking plenty of questions and regularly gathering feedback from my design team. We have a weekly meeting every Tuesday where everyone can share their work and get feedback from the team.

The Final Design

Based on the research and early explorations, I designed a centralized compliance experience that makes information easier to find, understand, and download.

01 Clear information hierarchy
I organized compliance information into clear sections so users could quickly scan and find the information relevant to them.

02 Make documents easy to access
I placed download actions alongside relevant compliance information, making documents easier to discover and access.

03 Reduce cognitive load
I simplified the navigation and reduced competing links to help users focus on the information they need.

The main page includes a filter feature and an icon on each compliance card that provides additional information, such as the product, region, and industry.

Results

The project received positive feedback from multiple stakeholders across the company and supported Red Hat’s efforts to improve access to compliance information for customers and internal teams.

“I have done product marketing at multiple security/IAM companies over the last 15 years and at EVERY single one of them, what is on this page has been a top request from the field. This is the first company I have worked at that has actually produced a comprehensive page like this. While it may appear straightforward, creating a detailed list like this quite difficult to compile and requires serious security/compliance expertise to analyze/justify inclusion of the multiple products, versions and capabilities. Serious kudos to whichever team/individuals created this as it’s pure gold!” - Jmanuel

Following the initial release, I continued to iterate on the experience by incorporating feedback and exploring additional features, such as gated downloads for specific compliance documents. I also contributed to the CRA compliance initiative, which required creating a dedicated documentation page based on the same design principles.