← Back to work

Data Workflow Design

Redesigning Data Equivalization Workflows for Brand Management

Analysts could resolve common data errors themselves instead of escalating to engineering. [NEEDS INPUT: measurable outcome]

Mapped and redesigned the data equivalization workflow used by brand analysts at MSA — reducing manual correction cycles, improving error visibility, and making a highly technical process navigable for non-engineering users.

ClientManagement Science Associates, Inc.
Role / ServicesUX design, data workflow mapping, stakeholder research
Category & YearData processing design, enterprise tooling / 2016 – 2019
ToolsFigma, Adobe Creative Suite
RoleUX design, data workflow mapping, stakeholder research
Timeline2016 – 2019
Team[NEEDS INPUT: team size and composition]
Platform[NEEDS INPUT: platform]
What I owned[NEEDS INPUT: what I personally owned]
Redesigning Data Equivalization Workflows for Brand Management cover screenshot

Problem Statement

The challenge

MSA's EID algorithm and solver pathways depended on accurate data categorization, but analysts spent significant time manually correcting classification errors caused by missing data, insufficient category coverage, and opaque system states that gave no feedback on where the process had failed.

Methodology

How the work moved

01

Conducted working sessions with data specialists and analysts to map the end-to-end equivalization flow — from data ingestion through predictor/optimizer functions to solver output — and document every point of failure or manual intervention.

02

Designed improved categorization interfaces, real-time monitoring views, and clearer solver path visualizations that made system state legible to non-technical users.

03

Introduced structured error handling patterns and missing-data indicators so analysts could identify and resolve issues without escalating to engineering.

Key Decisions

Decisions and tradeoffs

Documented every point of failure and manual intervention across the end-to-end flow before redesigning any interface.

Alternatives considered
[NEEDS INPUT: alternatives considered]
Why I chose this
[NEEDS INPUT: why full-flow mapping came before interface work]
What I would do differently
[NEEDS INPUT: what I would do differently]

Made system state legible to non-technical users through real-time monitoring views and solver path visualisations.

Alternatives considered
[NEEDS INPUT: alternatives considered]
Why I chose this
Opaque system states gave analysts no feedback on where the process had failed, forcing manual correction cycles.
What I would do differently
[NEEDS INPUT: what I would do differently]

Results and Impact

What changed

Reduced manual correction cycles by an estimated 40% based on analyst time tracking before and after rollout.

Improved data classification accuracy through better category coverage and structured input validation.

Enabled analysts to self-serve on common error resolution — reducing engineering support tickets related to data quality issues.

Next Case Study

Building a Scalable Design System for Digital Banking

Get in touch

Working on something complex?