Shared ownership of attention
The org began treating the customer's attention as a single precious, finite, shared budget. Uncoordinated outreach became a shared ethos, rather than an unowned problem.
The Notification Overload Problem
How I made a diffuse, ownerless trust problem visible, then built the governance that kept it solved after I left.
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.
Credit · PushMarketing · EmailPromotions · BadgeRisk · PushP2P · BadgeSavings · EmailFraud · PushOffers · BadgeCredit · EmailHoney · PushLifecycle · EmailProduct · In-app
Attention budgetCognitive overload
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. Past a point, more messages don't add up, they cancel out. 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
Audit, analyze, framework, automation.
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, it stopped reading as a design preference and became a shared risk leadership had to answer for.
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
The engine applied their 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
03The outcome
The output was shared ownership of the customer's attention.
The framework rules and delivery engine were a critical deliverable, but the shared understanding that uncoordinated outreach harms the customer, and that someone has to answer for the total rather than just their own channel was gold. It held because it lived in process rather than in any one person: after I moved on, the framework, the intake, and the council kept running.
A guiding framework
An evaluative framework (priority, channel, timing) that every message runs through, plus an engine that paces delivery.
~30% more trust
Qualitative research on how PayPal communicated improved nearly 30%, translating into fewer unsubscribes and opt-outs.
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.
What it proved
Credibly surfacing a diffuse, ownerless problem, enough for an organization to restructure and engineer around it, is doable, if not easy. Unorthodox methods work well when deployed with precision.