ARDNTPortfolio
Back to selected work

Operations dashboard

Lumen Dashboard

Analytics that feel calm — data-dense without the anxiety.

Role

Product designer & fullstack developer

Duration

8 months

Year

2026

Status

In production

3 company implementations

Lumen Dashboard

The brief

From context to system.

Overview

A modular real-time operations dashboard adapted for three companies with different workflows, data sources and approval structures.

Background

Operational teams were making daily decisions from fragmented spreadsheets, delayed exports and dashboards that exposed every metric at once.

Challenge

Design one stable dashboard foundation that could adapt to different organizations without turning into three disconnected products.

Goals

Reduce reporting time, improve decision confidence and create reusable modules for future company rollouts.

Core solution

A modular dashboard system with role-aware navigation, composable widgets and per-company integration adapters.

Process

The work moved from workflow interviews and information mapping to low-fidelity task prototypes, a shared component system and staged company rollouts.

Technical architecture

A typed React frontend consumes normalized domain APIs while company-specific adapters isolate ERP, HR and sales data differences.

Key capabilities

  • Role-aware workspaces
  • Composable analytics widgets
  • Approval workflows
  • Real-time alerts
  • Exportable reports

Implementations

One system,
different realities.

Each rollout adapted the core product to a different company, workflow and operational constraint.

01
N

Nusantara Logistics

Logistics · Jan–Apr 2026

Branch operations control center

Nusantara Logistics implementation

Context

Regional operations teams needed one view across twelve branches and daily delivery exceptions.

Requirements

Branch comparison, delayed-shipment alerts and ERP-backed operational reporting.

Custom adaptation

A geographic hierarchy and exception-first workflow replaced the platform's default department navigation.

Solution

A normalization layer aligned operational entities before data entered the dashboard modules.

Challenge

Source systems used inconsistent branch identifiers and updated on different schedules.

Outcome

Weekly reporting moved from manual spreadsheet consolidation to an automatically generated operational review.

ERPFleet trackingEmail reports
02
A

Aster Retail Group

Retail · Mar–Jun 2026

Regional sales intelligence

Aster Retail Group implementation

Context

Regional managers lacked a consistent daily view of sales performance and inventory pressure.

Requirements

Store comparison, target tracking, promotion performance and mobile-friendly summaries.

Custom adaptation

Widgets were reorganized around commercial regions and promotion cycles rather than operations teams.

Solution

Every module exposes its last synchronization state and falls back gracefully when inventory data is delayed.

Challenge

Sales and inventory data arrived at different intervals and needed clear freshness indicators.

Outcome

Regional reviews shifted from retrospective monthly reports to daily exception-based decisions.

Point of saleInventory APICampaign calendar
03

Confidential organization

May–Aug 2026

Multi-level approval monitoring

Confidential organization implementation

Context

A regulated operations team needed visibility into approval queues without exposing sensitive customer records.

Requirements

Strict role permissions, approval aging, audit trails and private-network deployment.

Custom adaptation

The platform added fine-grained authorization and aggregate-only views for executive roles.

Solution

Data minimization rules were applied at the API boundary, with the UI designed around operational aggregates.

Challenge

The interface had to remain useful while minimizing personally identifiable information.

Outcome

Teams gained queue visibility and escalation signals without expanding access to sensitive records.

Identity providerApproval engineAudit storage

Overall outcome

The shared platform replaced repetitive manual reporting while preserving each company's operational differences.

What I learned

Multi-tenant products need explicit boundaries between reusable domain behavior and organization-specific workflow rules.

Explore further

See the product or inspect the build.

Live project Repository