Product Design  ·  B2B SaaS  ·  Infrastructure AI

Designing
trust into
critical
infrastructure

Pred4Infra monitors bridges, pipelines, dams, and industrial machinery with cyberphysical AI. The technology worked. The interface didn't earn trust.

Company
Predulive Innovations Korea
Role
Lead Product Designer
Timeline
12 weeks · Q4 2025
Scope
5 modules · End-to-end
Redesigned Pred4Infra Infrastructure Dashboard
01
Situation

A disruptive product nobody trusted

The platform was technically ahead of every competitor — physics-informed AI, live LiDAR, 3D digital twins, autoregressive failure prediction. But it had been built engineer-first.

Operators were ignoring alerts, misreading visualisations, and overriding AI recommendations out of habit, not evidence. The intelligence wasn't being used.

Operations live monitoring
Operations — live structural monitoring with 3D point cloudRedesigned
AI Copilot intelligence panel
AI Copilot — real-time intelligence with generated insightsRedesigned
02
The Problem

Six failures.
One root cause.

A trust deficit running through every screen.

Original Admin — mixed controls
Platform and org controls mixedBefore
Failure 04
Platform and org controls mixed
Client admins could trigger system-wide changes. Restart Server had the same visual weight as Auto Backup.
Original 3D viewer — broken state
High-compute sessions auto-loadedBefore
Failure 05
High-compute sessions auto-loaded
Remote rendering fired on every page load. 10 to 20 seconds of apparent failure. The team called it the broken tab.
Original Infra Dashboard — undefined tags
No freshness, no definitions, no legendsBefore
Failure 01–03
No freshness, no definitions, no legends
Timestamps missing. Severity labels undefined. Heatmaps without a legend. Operators couldn't trust any number, anywhere.
Core insight
"Not a features problem. A trust deficit at every layer."
03
Key Decisions

Three decisions that
defined the redesign

Before. After. Why it mattered.

01
Infra Dashboard + Operations

Severity levels given a threshold, a response window, and a guided action

Before
Original condition tags
Condition tags with no defined thresholdsBefore

Status labels with no definition. "Moderate Stress" meant something different to every operator. In incident response, ambiguity caused real delays.

After
Redesigned status table
Defined severity with response windows and timestampsRedesigned

Each status carries a threshold, a response window, and a guided next step. Every row shows live data freshness. The label tells you what to do.

WhyIn critical infrastructure, ambiguity costs time. Time costs lives.
02
3D Visual

The broken tab redesigned as a deliberate 5-state inspection experience

Before
Original 3D viewer
Auto-loaded compute session, appeared brokenBefore

Remote rendering fired on every page load. No user intent. The team called it "the broken tab."

After
Analysis Mode Selection
View Selection: user chooses mode, then connectsRedesigned

Four named inspection modes with data source, reliability score, load time. User chooses, then connects. Intent captured. Resources spent deliberately.

WhyChoosing a mode primes the user's interpretive frame. They know what they're about to see and what it means.
03
Admin Dashboard

Admin split into Platform Admin and Organisation Admin — two architecturally separate views

Before
Original Admin mixed controls
Platform controls and org controls, same visual weightBefore

One screen, two audiences, no distinction. Client admins could trigger platform-wide changes. A governance liability.

After
Redesigned Admin separated
Two views, two audiences, zero crossoverRedesigned

Platform Admin gated behind elevated auth with 2FA for critical controls. Org Admin for users, roles, alerts. Two views. Zero crossover.

WhyEnterprise procurement teams ask one question before signing: is this safe to govern? The original Admin screen failed that test.
04
The Redesigned Platform

All five modules.
High fidelity.

Each module redesigned to answer one question and one question only.

Infrastructure Dashboard
Infrastructure Dashboard — zone-based overview, defined severity, live statusRedesigned
Operations live monitoring
Operations — live structural monitoring, point cloudRedesigned
Operations incident triage
Operations — Immediate Action card with guided escalationRedesigned
Operations camera and thermal
Operations — live cam with source-labelled thermal overlayRedesigned
Operations trend charts
Operations — trend charts with threshold lines and time controlsRedesigned
3D Visual mode selection
3D Visual — Analysis Mode Selection, reliability scoresRedesigned
3D Visual connected session
3D Visual — connected inspection with mode legendRedesigned
Admin redesigned
Admin — separated governance layer, audit trailRedesigned
Admin user management
Admin — user management, role distributionRedesigned
AI Copilot insights
AI Copilot — real-time infrastructure intelligenceRedesigned
AI Copilot executive brief
AI Copilot — executive briefs with data lineage on every outputRedesigned
05
Outcomes

What the redesign delivered

5 to 1
Coherent 3D state machine
"The broken tab" became the most praised screen in stakeholder reviews.
2
Admin layers, zero crossover
Platform and org controls architecturally separated. Enterprise procurement blocker removed.
100%
Data freshness coverage
Every panel across all five modules surfaces a live timestamp with visual degradation.
4
Severity levels defined
Each status carries a threshold, a response window, and a guided action.
5
Modules to high fidelity
Full component library and engineering annotation spec delivered in 12 weeks.
1
Governing principle
"Trust is the feature" kept five very different screens coherent throughout.
Redesigned Admin user management
The redesigned Admin — separated user management, role distribution, session tracking. Enterprise-procurable.Outcome
06
Reflection

What I carry forward

1
Trust is a design material

A timestamp is a trust signal. A confirmation dialog is evidence that the system respects the gravity of the action. Every element either builds or erodes trust.

2
Naming is architecture

Renaming "GLB Model" to "Digital Twin Viewer" changed how users modelled the tool, which changed mode selection, which changed interpretation. The most impactful decisions were taxonomic, not visual.

3
What I'd do differently

Get real operators into usability sessions earlier. Bridge engineers, HSE managers, control room supervisors. The audit was expert-led. Lived operator intuition under real pressure finds what structured analysis misses.

Available for thoughtful product work

Nice to have you here.

I’m open to full-time & freelance opportunities

Let's Talk!

Available for thoughtful product work

Nice to have you here.

I’m open to full-time & freelance opportunities

Let's Talk!