Nick Montesano
← All work

OneTrust · UX Designer

Speak Up

An admin-first design system couldn’t serve a scared employee on a phone. I extended it with consumer-grade, responsive components.

Three Speak Up mobile screens: location step, people-involved step with card buttons, and the emergency notice

Impact

One library, built for reporters and ready to scale across OneTrust.

4 PMs

aligned on one cohesive intake flow through bi-weekly workshops I led

Cross-functional

1 library

extended inside OneTrust’s design system instead of running Material alongside it

Decision

Responsive

sizing and breakpoints for modals, which had none before

New definitions

  • Ethics and compliance leaders on the advisory board called customizable intake critical for reporter trust
  • Advocated launching the responsive foundation first to gather data while AI intake was explored
  • Led Speak Up while also driving Disclosure Approval, one of four OneTrust products I designed for

Overview

Problem

Reporters needed a safe, fast flow. The system was built for admins.

What I did

Led design for the intake flow and the new component library.

Result

Responsive library documented with components and variables.

Team · Time

UX director, 2 designers, researcher, 4 PMs, eng and architecture leads. 4 months.

The problem

Reporters aren’t admins.

Speak Up lets employees of OneTrust’s customers report ethics concerns, from small misunderstandings to fraud or abuse. Reporters are often stressed, rushed and away from a desk. OneTrust’s components were made for dense desktop admin work.

Research process: planning, internal interviews, customer interviews, synthesis, validation and testing with customers
Research shaped three requirements: welcoming, intuitive and responsive.
Welcoming

Reassure people the space is safe from retaliation.

Intuitive

People may have minutes. Each step is simple and hard to get lost in.

Responsive

Many report from a phone or tablet, away from the office.

01 · Extend, don’t adopt

Grow our own system, not a second one.

Chose

A new library inside OneTrust’s design system.

Rejected

Material Design, which the team first considered.

Why

Two component sets mean long-term design debt. Material also limited the branding customers needed.

Cost

We gave up Material’s ready-made docs and speed.

Material Design exploration of two intake steps on mobile
The Material exploration: fast to build, but hard to make feel like each customer’s own brand.

02 · Consumer feel, same foundation

Bigger, softer and brandable.

I extended core components instead of replacing them: larger buttons and fields, more padding, and corner radii customers can set. Mouse states and keyboard or voice focus states were designed together.

Buttons: OneTrust design system states beside the new Speak Up enhancements, for mouse and keyboard users
Buttons: the existing system (left) and the Speak Up enhancements (right), with every state.
Text, search and error inputs: existing system beside the larger, rounded Speak Up versions
Inputs: the same labels, search and error states, sized for touch.

03 · A new component

Answers that explain themselves.

Reporters often need context to choose an answer. I designed a card button with a clear selected state and optional help text that each customer can write.

New card button component: default, hover, press, loading, disabled and focus states, plus help-text variants
The card button, with mouse and keyboard states and help-text variants.
Card button variants, including a navigation card with an arrow and help text
Variants, including a navigation card for the landing page.

04 · Responsive by definition

Modals that work on a phone.

Modals had no responsive rules. I defined sizing, columns and width at each breakpoint, from small phones to large monitors, so engineers had one answer for every screen.

Mobile emergency-notice modal beside a breakpoint table of min and max widths, columns and modal width
The “not an emergency service” modal, and the breakpoint table behind it.

The mobile flow

From a chat concept to guided steps.

Early wireframes tried a chat-style flow. The final intake uses one question per step, a progress bar, and the new components.

Four phones: chat-style concept, welcome wireframe, and two final intake steps
Left to right: chat concept, welcome wireframe, final location and people-involved steps.