// Workforce Management System

// Duration
12 Weeks
// Role
UX / UI Designer
// Platform
Mobile
// Discipline
Research · Design · Prototype
01 — Challenge
The system worked.
The people didn't.
Problem Statement
Problem A
Fragmented navigation
Problem B
One-size-fits-nobody dashboard
Problem C
Approval bottlenecks
Problem D
No centralised HR visibility
02 — Goals
Simplify workflows
Reduce approval friction
Improve role clarity
Enable faster actions
03 — User Types
Three roles, three realities
Each user group had fundamentally different daily tasks, mental
models, and pain points. Designing one experience for all three
was the core challenge.
EM
Employee
Daily task executor
→
Mark location-based attendance
→
Apply leave & regularization
→
Submit timesheets
→
Track reimbursements & requests
→
Raise & track grievances
MG
Manager
Team decision maker
→
→
Approve leave, timesheets &
expenses
→
Monitor team performance
→
Handle team requests
efficiently
→
Review reimbursement claims
HR
HR Admin
System-level controller
→
Oversee org-wide operations
→
Manage announcements & events
→
Handle grievances & employee
support
→
Monitor approvals & compliance
→
Manage reimbursement policies
04 — Feature Architecture
Structure before screens
Attendance & Time
→ Clock In / Clock Out
→ Attendance Logs
→ Regularization
→ Timesheet
Leave Management
→ Apply Leave
→ Leave Balance
→ Leave History
→ Calendar View
Approvals
→ Leave Approvals
→ Timesheet Approvals
→ Expense Approvals
→ Bulk Actions
Expense Reimburse
→ Raise Claim
→ Category Selection
→ Claim History
→ Status Tracking
Grievances
→ Raise Grievance
→ Category & Priority
→ Status Timeline
→ Resolution History
Org & HR
→ Announcements
→ Events & Birthdays
→ Team Directory
→ Documents
05 — Key Insights
What the data said
High-frequency actions
Approval bottlenecks
Cognitive overload
Centralised HR needs
06 — Design Decisions
01
Usage analytics showed 80% of sessions started with the same 3 actions per role. Surfacing those on the home screen eliminated the need to navigate at all.


02
Card sorting with 6 users revealed clear mental groupings matching this structure. "More" acts as a progressive disclosure mechanism for
less-frequent actions.



03
Managers confirmed approval delays were the single biggest daily frustration. Bringing approvals to the surface reduced the action from 6 taps to 2.



04
Research showed users checked the app at the start of each workday as a "what do I need to do?" ritual. The home screen was redesigned to answer that question instantly.

07 — User Flows
Employee — Clock In
Manager — Approve Leave
Employee — Raise Expense Reimburse
Employee — Raise Grievance
08 — Final UI: Approvals
Approvals, finally surface-level
Managers can review, approve, or reject requests directly from
the home screen. The detailed view expands inline with full
context — no context switching required.
6 taps → 2 taps
Approval action reduced from deep navigation to home screen widget.
View by type
Leave, Timesheet, Expense — managers handle by
category for faster batching.
Full context inline
Reason, timeline, and days visible before deciding.
No blind approvals.
09 — Final UI: Reimbursements
Claims that don't get lost
Employees raise reimbursement claims in under a minute.
Category, amount, and receipt attachment in one guided flow.
Status updates are trackable from submission to settlement.
Single guided flow
Category → Amount → Receipt → Submit. No dead ends or optional confusion.
Status always visible
Pending, approved, rejected — employees never wonder where their claim stands.
Aggregate view
Total pending amount at a glance — employees track
their money, not just their requests.
10 — Final UI: Grievances
Concerns raised, not buried


Visible pipeline
4-step status track removes anxiety about where an
issue stands.
Priority levels
HR notes inline
08 — Impact
67%
fewer steps to clock in
6 steps → 2 steps
3×
role-based dashboards replacing
one generic view
Employee · Manager · HR
4/5
users completed leave flow without
assistance
usability test · 5 participants
Before
After
"
Employee · usability test
"
Manager · usability test
09 — Learnings
What this project taught me
01
Role separation is a design constraint, not a feature
02
03
04









