Product designer · ENXT · 2025

ENXT

1

Context

ENXT is a B2B platform for managing aviation cargo operations.

The AWB (Air Waybill) creation page is the key working screen for agents and operators: this is where shipments are formed, routes are added, codes are verified, and operational parameters are entered. This screen was used daily and directly impacted cargo processing speed.

2

Understanding the problem

The old version of the booking page was a long vertical form:

  • over 2 viewports of scroll
  • constant scrolling
  • frequent modal windows
  • scattered information blocks
  • high cognitive load

As a result:

  • users would return to already filled fields
  • errors occurred in required data
  • input speed suffered

The product domain was highly specific — I had to deeply understand the subject matter and interface structure.

3

Redesign goal

Make the booking flow more compact and readable:

  • Optimize screen usage
  • Minimize/eliminate vertical scroll
  • Reduce cognitive load
  • Embed frequent actions into the page instead of modals
  • Ensure responsiveness (desktop/tablet)
4

Metrics

5

Result

After the redesign:

  • page reduced from 2+ to 1.25 viewports
  • average AWB creation time decreased by ~25%
  • field revisits dropped by nearly 40%
  • number of modal interruptions cut by more than half
  • cognitive load (visual blocks in viewport) reduced by 36%
6

My role

  • UX audit of the existing form
  • Information architecture of the booking service and platform navigation
  • Design decisions and iterations (v1 → v2)
  • Specifications and behavior descriptions for UI elements (paired with front-end developer)
  • Syncing the design system with the front-end codebase
  • Time management and meeting moderation

Before

The old version was a feature-rich screen with a linear vertical structure. As functionality grew, the page architecture was never reconsidered, resulting in vertical overload and constant scrolling. Logically related data was spread across separate cards, and some actions were placed in modal windows, interrupting the workflow.

Redesign v1.0

Structural rebuild and systematization

The project was run in a dev-first environment and used an outdated version of Material UI (React), with numerous custom style overrides and local solutions. So in the first redesign iteration I didn't change the business logic of the flow, but focused on a systematic rebuild of the interface.

Technical work:

  • Migration to a current version of Material UI
  • Elimination of accumulated local overrides and inconsistent styles
  • Collaborative work with front-end to sync the library in code
  • Building a design system based on the new Material version

At the UX level:

  • Grid and block layout streamlined
  • Visual overload reduced
  • Input fields, tabs, chips, toggles unified
  • Revenue and Operational Details readability improved
  • Fixed action bar with totals added

Redesign v2.0

Architectural optimization of the flow

In the second redesign iteration I reconsidered not just the visual system, but the page interaction structure itself. What changed:

  • Linear vertical form transformed into modular navigation
  • Key sections moved to a top segmented control
  • Persistent Booking Summary added for contextual feedback
  • DIMs extracted into a standalone module
  • Routing section simplified and restructured
  • Revenue and Operational Details optimized

The key difference between v2 and v1:

1

Context

Ground Ops is a module within the ENXT platform for managing aircraft turnaround. Turnaround is the period between arrival and departure. During this time, dozens of actions need to be completed by different teams:

  • unloading
  • loading
  • equipment connection
  • fueling
  • inspections

The system has two distinct audiences:

  • Coordinator / administrator — configures templates, processes and turnaround structure
  • Executor — works “in the field” and performs specific actions per flight
2

Understanding the problem

I started by separating roles and identified the core principle:

  • Everything configured by the coordinator must display correctly for the executor
  • Everything the executor does must fit logically into the overall time model

Importantly, aircraft turnaround is a hierarchical system: Template → Processes → Actions → Parameters.

Each action:

  • has a precise start time (in minutes)
  • has a duration
  • belongs to ARR or DEP phase
  • may depend on other actions
  • may contain nested parameters
  • must be recorded in the log
3

My role

  • UX architecture design for the Ground Ops module
  • Timeline logic development
  • Stage structure and nested parameter design
  • Executor web interface and state scenarios
  • Transition logic design (Start / Finish / Report Issue)
  • Preparing interfaces for development and discussing behavior with front-end

Creator

The main organizing principle is time. It is displayed as a timeline on a minute scale. Actions are created on the timeline, divided into arrival and departure stages. Each action has a layer of parameters (nested fields), shown in a panel on the right. An activity log tracks all changes.

Executor

Doesn't work with the full model. What matters to them:

  • which flight
  • what needs to be done now
  • what's next
  • what's already completed

I divided tasks into three time groups: current, upcoming, done. The individual action screen includes: time, stage, timer, input form, control buttons (Start / Finish / Report Issue). Interface states change depending on the execution stage.

ENXT Solutions
← Vedic Turkiye Skysmart →