N
Back to selected work

2025 / Human Resource System

Srawung Nova HRIS

An HRIS interface concept for making employee data, workflows, and operational states easier to scan.

Srawung Nova HRIS interface preview
Role
Product Design / Design System
Platform
Responsive web app / Operational dashboard
Timeline
2025
Stack
Figma / Design System / Responsive Design

Srawung Nova HRIS is framed as an operational product where clarity, repeated use, and trust matter more than visual spectacle.

Internal tools often become dense without giving teams enough visual structure to act quickly. The challenge was to reduce cognitive load while preserving the information teams need.

01 / Contribution

What I shaped.

  • Structured employee, attendance, and workflow information into clearer product zones.
  • Explored component states for dense operational screens.
  • Defined a design system direction that supports repeated admin tasks.

02 / Product decisions

Key decisions.

Decision 01

Make operational states visible before users open details.

Status, priority, and action cues are surfaced in the list and summary areas so teams can understand what needs attention faster.

Make operational states visible before users open details. visual placeholder

Decision 02

Reduce form friction with predictable grouping.

Fields are grouped by task intent instead of database structure, making longer HR workflows easier to complete.

Reduce form friction with predictable grouping. visual placeholder

03 / Interface

Screens and states.

Srawung Nova HRIS gallery placeholder 1
Operational dashboard placeholder.
Srawung Nova HRIS gallery placeholder 1
Srawung Nova HRIS gallery placeholder 2
Component states and form flow placeholder.

04 / System

Designed in systems.

The system direction centers on dense but readable tables, form groups, badges, and action states.

  • Data tables
  • Status badges
  • Form groups
  • Action bars
Srawung Nova HRIS design system placeholder

05 / Frontend

Built for responsive use.

This case study currently emphasizes design structure, with frontend notes prepared for future implementation.

  • Responsive operational layouts for desktop-first workflows.
  • Clear component state mapping for loading, empty, warning, and success states.
  • Reusable visual language for repeated HR modules.
const statusTone = status === "approved" ? "success" : "attention";

06 / Outcome

What this enables.

  • A more scannable HRIS direction.
  • A reusable interface system for operational modules.
  • A product foundation that can grow into real workflow documentation.
Operational products need restraint. The design work is strongest when it helps people act repeatedly without asking them to relearn the interface.

Next project

SIMANHAJ

View next