Case study · Kakitangan.com
Making payroll clearer, one step at a time
Payroll is where a small mistake costs the most: wrong salaries, late statutory payments, upset staff. I led the revamp of Kakitangan.com's payroll, from research with the support team to a new step-by-step flow, a spec for engineering, and a design system applied to the rebuilt pages.
- My role
- Product Designer + PM
- Timeline
- 2025 – 2026
- Users
- HR and payroll admins, employees
- Tools
- Figma, HTML prototypes
Local build with sample data. Names, companies and amounts are fictional.
Before and after
Drag the handle to compare the old payroll calculator with the new employee pay screen.
The goal
Same payroll engine, much easier to use
The calculations already worked. The problem was everything around them, so the revamp focused on three things.
01
Clarity
Users can see what to do next at a glance.
02
A simpler flow
Payroll runs as clear steps, not a maze of pages.
03
Less mental load
Fewer things on screen, and no silent surprises.
Research
Listening to the people who take the support calls
The support and customer success team hear every payroll problem first. We ran two discovery sessions with them, compared what they said with the list of high-priority tickets, and mapped every payroll page into one sitemap.
What kept coming up
- Users didn't know when or why to recalculate payroll.
- Payroll's own menus were hidden inside the page, so even support struggled to guide people to EA forms.
- Unticking "Include in payroll" quietly changed a salary, and users missed it.
- Employer contributions couldn't be edited, and long employee lists couldn't be filtered.
- The text was too small to read comfortably, including for users with reading difficulties.
Design decisions
What changed
"I can't find the payroll menus"
A clear step-by-step flow
Payroll's sections are now tabs: Payroll, Yearly report, Contributions and Statutory forms. Each month runs the same way: adjust each person's pay, calculate and generate the report, then confirm. "View report" only appears once a month is complete.
"Why do I need to recalculate?"
The report tells you when it's out of date
When leave is approved or a salary changes after the report was made, a banner explains what happened and offers one Recalculate button. Each affected person is tagged, so admins never confirm an old amount by mistake.
"Everything for one person is spread out"
One place for each employee's pay
- Earnings, deductions and contributions sit side by side.
- Employer contributions can be edited. Edited amounts are marked "Customised", with one click back to the calculated amount.
- Excluding someone from payroll keeps their salary as it is.
-
Risky actions ask first
Confirming an amount shows the net pay and payment date. Switching pay cycles warns before anything changes.
-
Easier to read, on any screen
Larger text and accessible colours from the design system. Wide tables stack into cards on phones.
-
Find people fast
Filters by employee, department and status, for companies with long staff lists.
Working with engineering
Designing with the build in mind
Six months of engineering time meant the scope had to stay tight. Before handoff I checked the code to see which changes were only front-end work, and flagged everything that needed backend work.
✅ Already supported, mostly front-end work
- Confirming and unconfirming amounts
- Excluding employees and pay cycles
- Reports, statutory forms and accounting exports
🛠️ Needs backend work
- Choosing single or multiple cycles per month
- A payroll-level Completed / Pending status
- Splitting large reports into pages, so they stop timing out
Where the spec was silent, I made a call and flagged it
- Page actions moved to the header, because the chat bubble covered the main button in a bottom bar.
- Status labels say what to do: "Needs calculating" instead of "Pending".
- Completing payroll with unconfirmed amounts asks you to confirm them first.
What I learned
- Support teams are the fastest research shortcut: they already know where users get stuck.
- In payroll, "no surprises" matters more than "fewer clicks". Every silent change was a support ticket waiting to happen.
- Checking feasibility before handoff kept a six-month build focused, and made the backend work visible early.
What's next
- Finish the build and test it with real payroll admins.
- Later releases: payslip customisation and deductions with an end date, both highly requested.
- Measure support tickets about payroll before and after.
Next case study
Leave that explains itself