Slotxpert

B2B OPERATIONS & DATA MANAGEMENT PLATFORM

Redesign of a data-heavy B2B web platform used by internal teams to reduce operational errors and improve system adoption.

Client

The Port of Singapore Authority

The Port of Singapore Authority

Role

Product Designer (UX/UI)

Product Designer (UX/UI)

Platform

Web (B2B)

Web (B2B)

Timeline

Oct 2023 - May 2024

Oct 2023 - May 2024

TEAM

Product Manager, Developers, QA

Product Manager, Developers, QA

TL;DR

Problem :

High error rates and low usability in a complex, data-heavy internal platform.

User :

Internal operations and management teams.

Key challenge :

Improving accuracy without disrupting existing workflows.

My role :

UX research, interaction design, UI system, and developer handoff.

Outcome :

Reduced operational errors and improved system adoption within 6 months.

CONTEXT & CONSTRAINTS

Slotxpert is a B2B platform used daily by internal teams to manage large volumes of operational and analytical data.

The redesign had to work within several real-world constraints

  • Existing users were already trained on legacy workflows

  • Large tables and dense datasets with a high risk of human error

  • Limited tolerance for drastic UI changes

  • Tight delivery timelines aligned with business operations

  • Dependency on existing backend logic and data structures

Before the redesign, internal surveys were conducted with buyers and sellers to understand usability and confidence levels in key workflows such as booking and listing containers.

Survey results highlight that while most users could complete tasks, a significant portion reported uncertainty, friction, and lack of confidence—indicating a system that worked but was not optimized.

The Core Problem

Users frequently made mistakes due to dense tables, unclear visual hierarchy, and inconsistent feedback across key actions. These issues directly affected operational efficiency and reduced trust in the system.

My Role & Responsibilities

I worked as the Product Designer responsible for improving usability and reducing errors while maintaining familiarity for existing users.

• Audited existing workflows to identify error-prone actions

• Simplified information hierarchy in complex tables and dashboards

• Designed interaction patterns focused on error prevention and clarity

• Built a consistent UI system aligned with technical constraints

• Collaborated closely with developers to ensure feasible implementation

Information Architecture & User Flows

Due to the complexity of the system and the volume of data involved, clear information architecture and task-focused user flows were critical to reducing cognitive load and preventing errors.

Wireframes & Layout Exploration

Wireframes were used to explore layout options, validate information hierarchy, and test interaction patterns before moving into high-fidelity design.

Seller Wireframes

Buyer Wireframes

Key Design Decisions & Trade-offs

  1. Prioritized error prevention over visual minimalism
    Clear states, confirmations, and validations were favored over aggressive UI reduction.

  1. Used progressive disclosure for complex data
    Instead of showing all data at once, information was revealed contextually to reduce cognitive load.

  1. Preserved familiar interaction patterns
    Core workflows were intentionally kept recognizable to minimize retraining costs for internal teams.

  1. Accepted UI limitations imposed by backend constraints
    Some ideal design solutions were adjusted to align with existing data logic and development timelines.

Final UI Screens

The final UI focuses on clarity, predictability, and error prevention while maintaining familiarity for existing users.

Impact & Results

  • ~35% reduction in user errors based on internal QA logs over 6 months

  • ~85% adoption across internal teams following rollout

  • ~80% retention compared to the previous workflow version


    • Metrics are based on internal system data and stakeholder feedback.

What I Learned

• In B2B systems, predictability is often more valuable than novelty

• Small interaction improvements can significantly reduce operational errors

• Designing within constraints leads to better long-term adoption and trust