The payout queue at King
Approved withdrawals took three repeated actions each. I cut that to one and left the checks as they were.
- Context
- Gaming platform, payout operations
- Role
- Product Owner
- Date
- August 2016
The short version
- Result
- Roughly 600 to 1,000 clicks a day removed across 300 to 500 withdrawals. The checks and the final payment control stayed.
- What I did
- Redesigned the payout flow so approved withdrawals land in a batch list, one action each instead of three.
- The call
- I only removed the repeated clicks after approval and left every check before it as it was.
What changed
There were 300 to 500 withdrawals a day, each checked in its own tab, and that checking was necessary. Paying one out then took three repeated actions, submit, approve the confirmation and send.
Now one action sends an approved withdrawal to a batch list. The checks and the final payment control didn't change.
Problem
Every approved withdrawal on the real money skill games site took three repeated actions. Someone had to submit it, approve the confirmation and send it. The withdrawal had already passed its checks by then, so none of the three involved any judgement, and it happened 300 to 500 times a day.
Approach
I redesigned the flow so approved withdrawals land in a batch list instead. One action per withdrawal puts it on the list, and the reviewed list goes out in one send at the end of the run. The checking before the decision stayed exactly as it was, and so did the final payment control before any money left.
Outcome
Three repeated actions became one, which at 300 to 500 withdrawals a day removed somewhere between 600 and 1,000 clicks. The saving landed on whoever was clearing payouts that day, usually one or two people.