ONEVIEW — Arnab Roy

PROJECT / 01 · ENTERPRISE OPERATIONS · 2026

ONEVIEW

A modular enterprise operations platform connecting HR, finance, support and employee workflows.

UX + PRODUCT DESIGN

HR · FINANCE · SUPPORT · TIMESHEETS · PERFORMANCE

2026

ENTERPRISE OPERATIONS

OneView enterprise portal displayed on a dark laptop against a stone background.

CONTEXT / WHY THE SYSTEM EXISTED

THE HARD PART LIVED BETWEEN WORKFLOWS.

OneView had to connect HR, finance, support, timesheets and performance without forcing every workflow into the same generic experience.

01 / FRAGMENTED WORKFLOWS

Different operational domains had their own tasks, rules and entry points.

HR · FINANCE · SUPPORT · PERFORMANCE

02 / MULTIPLE DECISION LAYERS

Employees submit, managers review, and admin or finance teams govern the outcome.

EMPLOYEE · MANAGER · OPERATIONS

03 / SHARED STATE + OWNERSHIP

Status, approvals and responsibility had to stay understandable as work moved between roles.

STATUS · APPROVALS · OWNERSHIP

DESIGN QUESTION

How do six operational domains feel like one system while keeping each workflow distinct enough to stay usable?

THE OVERVIEW STARTED WITH WHAT NEEDED ATTENTION.

01 / PRIORITY METRICS FIRST

Pending invoices, receivables, payables, budget use, payroll and tax actions surface before deeper detail.

02 / STATUS BESIDE ACTION

Current financial state stays next to the work users can act on.

03 / DEPTH WITHOUT OVERLOAD

Navigation keeps deeper finance operations one step away from the overview.

WORKFLOW PROOF / 01

ONE REQUEST. THREE DECISION LAYERS.

A requisition keeps its core context as it moves from creation to HR review and leadership decision.

01 / DEPARTMENT HEAD / CREATE

02 / HR / VALIDATE

03 / LEADERSHIP / DECIDE

The request kept its context while each role got the actions it needed.

SYSTEM CONFIGURATION / 01

SETUP FOLLOWED REAL DEPENDENCIES.

The setup wizard sequences organization profile, structure, integrations and access toward launch.

The setup order followed dependencies between steps.

MANAGER INSIGHTS / DECISION SUPPORT

TIMESHEET DATA HAD TO HELP MANAGERS ACT.

The manager view turned raw timesheet activity into something useful for staffing and approvals.

01 / WORKLOAD / UTILISATION

SEE PATTERNS BEFORE RECORDS

Monthly workload and utilisation patterns stay visible without opening individual timesheets.

02 / APPROVAL / STATUS

KEEP EXCEPTIONS VISIBLE

Approved and pending work hours remain visible by employee, so review gaps are easy to spot.

03 / BILLABLE MIX / OPERATING SIGNAL

SEPARATE ACTIVITY FROM VALUE

Billable and non-billable hours are separated so utilisation becomes a management signal, not just a total.

Surface decisions before details.

GUIDED ONBOARDING / CONTINUITY

PROGRESS STAYS IN VIEW.

One roadmap stays visible as onboarding tasks move from documents to policy and training.

01 / ROADMAP / PRE-BOARDING

KEEP THE ROADMAP STABLE

Completed, current and upcoming stages remain visible while the employee works through the active step.

02 / ORIENTATION / POLICY + TRAINING

MOVE FROM GUIDANCE TO ACTION

Policy acknowledgement, training, due dates and certificates stay inside the same journey without breaking orientation.

The roadmap stayed consistent as the work changed.

OUTCOMES / REFLECTION / 01

ONEVIEW GREW WITHOUT MAKING PEOPLE RELEARN IT.

Different workflows could remain specialised without making the product feel unfamiliar.

01 / STRUCTURE

MAKE COMPLEXITY LEGIBLE

02 / CONSISTENCY

KEEP BEHAVIOUR PREDICTABLE

03 / JUDGEMENT

LET CONTEXT CHANGE THE UI

MY ROLE

INFORMATION ARCHITECTURE WORKFLOW LOGIC PERMISSIONS INTERACTION SYSTEM CROSS-MODULE UX

REFLECTION

Screens could change from module to module. What mattered was that people could still predict what would happen next.

NEXT PROJECT / 02

TARBA

HEALTHCARE RESEARCH DATA GOVERNANCE

2024

VIEW PROJECT →