CASE STUDY 05 · PAYPAL · 2019-2024
The Notification
Overload Problem
No one owned the user's total communication experience. Every team managed its own channel. The cumulative damage was invisible — until I made it undeniable.
0
TEAMS WATCHING AGGREGATE LOAD
1
EXTERNAL AUDIT COMMISSIONED
∞
GOVERNANCE STRUCTURE THAT OUTLASTED ME
THE PROBLEM
A platform-wide trust issue that nobody owned.
PayPal's consumer product had dozens of teams managing communication with users — push notifications, in-app messages, email, badge dots, lifecycle marketing, credit alerts, fraud notifications, promotional offers. Each team was responsible for its own channel. Each team optimized for its own metrics. No single team was watching what users experienced in aggregate.
The result was predictable in retrospect but invisible in the moment: cumulative communication overload. Users in early-life — the most critical period for trust formation — were receiving overlapping outreach from multiple disconnected sources, at volumes no individual team felt responsible for.
On the approach to organizational change: You can't argue against a problem no one can see. My job was to make it visible — and to make it legible in terms that demanded a structural response.
This wasn't a design problem in the traditional sense. There was no surface to redesign, no flow to optimize. The problem was organizational — fragmented accountability producing coherent harm to a shared asset: user trust.
THE APPROACH
Evidence first. Governance second.
I worked outside my formal lane. I assembled a modest budget from existing resources — no dedicated headcount, no approved initiative — and engaged a third-party research firm to conduct a secret shopper audit of PayPal's full blended communication footprint. They experienced the product as a new user would: every notification, every email, every in-app prompt, across the onboarding and early-life window.
Opinion vs. evidence
Design intuitions about notification overload existed for years. The audit converted intuition into organizational fact — data no individual stakeholder could dismiss as subjective preference.
Structure over persuasion
The goal was never to win an argument about notification frequency. It was to build a process where the argument didn't need to be won repeatedly. Governance outlasts persuasion.
Outside the lane
No one asked me to do this. I identified a problem that no individual team could see or solve, assembled resources without a formal mandate, and built the structural fix. That's the job at this level.
OUTCOMES
What the audit and governance produced
1
Centralized intake process for all notification requests across the platform — created from nothing
X-func
Cross-functional review committee that evaluated requests against total user communication load
Durable
Governance structure that outlasted my tenure — the process became the mechanism, not the person
WHAT MADE IT LAST
The external audit report made the problem undeniable to leadership across functions. When the evidence is external and documented, it stops being a design opinion and becomes a shared organizational risk. That shift — from opinion to evidence — is what created the conditions for structural change.