Skip to main content
Angelica Anderson
  • Work
  • About
  • Resume (opens in a new tab)
  • Contact

On this page

  • Overview
  • Problem
  • What I did
  • Key decisions
  • Results
  • What's next
← All work

Unearth Campaigns · Executive dashboard · Privacy compliance

California DROP Audience Impact Report

I led an executive dashboard that turned 1.7 million state-mandated deletion requests into a clear answer: which audiences we lost, and what to do about it.

All data shown is placeholder
Problem1.7M deletion requests, no clear picture

A new state privacy law began removing people from our audiences, and leadership couldn't see the impact.

What I didLed it from requirements to rollout

Learned what leadership needed, defined the metrics and layout with the developer, set impact criteria with the PM and pitched an AI summary.

ResultAn actionable report for leadership

A high-level overview leadership can scan in two minutes, with a daily AI summary and recommended next steps.

Role
Project Lead + Technical Coordinator
Timeline
Aug - Oct 2026
Team
Me, Developer, Product Manager
Tools
Claude, Slack, Plane

Methods

  • Stakeholder interviews
  • Requirements mapping
  • Iterative prototyping
  • Data visualization

The problem

Every deletion shrank an audience we sell, and the data only existed as millions of raw rows

California's Delete Request and Opt-out Platform (DROP) lets residents send one deletion request to every registered data broker at once. As a registered broker, our company has to pull new requests at least every 45 days, delete every match and report the status of each request back to the state. Missing the deadline costs $200 per request, per day. Every deletion also shrinks the audiences our product sells to clients.

Leadership kept asking the same questions, and nobody could answer them without pulling the data by hand.

request_id · list_type · match_key · audiences · status
DR- · phone · · 3 · matched
DR- · email · · 0 · no match
DR- · phone · · 7 · matched
DR- · ndz · · 1 · matched
DR- · email · · 2 · matched
DR- · phone · · 0 · no match
… 1.7 million more
Leadership askedWhich audiences had the most people opted out?
Leadership askedWhich audiences need to be repaired or rebuilt?
Leadership askedAre we on track to meet the 45-day deletion deadline?

What I did

Turned three leadership questions into a report they can act on in two minutes

01

Turned leadership's questions into requirements

I mapped each question to a part of the report: who was removed and how, which audiences lost the most and the raw data for anyone who needed to dig in. A contract developer built it; I owned what it showed and how it read.

Opt-out and DROP reporting · Requests received Jun 16 - Oct 8Placeholder data
What the DROP deliveries did to our audiences
AllDROP cycle 1Last deliveryLast 7 daysLast 30 daysCustom
All requestsDROPDirect requests
1.7MRequests received
XX,XXXMatched people removed
XX%Audiences impacted
X.X%Memberships removed
Removal funnel
Received100%
MatchedXX%
In an audienceXX%
RemovedXX%
Most impacted audiences
AudienceRemoved% lost
Audience AX,XXXXX%
Audience BXXXXX%
Audience CX,XXXX%
Audience DXXX%
02

Built a beta with the developer, then shaped it around what leadership needed

I iterated on a beta with the developer first. Before the first cycle closed, I walked leadership through a demo, gathered their questions and met with them to understand their concerns about DROP and what they wanted to see. Their answers became priorities for the whole report, not just fixes. The biggest lesson: percentages matter more than raw counts.

Round 1Easy, secure access

One-click sign-in with work accounts and sortable tables, so anyone on the team can open it and find what they need.

Round 2Readable anywhere

Company branding and a mobile pass, so the report holds up on a phone.

Round 3Answers for any time window

Faster loading, date filters and exports, so leadership can check one delivery or the whole cycle.

Round 4Percentages first

Leadership cared most about how much of each audience was lost, so tables sort by % lost and the funnel shows rates.

Round 5A quick-glance summary with next steps

An AI summary at the top calls out what matters most in the data and recommends what to do next, refreshed daily.

03

Pitched an AI summary so leadership didn't have to read tables

Leadership needed the story, not the spreadsheet. I proposed a summary written by Claude from the report's own figures, then edited how it reads: full width, no repeated descriptions and our team's words ("audiences," not "lists").

AIWritten by Claude from the figures in the tables below. Check a figure against its table before acting on it.

  • Smaller audiences took the sharpest hits: Audience A lost XX% of its members.
  • X audiences lost more than XX% and may need a refresh before their next campaign.
  • XX,XXX requests are still waiting to be reported back to the state.

The disclosure line was a deliberate trust decision: leadership sees that the summary is AI-written and where to verify it.

04

Set impact criteria with the product manager

Before the report could recommend next steps, we needed shared rules. I brought three questions to the product manager: What % of an audience lost counts as low, moderate or significant? Should that change with audience size? And what should each level trigger?

Impact criteria · draftThresholds in progress
Impact level% of audience lostNext step
LowUnder X%Monitor next cycle
ModerateX% to Y%Refresh the audience
SignificantOver Y%Rebuild, and flag affected campaigns
05

Redesigned the summary around decisions

Once leadership was using it, I mocked up a new top section that answers "how bad is it and are we on time" before anything else.

What stands out
1.7MRequests
XX,XXXPeople removed
XXXAudiences touched
XXX,XXXMatched requests
Biggest losses (by people removed)
AudienceRemovedImpact
Audience CX,XXXSignificant
Audience FX,XXXModerate
Audience EXXXMinimal
XX% of audiences impacted · X.X% of memberships removed1
XX%Audiences impacted
X.X%Memberships removed
1.7MRequests this cycle
XX,XXXPast due to report back2
Most affected audiences (by % lost)
3
Audience% lostRemoved
Audience AXX%X,XXX
Audience BXX%XXX
Audience CX%X,XXX
4
Version 1My redesign

Drag to compare, or choose a change below to see it.

Key decisions

Rank by impact, show deadline risk first, agree on criteria before labels

Rank audiences by % lost

WhyLosing 5,000 people hurts a 10,000-person audience far more than a 2 million-person one.
TradeoffLarge audiences with big raw losses rank lower, so I kept the raw count in its own column.

Show compliance status first

WhyMissing the 45-day deadline costs $200 per request, per day, so "are we on time?" comes first.
TradeoffAudience details moved further down the page.

Agree on criteria before adding labels

WhyA label like "significant" only helps if everyone agrees what it means and what happens next, so I took it to the PM first.
TradeoffThe summary shows numbers without labels until the criteria are set.

Results

Leadership went from raw rows to a daily, plain-language read

1.7M

deletion requests from the first state cycle, visible in one report

5

release rounds in 4 weeks, each driven by leadership feedback

Daily

AI summary refresh, so leadership never reads a stale number

What's next

Bring the report to where leadership already works

Leadership lives in Slack. Slack's new Surfaces let Slackbot build a live dashboard from connected data and pin it to a channel, where people can filter it, comment and ask follow-up questions. I plan to explore delivering the report there instead of asking leadership to open another tool.

# atlas-developmentConcept · placeholder data
SB
Slackbot9:00 AM

Here's this week's DROP impact. 2 audiences crossed the refresh threshold.

📌 DROP Audience Impact · SurfaceUpdated today
XX%Audiences impacted
X.X%Memberships removed
On trackState deadline
L
Leadership9:12 AM

Which client campaigns use those 2 audiences?

NextFinalize the impact criteria

Lock the thresholds with the PM, then bring the labels and recommended next steps back into the summary.

NextAlerts before deadlines

Post to Slack when unreported requests get close to the state deadline, or when an audience crosses a threshold.

ExploreCycle-over-cycle trends

DROP keeps running, so show whether each audience is stabilizing or still shrinking.

ExploreClient impact view

Once leadership decides the policy, show which client campaigns are affected so account teams can reach out first.

Next case studyHopeHub

From spreadsheets to grant-ready data for a shelter and service provider, with reporting built into the work staff already do.

Read next →

Angelica Anderson

Product design, web development, and technical coordination

  • Resume (opens in a new tab)
  • Email