Designing Optserv: what an HR dashboard looks like when you actually talk to users
Jeriel Isaiah Layantara
CEO & Founder of Round Bytes
Early Optserv looked like every other HR dashboard: a big sidebar, a kitchen-sink homepage, charts nobody asked for. It was competent and forgettable.
Then we did something we should have done earlier: we sat next to ops leads while they worked.
Two patterns emerged within a week:
Pattern 1: the 80% job is task-shaped, not analytical.
Most people opening Optserv aren't there to
analyze
. They're there to
do a specific thing
: move a candidate to interview, approve a leave request, generate an offer letter, kick off offboarding. The dashboard should reward this, not distract from it.
Pattern 2: the moments of truth are the transitions.
Hiring → onboarding. Active employee → leave. Active employee → offboarded. Each of those is where things break, where access stays open or paperwork lags. The UI needed to make those transitions impossible to half-finish.
So we redesigned. The homepage became a to-do list, not a dashboard. Onboarding got a pre-flight checklist instead of twenty menu items. Offboarding became a single flow that closes the employee record and fires Account Vault revocations in the same action, you can't accidentally do half of it.
User sessions dropped (good, people got to "done" faster). Task completion rates went up. Support tickets about "did the access actually get revoked?" went away because the answer is now "yes, it's logged."
Most product teams say they talk to users. Fewer actually sit in silence and watch them work. The second kind builds better software.
