SMART PORT
Category
Enterprise UX · Product Design
/
/
The goal was to help large fleet managers have a ease of aceess to manage the papaerwork for every single work in their fleet
A port runs on sequence. A vessel arrives, cargo is declared, documents move through approval, a gate pass is issued, a truck leaves. SMART PORT is the platform operators use to run that sequence.
It had been built as a set of modules, and the modules mirrored the departments that owned them. Vessel information in one place, gate operations in another, documents in a third, reporting in a fourth. Every module was internally sensible. The problem was that no operator's actual job lived inside a single one.
Getting one consignment out of the port meant moving through four modules, re-entering context at each boundary, and holding the sequence in your head because nothing on screen held it for you. The platform expected the operator to know the organisation's structure in order to do a task inside it. New staff learned the software by learning the org chart.
I reorganised the interface around the operational sequence instead.
The unified dashboard replaced the module menu as the entry point. Vessel movement, gate pass activity and reporting sit on one surface, so the operator opens the platform to the current state of the port rather than to a directory of departments.
The document workflow was the clearest case. Submitting a document meant filling a form in one place, uploading the file somewhere else, and tracking approval in a third — three locations for one continuous action. I rebuilt it as a single interface carrying form, upload and approval end to end, so the thing the operator thinks of as one task is one task on screen.
The analytics views were rebuilt around questions rather than tables. The platform had never lacked data; it lacked any view that turned the data into something a supervisor could act on in the moment.
Underneath all of it I built a design system — reusable components, a defined type scale, and colour standards checked for contrast. Government platforms are used for years by people with a wide range of screens, lighting conditions and familiarity with software. Consistency and legibility aren't polish there. They're the difference between a platform staff trust and one they work around.
Enterprise software tends to be organised by the people who commissioned it. The data model gets drawn first, the departments claim their territory, and the interface inherits both. The operator arrives last and is asked to absorb the structure.
Reorganising around the sequence of work didn't add features. It moved the burden of holding the process off the person and into the system, which is where it should have been.
