Workforce
Management System.
Scheduling, shifts, approvals, and time-off for a distributed workforce. End-to-end product design with a clean engineering handover.
- Sector
- HR · Operations
- Users
- Managers · staff
- Scope
- End-to-end product design
- Surface
- Web · mobile
• 01 · The brief
The brief.
The brief: a workforce-management product that staff actually open on their own — not just when prompted. The category has been overdesigned for managers and underdesigned for the people whose lives it actually shapes.
• 02 · Context
Context.
The workforce in question is distributed across multiple sites, on rotating shifts, with frequent swap requests and time-off needs. The legacy tool surfaced this as a manager-first dashboard with a thin staff view bolted on. Adoption stalled at the staff layer; everything cascaded back to the manager.
• 03 · The approach
The approach.
We inverted the priority. The staff member's experience is now the primary one, and the manager's view is a structured aggregation of it. Notifications use a single rule: if it can wait, it doesn't ping. Time-off, shift swaps, and approvals are designed to settle in a single conversation rather than a loop of comments.
• 04 · What we shipped
What we shipped.
- Staff schedule view — week, month, my next shift, swap requests.
- Manager console — team rota, approvals, exception flags.
- Admin — roles, locations, policies, audit trail.
- Mobile app surfaces for both roles.
• 05 · Outcome
What changed.
Approval cycle times shortened. Shift-swap volume rose — a sign of trust, not chaos — and exception escalations to managers dropped. The product became something staff actually opened on their own.
