I refined an early HRMS concept and working prototype into a reusable interface system for employee records, attendance, policies and approvals.
Early conceptHRMSDesign systemPrototype
Outcome
Delivered an HRMS prototype and reusable interface system for records, attendance, policies and approvals. Shared components brought the broad concept into one visual language; it remained an early product direction.
Early product concept · interface studies
01 / Context
A broad HRMS prototype.
The concept brought attendance, employee records, activities, calendars, approvals and work policies into one system.
I started with a working prototype. Walking through its flows showed how broad the scope had become and which interface rules could be reused.
Product
Zevian HRMS concept
Role
Product designer
Scope
Prototype · UI system
Foundation
Ant Design
Method
Atomic Design
Status
Early product direction
Earlier Zevian HRMS concept
The Zevian name later moved to a focused product for investigating performance changes and supporting manager decisions. This page documents the earlier HRMS interface and system work.
02 / Interface work
Status and next actions on dense screens.
Policy setup turned long work rules into reviewable steps. Employee and calendar views kept context close to the task.
Work modality policy setup.Employee context stays close to attendance records.A shared calendar keeps activities and status visible.
03 / System
One system for light and dark.
Built on Ant Design and organised with Atomic Design, the library gave inputs, buttons, avatars and navigation one set of rules.
Semantic variables carried those rules across light and dark themes, dashboards, records and reports.
Inputs and states
Buttons and avatarsNavigation
One semantic layerRepresentative variable map
RoleLightDark
Canvas#F7F8FA#14161A
Surface#FFFFFF#202329
Text#20242C#F2F3F5
Action#151515#D8FF52
DashboardRecordsReportsSame component rules
04 / Result
Prototype and UI rules.
Working prototype
The team could walk through the concept and question its scope.
Reusable UI rules
Core controls and navigation gave dashboards, records and reports the same starting point.
Clearer product boundary
The flows exposed how broad the HRMS concept had become.