RapidSS
Human Resources Management
RapidSS is a human resources management software that allows companies to modify the product according to their needs.
Client
Team
Duration
Rapidsol Consulting
Sole UI/UX Designer
Ongoing
Mobile
UX / UI Designer
Figma
Type
Role
Tools
Process
1. Research
The initial focus of the project was on the Leave Management module. Through user research and competitor analysis, I identified a key insight: Comprehensive calendar views for both admins and employees is a crucial feature for effectively managing leave requests.
2. User Personas & Scenarios
There are mainly two user groups: employees and managers. Several user scenarios were also used to better understand their workflows. This process helped guide design decisions by highlighting the specific needs and potential situations, ensuring that problems were addressed through design.
Problem
-
The product was developed within an ERP (Enterprise Resource Planning) system, which limited the user experience (UX) due to a confusing user interface (UI) and poor usability.
-
As new features were added, the design became increasingly fragmented, further complicating the overall UX.
-
Future modifications and additional features were planned, but the client lacked a clear design vision for the app's long-term development. The goal was to ensure that all actions could be managed in one place without clutter, even as new modules were added over time.
.jpg)
User Scenario I
Group Expense Scenraio Integrated with Travel Management
.jpg)
Task Flow
Group Expense Filing Integrated with Travel Management
Site Map
Process
3. Wireframes & Sketches
With insights from market research and the client's expectations, my design process begins with pen and paper. I start by mind mapping and sketching wireframes, simultaneously developing task flows. Since the design process is non-linear, it follows a dynamic path, allowing for back-and-forth ideation. This approach not only ensures thorough exploration of various solutions but also saves valuable time for both myself and the client by refining ideas early in the process.
Task Flows
Leave Request and Approvals
.jpg)
Process
4. Low-Fidelity Screens
Before finalizing the product, low-fidelity prototyping allowed us to focus on the functionality. I prepared Figma prototypes to begin user testing early in the process.
Lo-Fi Leave Request Flow
5. Prototyping & Final Product
High-fidelity prototypes were essential for the company to present and pitch the project to potential clients without the need for coding. These prototypes provided a clear representation of the app, allowing us to gather feedback. Based on this feedback, we made iterative improvements to ensure the app was both user-friendly and visually engaging.
.jpg)
Outcome & Feedback
At the end of the process, I handed off a UI library for both the web and mobile applications. The web application is now well-organized and easy for regular users to navigate. With over 1,000 users, the feedback has been positive. The company’s clients appreciated the simple and colorful UI, which made the app more user-friendly. The design system also allows for easy integration of future modules as needed.