01Portmasters

Case studyLogisticsWeb platform

Making freight booking transparent.

Portmasters connects freight carriers with the people who ship. I took it from the first stakeholder interview to a developer-ready UI kit.

Role
Product designer, UX + UI
Year
2024 – 25
Scope
Research, UX, UI, UI kit
Platform
Web, desktop + mobile
Portmasters rates table on a tablet held in two hands, with the Portmasters wordmark above

01 — Overview

Freight still runs on phone calls.

Large carriers, forwarders and individual shippers still coordinate cargo by phone and in person. There was no transparent price comparison and no real-time tracking. Every company managed its orders, its team and its payments by hand.

The brief

The company asked me to improve the brand identity, fix the user flows, add competitive features and design an up-to-date website that could scale.

The approach

Competitor analysis and user research showed where to focus. The answer was dedicated dashboards for each user segment, with the most requested features built in first.

  • 9core problems defined
  • 13interview insights analysed
  • 13“How might we” questions
  • 3competitors reviewed
  • 2user personas
  • 18planned activities, July to March
Portmasters quote page on a laptop: every leg of the route with its fees and a total
The quote page: every leg of the route, its fees and the total in one view.

02 — Process

Four phases. An agreement after every step.

I planned the work as four phases and ended every stage with an agreement checkpoint with the client. At the end of each week the team and the client knew exactly which deliverables to expect.

The roadmap: 18 activities in four phases, from July to March. Pick a phase above to see what it covered.

03 — Research

Nine problems, nine answers.

From the stakeholder interviews and a quick discovery step I wrote down what the product had to solve. Each problem got a concrete product answer.

Interviews

What customers actually said.

I put the most valuable interview data in one place and added my ideas, questions and comments. Then we went through it with the client, agreed on the ideas and got answers to the open questions.

User 01 · Regular customer

“I want to be able to have full control over choosing the company, route, and price.”

DecisionA search bar front and centre: the main function of the site, in the most visible place.

User 02 · Regular customer

“I need unconventional freight shipping options. I often transport items that most carriers won’t accept.”

DecisionEvery standard and code available to choose from, and every price factor shown clearly.

User 03 · Company owner

“Managing team members… is truly my most critical need.”

DecisionA dedicated company panel. Team members join by invitation, each with their own access level.

Interview data analysis · working fileSwipe to explore
Sticky-note board with interview quotes from three users and the team’s decisions

How might we

Thirteen questions, one idea each.

I generated as many “How might we” questions as I could from what we already knew. For each one we sketched one or more ideas for solving it in the interface.

Competitors & structure

From the market to a structure.

I analysed how competitors solve the same problems and collected UX and UI examples from each one. I added ideas, comments and questions to every example, to discuss with my team and the client.

  • Searates
  • Freightos
  • Flexport

Then I gathered everything from the first stage, grouped it by topic and grouped the groups again. That layered grouping gave the product its general structure and the points it stands on.

Next I turned every group into a precise written description of the interface of each module, as detailed as I could make it.

04 — Users

Two people to design for.

I built personas from the interviews to understand their objectives, problems and likely behaviour. Then I connected each persona to the agreed product structure and wrote a story map for them, to predict where the interface could go wrong.

Persona card: Elena Dubois, 39, e-commerce company manager
Persona card: John Marceau, 43, logistics company manager

05 — Structure

From use cases to a screen map.

Based on the concept, the journey of each persona and the list of use cases, I could see the whole structure of the product. I drew low-fidelity wireframes for each module first, agreed them with the client, then raised them to high fidelity.

  • Booking
  • Create a rate
  • Manage table
  • Report
  • Wallet
  • Profile
Map of all high-fidelity screens grouped as public pages, sign up and login, user panel and company panel
Every high-fidelity screen on one map: public pages, sign up and login, the user panel and the company panel.

06 — Interface

The final screens.

The UI is grouped logically by module and feature, so each user finds their own space.

Rate search results page in a browser Booking tracking page with route map and milestone timeline Work space with a kanban board of orders Manage rates page with the new rate modal open

01 / 04

Rate search: filter by services, price and transit time, then book.

And on the phone.

The platform works on mobile too: tracking, payments, documents, quotes, a profile and an AI copilot for customs questions.

Mobile booking tracking screen
Tracking
Mobile payments screen
Payments
Mobile documentation screen
Documents
Mobile list of quotes
Quotes
Mobile profile screen
Profile
Mobile AI copilot chat answering a customs regulation question
Copilot

07 — Design system

A UI kit for the developers.

For the developers I built a fully detailed UI kit with every design element they need, so each screen can be built the same way, every time.

Colour palettes in light and dark mode Typography: SF Pro Display headlines and SF Pro Text labels Icon set in 24px and 20px, outline and bold Button styles: primary, secondary, tonal and negative, with all states Input fields with and without measures A 4 pixel grid and the dimension scale

08 — Delivered

What the team received.

  • ResearchProblems and goals, interview analysis, “How might we” ideas, competitor review, personas, journey maps and use cases.
  • StructureLow- and high-fidelity wireframes for every module, agreed with the client at each stage.
  • InterfaceComplete UI for the public pages, user panel and company panel, on desktop and mobile.
  • UI kitColours in light and dark, typography, icons, buttons, inputs and a 4 px grid, with specifications for the developers.

More case studies

Keep exploring.