Most first-time users trying to deposit into a betting account on Kuda hit a dead end. The system asks for a User ID, but in many cases, what actually works is the phone number linked to the betting account.

This misalignment caused unnecessary friction and frustration. So instead of designing around a step-by-step flow, I tackled the root cause.

✅ I redesigned the input field to accept both username and phone number.

✅ I introduced smart validation that suggests an alternative if one method fails.

✅ I improved error messaging to guide users instead of leaving them stuck.

This is what problem-driven design approach looks like, understanding friction points, eliminating ambiguity, and making every interaction seamless.