Across 40 million monthly transactions, declines were the number one NPS detractor. The systems were messy, the rules were strict, and the humans on the other side were often stressed. The fix had to land everywhere the decline did: product, comms, call center, and the boardroom.
Declines are small individually and enormous in aggregate. Every month tens of millions of transactions didn't complete, and every unexplained decline was a moment where a member didn't trust the product, or in some cases, didn't trust the bank. Customer care was absorbing the overflow; the product, the app, and the call scripts were telling members three different stories.
Worse, the internal explanation of "why" was distributed across fraud systems, payment networks, issuer rules, and member account state. No one team had the whole picture. That gap between systems and explanation was where member trust was leaking.
This was not a screen-level problem, so I didn't start with screens. I mapped the full service: the moment of the decline, the push notification, the app message, the call to care, the written follow-up. At each touchpoint I asked what the member knew, what the business knew, and what the system could actually say.
On the research side I synthesized quantitative decline reason codes with qualitative interviews. The quant told us which reasons were dominant; the qual told us how members were interpreting each one, and it rarely matched.
A decline is not a transaction outcome. It's a service moment with a specific person on the other side of it.
The journey that came out of synthesis was briefed to the bank president, not just to the product team. The cross-functional scale of the fix required organizational sign-off to move, and putting the real member journey in front of leadership was the unlock.
The redesign rebuilt the explanation layer around what the member actually needs in the moment: what happened, what it means for them, what they can do next, and where to go if the answer isn't enough.
A declines problem is a cross-functional problem. Every artifact was designed to travel: product, fraud, care, comms, and the executive team could each pick one up and use it.
From the moment of the decline through the resolution, across every channel the member hears from. Annotated with owners, systems, and gaps.
Back-office codes collapsed into a plain-language set members and care agents could both use. The shared vocabulary the program now runs on.
Dominant reason codes mapped to how members were interpreting each one. Where the two didn't match is where the redesign focused.
The executive-level walk-through of the real member journey. Unlocked the cross-functional investment the fix required to move.
Push, in-app, written follow-up, and care scripts sequenced to tell one story at the member's emotional pace, not the system's.
Member-resolvable decline paths (temporary holds, limit changes) with a warm handoff to care where a human conversation was actually needed.
The declines experience was reframed from a support liability into a service pattern the bank could improve deliberately. The service map became shared language across product, fraud, care, and comms. The president's brief secured the cross-functional investment required to carry the work beyond a single ship.
Best for project inquiries, scoping conversations, and workshop requests. I answer within two business days.
A low-pressure intro call. Bring the system you're stuck on; I'll bring questions.