2025

CloudX

Standardized CloudX's system messages and interaction patterns, cutting decision time to under a minute and unifying 160+ alerts across the platform.

CloudX platform interface

Product

SSP/DSP platform

Domain

AdTech

Client

CloudX

Role

Product Design Lead

Activities

information architecture decision tree UX writing system

Metrics

consistency: ~95% dev decision time: < 1 m

Challenge

CloudX had major inconsistencies in microcopy and system feedback. Developers didn't know when to use toasts, dialogs, banners, or inline errors, so each feature shipped with a different pattern and wording. This caused repeated rework, user confusion, and an overall lack of trust in the interface.

Outcome

I audited the entire platform by mapping every location and action across publisher, advertiser, and superadmin roles. I built a custom decision tree for choosing the correct interaction pattern and coordinated with a junior designer to produce ~160 standardized messages. The final framework was delivered to engineering as a single source of truth for consistent system feedback.

Impact

The new messaging system eliminated pattern ambiguity, reduced developer rework, and aligned UI behaviors across all CloudX modules. Choosing the correct system feedback pattern went from 8–10 minutes of discussion in daily meetings to under 1 minute using the decision tree — an ~85–90% reduction in decision time.

Decision tree

This diagram defines when CloudX should use a toast, dialog, banner, inline error, or empty state based on context, severity, dismissibility, and scope of impact. It standardizes system feedback across all roles and screens, ensuring consistent, predictable interactions and eliminating ad-hoc developer decisions.

System Messages Matrix

This spreadsheet documents all error, alert, and notification scenarios for the Publisher side of CloudX. It maps every page, action, and field to the correct interaction pattern and final microcopy.