The payout queue at King
Approved withdrawals took three repeated actions each. I cut it to one and left the checking alone.
- Context
- Gaming platform, payout operations
- Role
- Product Owner
- Date
- August 2016
The short version
- The problem
- 300 to 500 withdrawals a day, each needing three repeated actions after the safety checks were done.
- What I did
- Redesigned the payout flow so approved withdrawals land in a batch list, one action each.
- What it was worth
- Roughly 600 to 1,000 clicks a day removed. The checking and the final payment control stayed.
- The call
- Touch nothing before the decision, remove everything after it.
What changed
Between 300 and 500 withdrawals a day, each checked in its own tab, and that was necessary work. Paying one out then took three repeated actions. Submit, approve the confirmation, send.
One action per approved withdrawal sends it to a batch list instead. The checking stayed exactly as it was, and the final payment control stayed where it was.
Problem
Every approved withdrawal on the real money skill games site took three repeated actions. Submit, approve the confirmation, send. By then the withdrawal had already passed its checks, so the three clicks were not judgement. They were repetition, 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. At 300 to 500 withdrawals a day, that is somewhere between 600 and 1,000 clicks a day that no longer happen.
For whoever was clearing payouts that day, usually one or two people, it meant far fewer clicks on approvals that had already passed every safety check. Nothing about the checks changed.