Bringing PayPal’s notification overload under control

How I made an ownerless trust problem visible, then set up the council and rules that were still running when I left.

All screens recreated. The flows, decisions, and results are my team’s.

Role
Senior Design Manager, Home & Dashboard
Surface
The blended, cross-team communication stream
Span
2021 – 2024
Output
Audit, rules, and a routing engine
01The challenge

A shared surface with no owner.

Every team at PayPal was spending the same scarce resource, the customer's attention budget, and no one was watching the balance for overdraft.

An illustration of one customer’s June. Each PayPal notification lands on the lock screen and in its day, under everything that arrives after it, and the package alerts she wanted sink with the rest. We couldn’t put a clean number on it, but a customer’s anecdote and a deep dive into real customer streams told the same story. Everyone was over budget.

A research participant told us the new package-tracking alerts weren't helping. She was surprised she'd even opted in, and they vanished into a cloud of competing notifications. That's the failure in one anecdote. More messages don't bring home the point: they just create attention fatigue. The cognitive load tips into noise, and the people most exposed were customers in early life, when trust is still forming.

You can't argue against a problem nobody can see. We had to make the overdraft visible, put it in terms that demanded a structural answer, and find someone to own the balance.
02The approach

We audited first, then wrote rules, then automated them.

1The audit

Funding real research took money no one had set aside, and without evidence there was no case for change. I got scrappy, running an informal audit, then pulling together about $100k in dribs and drabs from product leads who'd come to trust me. I brought in an outside firm to run a secret-shopper audit of everything a new customer hears from us, every notification, email, and in-app prompt across onboarding and early life. Once the evidence came from outside and sat on paper, leadership treated it as a risk they had to answer for.

My call

I was told a research project wasn’t an option because there was no budget. I decided to ask a lot of people for spare change and cobble the budget together.

2The Communications Council

I convened a cross-functional council (product, marketing, legal, content strategy) to analyze the audit findings and author an evaluative framework. They categorized each communication (urgency, regulatory, priority, actionability), which channel it belongs on, and when it should arrive, plus fallbacks for when a channel was blocked, a customer who declined push still received a required regulatory notice another way.

3The framework engine

Engineering built a delivery engine that applied the council's framework to every message, holding most in a per-customer queue and releasing them as an orderly agenda, while letting a genuinely urgent message jump ahead. It stayed open to oversight, since the council could sample a single anonymized customer's stream to see how the framework landed, no PII, enough context to judge it.

Credit · PushMarketing · EmailPromotions · BadgeRisk · PushP2P · BadgeSavings · EmailFraud · PushOffers · BadgeCredit · EmailHoney · PushLifecycle · EmailProduct · In-app
Evaluative framework
prioritychanneltiming
Day 1Welcome & setuppush
Day 15Savings tipemail
Day 45Overdue noticepush
An orderly agenda · within budget
Senders no longer reach the customer directly. The framework scores each message on priority, channel, and timing, and the engine delivers them as an orderly agenda.
A table of eight message types grouped by priority. P0 compliance messages, a regulatory notice and a fraud alert, are always delivered and fall back to email. P1 product notifications such as payment due, money received and package shipped go to the channel the customer turned on. P2 marketing messages need their own marketing opt-in, and nothing is sent without it.
A representative slice of the rules, recreated. Every message got a type, and the type set its priority. Compliance was P0 and could always fall back to email, which needed no permission. Marketing needed its own opt-in.
03The outcome

The output was shared ownership of the customer's attention.

The rules and the delivery engine mattered. The bigger win was a shared understanding that uncoordinated outreach harms the customer, and that someone has to answer for the total, beyond their own channel. I built it to live in process rather than in any one person, and when I moved on, the framework, the intake, and the council were all running.

Shared ownership of attention

The org began treating the customer's attention as one shared budget. Teams started answering for the customer's total attention together.

A guiding framework

An evaluative framework (priority, channel, timing) that every message runs through, plus an engine that paces delivery.

~30% higher trust score

In our scored survey research, trust in how PayPal communicated rose nearly 30%.

04Hindsight

Keep the evidence fresh.

What I'd watch

It isn't clear the rules-based prioritization is still happening. I left a functioning committee, rules, and an engine, but the whole org has to stay vigilant. In lean times it's tempting to bend the rules to goose short-term revenue, and that quietly damages long-term trust.

The lesson

Building the governance was the right move. Pairing it with a standing external re-audit would have made it more durable; external evidence is what gave it authority in the first place.

See more case studies →