After Rapyd acquired Neat.hk, our product design team transitioned to join Rapyd's product design group. I, along with another Senior Designer, took responsibility for Rapyd's Back Office (RBO), which supports various internal teams across different departments and markets.
.jpeg)
Due to legacy issues, many features in the RBO were developed reactively, based on immediate requests, without thorough planning for usability and user experience. Our current focus is on rethinking the user flows and modularising all functions to create a consistent user experience across different pages and features.
Redesigning the UI components from scratch based on the branding guidelines and maintaining them to ensure UX/UI consistency across the platform.
Starting by understanding the daily workflows of various internal users, I have been working closely with the Product Owner to conduct ongoing interviews with department leads who heavily rely on the RBO product for their daily tasks.
Research Goals
Given that the RBO has a lot of terminology and specific use cases for each team, it’s challenging to grasp by simply exploring the staging environment. After interviewing users, I can translate this knowledge into a concise summary, outlining the feature’s background, purpose, and current user pain points.
I were responsible for maintaining the RBO's design components and syncing with the team whenever there were new designs or use cases related to UI components.
