TriumphNet

Lawrence Tang

UX Designer
Figma
TriumphPay

Overview

In the trucking industry, there are 4 roles:
Carriers - Hardworking truck drivers who transport loads from one place to another (A to B).
Brokers - Middlemen that connect shippers who have loads with carriers willing to transport them.
Factors - Similar to brokers, but they pay carriers earlier for a fee, offering quicker payment options.
Shippers - Manufacturers who have loads ready to be transported.
Carriers are the heart and soul of the trucking industry. They brave the roads, risking their lives to deliver shipments safely and on time. Without them, we wouldn't have everyday essentials like clothing and food. Carriers rely on their brokers or factors to ensure they get paid on time, supporting their livelihood and keeping goods moving.

Problem

According to TruckInfo.netthere are 3.5 million truck drivers in the US with a median salary of $49,920 as of 2022. Unfortunately, carriers often face issues with underpayment or delayed and incorrect payments, caused by bad data from payors (brokers, shippers, or factors) or even fraudulent activities.
To get their payments sorted out, carriers have to make multiple calls to their associated payors or turn to companies like TriumphPay, a fintech company in the trucking industry that has a payment app for carriers. This constant communication wastes valuable time and leaves carriers frustrated.
But now, there's a solution! With a new platform at TriumphPay, we can access verified carrier data all in one place, making payment issues a thing of the past.

Solution

Introducing TriumphNet, a fantastic new tool at TriumphPay! It helps Carrier Record Admins keep track of verified carrier records and connect them with data from brokers, shippers, and factors. This ensures that carriers get paid accurately and on time.
In simple terms, TriumphNet is like a super helpful hub that improves the payment process, and helps identify/prevent fraud. It makes things easier for everyone inside the company and also benefits our carriers.

My Role & Scope

I was the UX Design lead for this new internal tool at TriumphPay, where I collaborated with stakeholders for requirements/feedback and executed final high-fidelity design solutions.

Discovery & Process

User

Since TriumphNet is an internal tool, the user would be an employee at TriumphPay. Specifically, the role would be a Carrier Record Admin. A Carrier Record Admin would resolve exceptions regarding global carrier records to maintain accuracy and verification. This would be a brand new role.

Stakeholders

Stakeholders were internal TriumphPay employees, which included: Developers, Product Managers, Sales Engineers, Chief Product Officer, and Admin. We would meet frequently to collaborate for requirements/feedback to empathize with the user and iterate for the most optimal design solutions.

Research

I analyzed competitors and conducted secondary research to assess best practices for creating tables since they would be a major component in the UI.

Design

The design process for this project was a goal and solution approach to address each user flow.

Goal #1

View unverified or verified carrier record data from brokers, shippers, or factors.

Solution

Select brokers, shippers, or factors and choose an individual company to view its carrier record data as exceptions (unverified) or matches (verified).

Goal #2

Connect unverified carrier records of a broker, shipper, or factor with verified carrier records in order for carriers to get paid timely and correctly. Alternatively, show actions to take if there are no possible records to connect with.

Solution

When you click on an unverified carrier record, you'll see possible verified carrier records sorted by the best match. These matches are highlighted in green with checkmarks, showing the data points they have in common. You get to decide which verified carrier record to connect with to resolve the exception. If there are no matches, you can either contact the right payor (broker, shipper, or factor) or create a new verified carrier record

Goal # 3

Resolve any mismatch of factor data when it occurs as the user attempts to connect an unverified carrier record with a verified one. There are 3 scenarios where this can be prompted.

Solution

A progressive disclosure modal where the user may see factor information and upload required documentation to assign a new factor and/or release a current one. This is determined based on what scenario the factor mismatch is.

Global carrier has a factor and carrier record has no factor

Carrier record has a factor and global carrier has no factor

Global carrier and carrier record have different factors

Goal # 4

Disconnect a broker, shipper, or factor from a verified carrier record if they should not associate with each other.

Solution

After the user clicks into a verified carrier record, they can select associated brokers, shippers, or factors and choose an individual company record to disconnect it from the carrier record.

Goal # 5

Create a new verified carrier record only if there are no possible records to connect with.

Solution

A full page progressive disclosure view where the user can manually enter information of a carrier to create a new record, and then submit for approval.
Partner With Lawrence
View Services

More Projects by Lawrence