Case study Β· Kakitangan.com
Redesigning the home dashboard for employees, managers and HR
The dashboard is the first page everyone sees after logging in. It has to answer very different questions for each role without becoming cluttered. I led the redesign from research to release planning, and tested it with users twice before the first release.
- My role
- Product Designer + PM
- Year
- 2026
- Users
- Employees, managers, HR admins
- Tools
- HTML prototypes, React
Clickable prototype with sample data. Names and companies are fictional.
Before and after
Drag the handle to compare the old dashboard with the redesign.
73%
rated the redesign 4 or 5 out of 5 against the old dashboard
2
rounds of user testing, with 33 and 25 responses
3
releases planned, with the most-requested fixes first
The challenge
Kakitangan.com is HR and payroll software for Malaysian businesses. One dashboard serves everyone: employees checking leave and payslips, managers checking who's in today, and HR admins clearing approvals and running payroll.
Early feedback was clear: it felt like too much information, admins wanted their approvals first, and payroll items were hard to find.
What I did
- Planned and ran two rounds of user surveys with task-based tests
- Designed the layout, cards and states for each role, on desktop and phone
- Built clickable prototypes that switch between people, roles and company setups
- Wrote the product spec, acceptance criteria and edge cases
- Split the work into three releases and planned the first one
- Built the first release's changes, then handed off to engineering
Research
Testing with users, twice
Round 1 Β· 33 responses
The redesign compared with the old dashboard.
Round 2 Β· 25 responses
An improved version compared with the first, plus real tasks for each role.
How people rated it (share scoring 4 or 5 out of 5)
| Question | Round 1 | Round 2 |
|---|---|---|
| Easy to use the first time | 79% | 64% |
| Information is easy to understand | 88% | 80% |
| Confident without training | 76% | 60% |
| Helps me get things done faster | 79% | 80% |
Reading the dip: Round 2 asked people to complete real tasks, which usually lowers "easy" and "confident" scores. "Gets things done faster" held steady, and 64% preferred the improved version over the first (20%).
Could people find it? (Round 2, "Yes, easily")
-
Employee: check medical claim balance88%
-
HR: see leave requests waiting88%
-
Manager: who hasn't clocked in80%
-
Attendance admin: clocked in but not out72%
-
Claims admin: compare the last two months60%
-
Employee: hide a card60%
-
Employee: find the latest payslip48%
-
Payroll admin: staff missing bank details44%
The weakest results were both about finding payroll things. That changed the plan: payslip access went into the first release, and missing bank details became a to-do item for admins in a later one.
Design decisions
What people said, and what changed
-
"Admin approvals should come first" Β· 5 people
Team approvals is now the first card for admins.
-
"The attendance numbers are wrong when people work more than one shift"
My team now follows each person's shift: who's working now, on a break, on half-day leave, or still on last night's shift.
-
Only 48% could find their payslip
Payroll admins get a direct "My payslip" link, and staff without a payslip see a clear message instead of an empty button.
-
"Show my leave as 14/20" Β· "Pending claims show no amount"
Leave tiles read "14/20 days available", and claims show amounts in the company's own currency.
-
"I can't find Switch Companies"
The company name sits in the greeting, with a clear way to switch or add a company.
Release plan
Ship the biggest fixes first
Instead of waiting for everything, I split the redesign into three releases so users get the most-requested fixes early.
-
V1
In reviewFix what users asked for most
Approvals first, shift-aware team view, payslip access, clearer leave and claim tiles.
-
V2
PlannedCompany announcements
A place for HR to share news, asked for in both rounds.
-
V3
PlannedAdmin to-dos and reporting
Things that need fixing (like missing bank details) and trends for admins.
How I worked
Prototypes people could actually use
Instead of static screens, I built clickable prototypes. Reviewers could switch between five people and roles, different company setups and tricky states, and try the real flow before any engineering time was spent.
I then built the first release's changes, backed by 174 automated tests and handoff notes covering the risks, data changes and how to test.
-
5
people and roles to switch between
-
3
screen sizes: desktop, laptop, phone
-
28
settings for company setups and states like new joiners, loading and errors
-
174
automated tests passing
What I learned
- Ratings alone looked good. Real tasks exposed the payroll gaps that ratings missed.
- Not every request should be built. Some were kept as they are on purpose, with the reason written down.
- Clickable prototypes made reviews faster, because people reacted to a real flow instead of imagining one.
What's next
- Release V1, then re-run the same tasks to measure the change.
- Test with phone-only users and real attendance data, which neither round covered.
- Move the payslip higher up the page for everyone.
Next case study
Making payroll clearer, one step at a time