All data shown is for illustration purposes only.
Summary
A compliance team of 17 audits classifications across roughly 600,000 tables every quarter, scanning manually over several days. I designed a flow that narrows that down to only the columns worth reviewing. After the first audit using it, unassigned columns dropped by about 30% and columns with two classifications by about 40%.
What I owned
Reframed the brief from “export a file” to “narrow to the affected columns”.
Designed three directions.
Split the work into phases so the narrowing could ship before the deadline.
The stakes

Who this was for
The Tech and Data Compliance (TDC) team with 17 analysts. Each analyst owns a set of domains and is accountable for the classification accuracy of every table in them.
The workflow looked something like this for each analyst.

The request from the users

But it did not address the audit itself…
So I reframed the goal.
Three directions
2. Classification and mismatch filters.
3. Classification wizard
The constraint and the decision
The team preferred option 3, but engineering could not build it inside the deadline, which was driven by a compliance commitment.

What shipped
This is how the Phase 1 design looked.
This is the final design, where the user can either upload or edit all the data.

Results
~30%
Unassigned columns classified
~40%
Columns with two classifications resolved
The in-UI edit flow from Phase 2 hasn’t shipped yet.
What I took from it


