During my time as an intern at Highradius, I have been majorly involved in establishing an updated design language for Highradius products. As we progressed with the new style guides and components, our team was parellely incorporating the new standardized design language across all products and Highradius PayNRemit was one of them.

Though, apart from updating the visuals, there were chunks of UX problems to solve as well that could enhance the user experience.

Prior to discussing the app and its problems, it was crucial to understand the business and how the mobile application generates revenue. Therefore, I obtained knowledge about the business and how the app facilitates its services to design effective solutions for any issues related to the application by setting up meetings with the management.

As mentioned above, there are two methods for completing this transaction: payment settlement by the supplier or by the buyer.

PM team came with following statement —

Stating the above, they walked me through the entire application explaining the entire payment process along which they pointed out problems faced by sales agents. With this, they gave me the task to run in parellel — visually uplift the application. Then I started using the application myself where I could clearly identify some of the root causes that were leading to unintended user problems.

The HighRadius Supplier App facilitates the remittance collection process, which involves several steps. In this process, the supplier's accounts receivable representative visits the customer (here, Walmart) to collect the remittance and settle any open invoices on behalf of the customer.

After subsequent discussions with the product management (who had customer feedbacks), engineering and other internal stakeholders I made a consolidated list of problems, solving of which could effectively improve the user experience to significant amount.

Interface prior to the design overhaul:

Keeping focus on how to fasten the remittance collection process but also knowing that the current payment ecosystem can not be modified, I decided to optimize the flow by reconnecting the navigation routes by placing/adjusting information & actions accordingly to facilitate same. This helped me to optimize the overall user flow.

First design language I worked on, where I created new components, updated a few and documented all of them in the link below.

Greetings! Start a new payment or continue where you left. You can come here whenever you want to explore other options and your payment progress will be saved automatically.

The number of invoices to remit can be a large. Instead of doing everything on a single screen, the user has all the invoices properly segmented. Here, reducing cognitive load is more important than reducing user efforts in terms of taps or clicks.

After selecting customers and their respective invoices to remit, come to step three where you — enter remittance amount, swipe, repeat until all the invoices selected for remittance are covered.

Remittance Summary after payment collection helps you sync the payment information to the cloud. Payment History has an audit of the remittances made. User Preferences allows some level of personification to the user.

In my first major undertaking as a design intern, I learnt more about in designing solutions within not only time but techical constraints, collaborating with developers, communicating and signing-off to the product management. Good design is iterative has been my mantra, but a successful sign-off requires a well-justified design. While the new design captured more users and we could see increasing engagement from current ones, I would still love the opportunity to start fresh by consulting field sales representatives and merchant owners on a ground-level, addressing potential unknown problems. This approach would fully leverage the possibilities of a B2B merchant/supplier remittance collection process.