Back to home

Real-time monitoring of ML models

None of a financial company's ML models in production were monitored, and problems only surfaced after they hit the business. I facilitated the Design Sprint that defined PSI, KS and VDI dashboards with real-time alerts.

ToolsFigmaMiroGCPNotion
Coverage
0%
of models monitored
Standard
0
critical metrics standardized
Alerts
Live
alerts on behavior drift
Detection
−0%
time to detect drift
Overview

Project context

The project

A Design Sprint run to develop a monitoring system for machine learning models and variable books in the GCP environment.

The challenge

Without a monitoring system, it was hard to proactively spot model performance degradation, which undermined the quality of business decisions.

My role

UX Designer on the Machine Learning team. I facilitated the Design Sprint, from stakeholder mapping to dashboard prototypes validated with data scientists and managers.

Primary persona L Lucas Mendes 33 · Data Scientist / MLOps Engineer
Main pain
“Only finds model problems after they impact business results, because there's no way to automatically monitor performance degradation or data drift.”
Goal
“A centralized system that monitors every model automatically, flagging drift in real time for preventive action before the business is affected.”
Research and discovery

What the data and users revealed

01CSD matrix

The CSD matrix showed that no model in production had automated monitoring: problems were only discovered after they hit business results.

02Stakeholders

Stakeholder mapping revealed distinct needs: scientists needed granular metrics (PSI, KS, VDI) and managers needed a consolidated executive view.

03Retraining

Teams struggled to define the right moment to retrain, with no comparative history or automatic drift alerts.

04Costs

Without per-model cost control in GCP, it was impossible to optimize AI infrastructure spend and justify budgets.

Design process

From problem to solution

01Understand

CSD matrix and stakeholder mapping

We built a CSD matrix to map certainties, suppositions and doubts about the requirements, and mapped stakeholders from the strategic to the operational level.

CSD matrixStakeholder mappingDesk researchRequirements gathering
02Create

Proposed solutions and monitoring framework

We proposed solutions such as categorizing variables, monitoring PSI, KS and VDI monthly and running historical comparisons.

Solution ideationAlert frameworkGCP cost tagsRisk analysis
03Decide

Scope definition and system components

The scope was set as monitoring every model, with specific books when needed. We detailed the components: dates, values, dimensions and filters.

Scope definitionSolution votingComponent detailingFeature prioritization
04Prototype and validate

Lo-fi prototypes, dashboards and stakeholder validation

I created low-fidelity interfaces with sample dashboards, variable visualization, model degradation and an alert system, validated with stakeholders.

Lo-fi prototypingDegradation dashboardsAlert systemStakeholder testing
Screenshots

A visual walkthrough of the solution

Model monitoring dashboard prototypes
Dashboard prototypes
Sprint board with the team's goals and expectations for the project
Goals and expectations
CSD matrix with certainties, suppositions and doubts about the requirements
CSD matrix
Risk exercise: imagine the project failed, what could have happened
Risks
Board of features and capabilities the product should offer
Features
Solution sketches with a wireframe of a data drift and performance dashboard
Solution sketches
Design decisions

Why each choice matters

1

Centralized dashboards with critical metrics

PSI, KS and VDI were centralized in dashboards with color-coded indicators, to quickly assess each model's health.

2

GCP architecture with Vertex AI and BigQuery

The architecture combines Vertex AI and other GCP components, with metrics stored in BigQuery for historical analysis and cost control.

3

Automated alerts and preventive action

Alerts via message, email and real-time dashboards ensure problems are caught before they affect the business.

Results and impact

Numbers that prove the value of design

before: zero visibility
0%
of models monitored
PSI · KS · VDI
0
critical metrics standardized
before: manual detection
Live
alerts on behavior drift
automated vs. manual analysis
−0%
time to detect drift
Next step

Facing a similar challenge in your data product?

Let's talk