Most people did not try again after a failed payment.
Out of every 100 failed payments, 30 were tried again and 10 went through. And 2.5 per cent of users with a failed payment blocked their Paytm account.
Senior AVP, product design. Design innovation in fintech.
I am at Wells Fargo, designing B2B fintech products and working on AI product innovation. I use AI tools through the whole of a project, from research to handoff. Behind that are nine years of payment flows and gamified journeys that moved the numbers.
Across payments, games and banking, every project starts with the job a person is trying to get done and ends with a number that shows whether the design helped.
Three projects, each written up in full.

Most people did not try again after a failed payment.
Out of every 100 failed payments, 30 were tried again and 10 went through. And 2.5 per cent of users with a failed payment blocked their Paytm account.
People were skipping the reason for the failure.
A three-week heatmap study across more than 20,000 failed payments showed taps going to the logo, the amount and the floating bar, and very few on the reason.
The reason became the title of a bottom sheet, with the next step under it.
In December 2023, 49 of every 100 failed payments were tried again and 22 went through, up from 30 and 10.





Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.
Antoine de Saint-Exupéry
I use AI at every stage of a project to move faster. Each stage still ends with me checking the work against real users, the design system and an agreed number.
Before I draw a screen, I write down the job people hire the product for and check it against interviews, tickets and analytics.
Sorting hundreds of interview notes and tickets into themes.
Meeting users myself and reading the quotes behind each theme.
For each key screen I explore about ten directions, narrow them to three to work up in detail, and take the strongest one forward.
Drafting flows and layouts, so ten directions take a day.
Cutting what is generic or does not serve the job.
I test working prototypes with real data and every state, including the moment an AI answer is wrong, before engineering builds.
Turning a design into a working prototype in a few hours.
Running the sessions and deciding what the findings mean.
With product and engineering, I set the goal, the signal that shows progress and the metric to read. Then the flow ships as a test.
Pulling results and session recordings into one summary.
Reading the result, even when it says the idea failed.
I have given 65 mentoring sessions on ADPList. These are my mentees' own words, unedited. The sessions I run are on the mentoring page.
His in-depth feedback on my designs and his willingness to answer my questions helped me to see things in new and different ways.
Review 1 of 10.