ALL WORK

LVL 04 — CAPITALAND

Making an IT park easier to see, manage and act on.

Structuring operational information so teams can move from an overview to the issue that needs attention.

ROLE
Product Design
TIMELINE
Historical project · timeline not listed
PLATFORM
Dashboard + Mobile
TEAM
Cross-functional team · details not listed
DOMAIN
Enterprise
Pixel-art illustration of an office campus with an operations dashboard
CONCEPTUAL PIXEL-ART ARTWORK — NOT AN ORIGINAL PRODUCT SCREEN. REPLACE WITH APPROVED PROJECT SCREENS.

01 / CONTEXT

The problem

Operational teams need a clear view of status, issues and next actions across a complex physical environment.

02 / TENSION

The challenge

Turn a dense operational picture into a hierarchy that supports monitoring, inspection and action.

A dashboard is only useful if it leads to a decision.

03 / PROCESS

The approach

DESIGN FOCUS — THE WORKFLOW BELOW SHOWS THE INTENDED PATH THROUGH THE PRODUCT.

  1. 01Dashboard
  2. 02Identify issue
  3. 03Inspect
  4. 04Take action
  5. 05Resolution
  • Information hierarchy
  • Overview → detail
  • Status visibility
  • Operational decision-making

04 / RATIONALE

Key decisions

DECISION 01

Design for exception scanning

Why it mattered
Operational attention is limited.
Design response
Prioritise changed and actionable states over neutral information.

DECISION 02

Connect overview to detail

Why it mattered
A summary without a path to diagnosis creates a dead end.
Design response
Keep location and issue context intact as users move deeper.

DECISION 03

Make ownership visible

Why it mattered
Knowing what happened is different from knowing what happens next.
Design response
Pair status with the next available action and resolution state.

05 / EXPERIENCE

The experience

KEY CONSIDERATION — VISUALS ARE CONCEPTUAL PLACEHOLDERS, NOT ORIGINAL PROJECT SCREENS.

Pixel-art illustration of an office campus with an operations dashboard
PLACEHOLDER ARTWORK — REPLACE WITH APPROVED PROJECT SCREENS.

06 / OUTCOME

Opportunity

OUTCOME DATA WAS NOT PROVIDED FOR THIS PROJECT.

This case study documents the design focus and intended experience without making claims about measured results, stakeholder feedback or usability findings.

07 / REFLECTION

What I would revisit today

Validate alert priority, escalation paths and cross-device continuity with the operational teams using the system.