← All case studies

Case study · Kakitangan.com

Leave that explains itself

Leave touches everyone in a company. Staff check balances and apply, managers and HR approve, and everyone wants to know who's away. I designed the new leave module as a clickable prototype, tested it against real-world setups, then built its pages on the new platform.

My role
Product Designer + PM
Year
2026
Users
Employees, managers, HR admins
Tools
HTML prototypes, React
My leave: nine leave balances shown as days left out of the total, upcoming public holidays, and an Apply leave button

Local build with a test company. Names and numbers are test data.

The module

Five jobs, one place

  1. My leave

    Balances, my applications and the next public holidays.

  2. Applications

    Everything waiting on you, in one queue.

  3. Calendar

    Who's away, before you plan your own leave.

  4. Replacement credit

    Days earned for working on a rest day or public holiday.

  5. Reports

    Everyone's balances, by department or location.

Prototype first

Testing the hard cases before building

Leave rules change from company to company. The clickable prototype had a test panel, so reviewers could switch the setup and see the design hold up, not just the happy path.

  • 2

    approval flows: manager or any HR admin, or manager then HR

  • 3

    calendar rules: see everyone, your department, or only your own

  • 300

    staff and 100 requests waiting, to test a large company

  • 3

    failure states: slow pages, failed loads and failed saves, each with a clear message

Design decisions

What each page does

One queue for approvals

"Waiting on you" shows only what needs a decision, with the count up front. Search, filters and bulk select help HR clear a long list. Each row shows who, what and how long, with Decline and Approve side by side.

Applications page: a Waiting on you tab with 37 requests, search and filters, and each request with Decline and Approve buttons
Leave calendar month view: each day shaded by how many people are away, with the selected day's list of people and their leave types on the right

See who's away at a glance

In the month view, busier days are darker, so clashes stand out. Pick a day to see exactly who's away and why, filtered by department or location. Holidays show on the calendar too.

Made for phones too

Every page works at phone width. On small screens the calendar keeps its month grid, and tapping a day opens the full list of who's away.

On a phone, tapping 4 November opens a full-screen list of the 10 people away and their leave types

Reports grouped the way HR thinks

Everyone's balances, grouped by department or location, with each group opening on demand so a large company stays readable. Switch to a person or a leave type, then export to Excel.

Leave reports: balances grouped by department, each group showing how many people it has, with the Accounting group open

Reviewing my own work

Before handing over, I review the build like a new user would, on desktop and phone. The latest pass turned up these fixes for the next round.

  • Explain the numbers on the month calendar, so it's clear they count people away.
  • Keep leave-type colours apart from status colours, so a green or orange tag never reads as "approved" or "warning".
  • Make the reports table work on phones, not just scroll sideways.
  • Use the same date format everywhere, including date pickers.

Next case study

Claims, from receipt to payment