Conceptual B2B SaaS Logistics Enterprise Dashboard

Orbit.
Supply Chain War Room

A unified command centre for operations teams managing global supply chain disruptions.

Role
Product Designer
Domain
Logistics · Supply Chain · Enterprise SaaS
Platform
Desktop
Scope
UX Research · IA · Dashboard Design · Data Viz · Interaction Design · Design System

Modern supply chains generate an enormous amount of information — the challenge isn't a lack of data, it's knowing what requires attention right now.

01Overview

From reporting information to supporting decisions.

Orbit is a conceptual B2B SaaS platform designed to bring fragmented supply-chain signals — shipments, vendors, inventory, ports, geopolitical events, operational risks — into one operational command centre.

The goal was to move from a dashboard that simply reports information to a system that helps operations teams understand risk, prioritise problems, and decide what to do next.

02The problem

Dozens of vendors. Hundreds of shipments. One fragmented view.

Operations teams may be responsible for dozens of vendors and hundreds of active shipments while simultaneously monitoring external disruptions. Information is often distributed across multiple systems, making it difficult to answer simple but critical questions:

The opportunity was to create a single operational view that connects these signals instead of forcing users to investigate them separately.

How might we help operations directors identify supply-chain risks early and turn complex operational data into clear, actionable decisions?

03Understanding the user

Operations Director

Responsible for monitoring supply-chain performance, identifying disruptions, managing vendor risk, and coordinating responses across the organisation.

What they need
A high-level view of supply-chain health
Immediate visibility into disruptions
Context around affected shipments and vendors
Confidence when evaluating risk
Clear recommended actions
Executive-level summaries for decision making

Orbit therefore needed to support both rapid scanning and deep investigation.

04Information architecture

Organised around the questions the team needs to answer.

Overview
What is happening right now?
Shipments
Which shipments are moving normally and which are at risk?
Vendors
Which suppliers represent the highest operational risk?
Inventory
Where could supplier or shipment disruption create shortages?
Disruptions
What external events could affect operations?
Reports
What should leadership know?
Situation
Risk
Impact
Action
05The dashboard

The operational command centre.

At the top, a KPI strip provides an immediate health check: at-risk shipments, delayed vendors, stockout predictions, days of inventory.

The primary visual layer focuses on global disruptions and their relationship to the supply network. Instead of treating the map as a decorative visualisation, Orbit uses it as an interactive navigation surface — selecting a disruption filters the surrounding information to show the shipments and vendors affected by that event.

The visualisation is functional, not ornamental.

06The screens

Five views, one operational workflow.

01 — SCREEN

Global Disruption Overview

Answers the question: what's happening across the supply chain? A world map provides the main spatial overview — shipment routes connect origins and destinations while disruption markers highlight events.

Disruption markers
Port disruptions Weather events Geopolitical alerts

The KPI layer provides immediate operational context alongside the map.

Key UX decision — The map is navigation, not decoration
A user can select a disruption and immediately understand its downstream impact — creating a connection between event → shipment → vendor → operational risk, rather than presenting each dataset in isolation.
02 — SCREEN

Shipment Deep-Dive

When a shipment requires investigation, Orbit moves from the global overview to a focused timeline.

Shipment view surfaces
Origin Destination Current location Estimated arrival Delay information Customs status Latest update Alternative routes

The timeline helps users understand not only where the shipment is, but also why it may be delayed.

Designing for action
If a shipment becomes disrupted, the interface can surface alternative routing options instead of forcing the user to leave the product and investigate manually.
03 — SCREEN

Vendor Risk Scorecard

Supplier risk is rarely caused by one variable. Orbit breaks the overall vendor risk score into multiple dimensions.

Risk dimensions
Financial health Geopolitical exposure Delivery reliability Quality compliance

This gives users a way to understand the composition of risk instead of relying on a single unexplained number.

74
False precision
74 ± 8
Honest estimate
Key UX decision — Communicate uncertainty
Rather than presenting "Vendor Risk: 74," Orbit communicates "74 ± 8" — the purpose is to avoid creating a false sense of precision. Risk is treated as an estimate rather than an absolute truth.
04 — SCREEN

Inventory Shortage Predictor

The next question after identifying a supply-chain disruption is: what could this disruption affect? Orbit connects supplier and shipment risk with inventory.

Shortage horizon
30 days 60 days 90 days

The interface uses a simple risk hierarchy so teams can quickly identify products requiring attention. The experience also connects the insight to an operational action: raise emergency purchase order.

Design intent
This shifts the dashboard from reporting problems to helping users respond to them.
05 — SCREEN

Executive Summary

Not every stakeholder needs the same level of information. Operations teams need detailed operational data. Leadership needs the answer.

Distilled into
Key disruptions Top vendor risks Major operational impacts Recommended actions

The visual language becomes simpler and more focused. The report is designed for leadership consumption and can be exported for board-level discussions.

Design principle — Minimum data. Maximum clarity.
The Executive Summary distils the week's most important information rather than repeating the operational view at a smaller scale.
07Three key UX decisions

The decisions that shaped Orbit.

01
The map became an interaction layer
Many dashboards use maps simply because they look impressive. Orbit uses the map to drive exploration — selecting a disruption changes the surrounding context and helps users understand which shipments and vendors are affected. The visualisation becomes part of the workflow.
02
Risk includes uncertainty
A single risk number can create false confidence. Instead of presenting a vendor as simply having a risk score of 74, Orbit communicates the estimated range — 74 ± 8 — encouraging users to interpret risk with appropriate caution.
03
Every problem leads toward an action
A dashboard shouldn't stop at "something is wrong." It should help answer "what should I do next?" Orbit introduces recommended actions directly into operational tables — expedite, find alternative, monitor, no action needed — transforming information into decision support.
08Visual & data design

Not every number deserves equal weight.

Because Orbit handles several layers of operational information, hierarchy was critical. Risk indicators, alerts, KPIs, maps, tables, and timelines each have a distinct visual role.

Primary
What requires attention immediately?
Secondary
Why is it happening?
Supporting
What additional context is available?

This prevents the dashboard from becoming a wall of equally important numbers.

09The design principle

"Don't make users search for the problem. Help them understand the problem and decide what to do next."

Detect Understand Assess Act
10Outcome

From analytics dashboard to decision-making experience.

Orbit demonstrates how complex supply-chain information can be transformed into an operational decision-making experience. Rather than designing another analytics dashboard filled with charts, the project focuses on:

Contextual data Risk visibility Spatial navigation Uncertainty Predictive information Recommended actions Executive communication

The result is a conceptual enterprise SaaS platform designed around the workflow of operations teams rather than the structure of the underlying data.

11What I learned

Four things this project reinforced.

01
More data doesn't mean more clarity
The challenge in enterprise dashboards is often deciding what not to show.
02
Visualisations need a purpose
A map, chart, or graph becomes valuable when it helps users complete a task.
03
Risk needs context
A number without an explanation can create misleading confidence.
04
Dashboards should support decisions
The strongest enterprise experiences don't simply tell users what happened — they help them determine what happens next.
Orbit in one sentence

Orbit turns fragmented global supply-chain signals into one clear operational command centre where teams can detect disruption, understand risk, and act with confidence.

Project details
TypeIndependent portfolio concept
RoleProduct Designer
DomainLogistics · Supply Chain · Enterprise SaaS
PlatformDesktop
ScopeUX Research · Information Architecture · Dashboard Design · Data Visualisation · Interaction Design · Design System

Explore

Orbit is a conceptual enterprise SaaS project designed for portfolio purposes. It is not a shipped product, and no proprietary data or confidential systems were used.