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

System feedback in CloudX had no single owner or logic, so every team made its own toasts, dialogs and wording. Across roles and screens the product spoke in many different ways — which caused constant rework, confused users, and slowly reduced trust in the interface.

Outcome

A standard system-feedback framework — a decision tree for choosing the right pattern and a documented set of ~160 messages — handed to engineering as one source of truth.

Impact

Choosing the right feedback pattern stopped being a repeated discussion and became the default, which removed rework, made behavior consistent across modules, and let users rely on what the interface says.

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.

See in GoogleSheets