Financing check: A missing API check was costing a retailer over $800K a year.
- Role
- Senior Product Designer
- Outcome
- UX research changed the brief, and the fix to a problem saves the customer $800K a year with absolutely no UX or UI changes.
The problem
The company I worked for made RQ, retail software that was 25 years old. Over those years, RQ had been connected to many carriers and partners, one integration at a time.
The brief came from a retailer with over 600 stores. Sales reps were completing phone sales before the customer's financing was approved. It was rare, but when that financing was later declined, the customer had already left with the phone. The retailer put the cost at over $800K a year, and asked for a new user interface with an extra verification step.
The research
The software's data couldn't show what was going wrong with the financing. The system has so many settings, workflow options and customizations that the same sale can be made in many different ways. Retailers usually kept the company from speaking directly to their sales reps. I kept pushing, and I convinced them that observational research, watching reps make real sales, would show what the data couldn't. From those sessions, I mapped the user journey step by step, across the customer, the sales rep, the carrier's system and the retail software.
Decisions and trade offs
Because of my research, I found the specific problem. It was a finance status check in our integration with the carrier system. I recommended adding an API check instead of the new user interface the retailer asked for. Reps in over 600 stores would have had to change their workflows for an edge case.
The work
The financing check
The software should have checked the financing status every time it imported an activation or reopened an activation in progress. It did, except in one edge case. The fix was to add the missing check in that edge case. It was a small piece of work, with no change to the sales flow the reps already knew and no added complexity in an already complex integration.
Outcome
The client estimated the financing check fix saves them $800K a year. The UX research took a couple of weeks, but the result was a simple validation check. No new user interface, no new help file updates, and no impacts to a user experience sales reps ran on autopilot.
$800K
a year, what the client estimated the financing check fix saves
What I would do differently
I would have advocated earlier in the research for direct access to the end user. The only reason we found the workaround the sales reps were using was because of that research. No analytics we had would have ever surfaced the issue.