Streamlining Solu's employee and staffing management portal
How I created a standard component library for solu
How we helped managers & HR manage employee assignments, leaves, and build a resource repository
Current State
mySolu is Solu's portal currently only serving as an employee database and leave management.
It was minimal tabular data with default themes and did not provide enough actions for employees and managers to accomplish their tasks.
My goal was to
- Firstly build a foundational standardized component library that will ensure consistency and brand identity across Solu's internal tools
- Secondly understand the workflow of managers and HRs to optimize and streamline their process in mySolu. Focus was mainly on employee assignment, and Leave management workflows.
Landing page + Contacts page
Leave Request + Approval page
Leave requests management - Manager view
Research
Understanding the user and current system
To understand the tasks carried out by different users groups I conducted following activities to familiarize myself with the tool
1. User Interviews
to understand top tasks and demo workflows
Project Managers, HR and recruiters and some employees took us through their current usage of mySolu
2. Screen Audit
to gather components used and needed , determine scalability and identify areas needing consistency, improvement, etc.
3. Task Flow Maps
to inform wireframes of what information and actions are needed at different stages
Task Demo Interview with project managers
1. User Interviews
Project Managers, HR and recruiters and some employees took us through their current usage of mySolu
Key Insights
Managers:
- They do not find out who’s leave is upcoming until the day. Would prefer knowing before hand to plan accordingly
- Filters are hard to operate
- Takes time to find who is on leave today
- Leave approval process is unclear
- Not all employees use this portal
- Takes a lot of time to find an employee and their details. Would like to improve employee profile to understand their project assignments
2. Screen Audit
Results:
- Identified key components required for mvp eg. Datatable, navigation style, etc.
- Identified data redundancies
- Consistency issues with styling and data representation
- Difficult to use or non functioning components like in table filters were identified
- Familiarize with admin and role functionalities
Neha Patil
UX Researcher & Designer