Tempo

Tempo is a mobile app that connects truckers with shippers in real-time, simplifying the transportation process. The app provides a user-friendly interface for searching and filtering available loads and trucks, instant messaging and real-time location tracking for communication, and a feedback and rating system for maintaining a high level of quality and reliability. Tempo aims to reduce waste caused by miscommunication, provide transparency and accountability, and streamline the entire transportation process.

My Role

Solo UX/UI Designer
UX Research
Information Architecture
UI Design
Usability

Deliverables

User flows
Wireframes
Low-fidelity prototype
Research results
High-fidelity prototype

Tools

Figma
Google Forms
Zoom
Maze

Timeline

3 weeks

Overview

Problem Statement

Due to the lack of visibility and reliability, connecting truck supply to shipper demand is inefficient and difficult.

Users and Audience

The users are truckers looking for work, as well as shippers looking for trucks. Both of these groups are the audience for this product.

Solution

Create an app that serves the logistical middle man for the truckers and shippers to find one other and communicate efficient and trustworthy manner.

Process

I made use of the double diamond process, I found it to be an effective method for organizing my design process. The Double diamond process contains four phases:

Discover in which I established and tested hypotheses, uncovered user needs, collected and analyzed data, and established problem statements.
Define in which I decided what the problem will solve.
Develop in which I tested solutions, and established branding and style.
Deliver in which I completed the final product.

Goals

These were the main goals of the application:

To match trucker demand to logistical supply.
To reduce food wasted in transport

Discover

HwyHaul is a rapidly expanding digital freight platform, serves a diverse range of clients who require an effective Transportation Management System (TMS) to optimize their logistics operations. To address this need and strengthen its position in the market, HwyHaul embarked on the creation of a Software as a Service (SaaS) solution designed to deliver comprehensive TMS functionalities to its customers. This is my contribution that highlights the steps taken and the critical choices made in the design and development of this SaaS TMS offering.

Competitive Analysis

In order to better understand how transit apps work in the market currently, I downloaded the following apps to analyze: Uber Freight and Doft. I used a SWOT analysis, as well as a general observational task analysis on each app.

Strengths

Stations and routes are marked clearly on intuitive map.
The pricing is fair and readily visible.
The features are well organized.

Weakness

Missing perosnalization features.
Multiple pop- ups.

Opportunities

Improved prioritization.
Lower reliance on a pre-established brand guideline.

Threats

Well organized and clean interface.

Strengths

The map is clearly displayed.
Important dates are displayed with good hierarchy.
All the information is visible on one main screen.

Weakness

The progress is not visualized.
Lots of things on one screen. Can be difficult to look at.
Arrival time not displayed.

Opportunities

Better progress visualization.
Arrival time estimation.

Threats

Shows a lot of information thats relevant to the user.

Quantitative Research

To find out what the exact pain points and user experiences were like with the current state of fresh transport, and to get an idea of the user base, I conducted two surveys using Google Forms. The first survey was open to truckers from all backgrounds. The second survey was open to anyone that was in a managerial position that dealt with the booking of transportation using trucks. Both surveys entailed questions regarding demographics, general issues that make their job harder, and what we could provide them. The truck driver survey had questions specifically related to what issues they have with communication. The managerial survey had questions that related more to the difficulties they had finding and monitoring trucks.

Key Takeaways:

A vast majority of the carrier users prefer not to talk to managers. Many truckers and dispatchers found that a lot of time is spent talking about things that could easily be texted.

Location is the most important thing for truckers to know first. The location of the pickup and delivery is the first thing truckers want to know.

Pricing is one of the most important factors. Fair pricing for the drive is important to both parties.

Qualitative Research

I used in-person interviews to get a better idea of the audience and to get further insight regarding the pain points and needs of the users. I visit a loading zone to conduct these interviews, which lasted in between 20-30 minutes each. The participants were recruited via contacting the dispatcher through my client, who in turn connected us to truckers who were open to speaking with us. The participants were various truckers who were at the stop at our time and willing to speak to us regarding the app. They were offered $50 Visa e-gift cards as compensation for their time and willingness to help us.

Conclusion:

The findings of the survey seemed to reflect the quantitative data I gad gathered. This helped frame some of my decisions for the remaining elements on the app.

Personas

Journey Map

Define

User Stories

As a trucker, I want clear instructions from the managers and dispatchers, to minimize errors and the wastage of my time.

As a trucker, I want to know the exact time it will take and how much I will be paid for it, so that I can make a responsible decision on whether to accept the order.

As a logistical manager, I want the ability to monitor the shipment, so that I know the load is in good condition and on time.

As a supply manager, I want the ability book loads quickly and with good pricing so that I can save time in my daily routine and focus on other tasks.

User Flow

These were the initial user flows I drew up to build a wireframe of my project around. The amount of features increased once I developed my wireframe, but these flows served as the basis for my design.

Sketches

These are the initial sketches I came up with to map out the idea. The visual deisgn aspect was introduced to the project here. I used the crazy 8 method and the very rough wireframe method to map out the idea, as those are the ones I found to be most effective in my past projects.

Wireframes

These are the initial wireframes that I created for the two interfaces. They are divided into day 1 and day 2 because I wanted to flesh out the way the onboarding process would look like on the apps, as well as create a wireframe that demonstrates the regular use of the product.

Summary

Working with a client. This project provided me with a great opportunity to work with a real client. This gave me a lot of insight into how much clarity and guidance a client can provide, while also making me aware of of the constraints this can bring.

Interviewing real users. Thanks to my client, I was also able to schedule and participate in interviews with real truckers. The interviews and in person interactions provided many different challenges, from participants not showing up, to language barriers. Being able to do this and overcoming these challenges was a great way for me to learn about the realities of field research in this profession.

Working with tools. I was able to further my understanding of design tools such as Figma, as well as narrow down which sketching exercises and work styles worked best for me.

This project was a valuable learning opportunity as it allowed me to work alongside a client, and allowed me the opportunity to personally interview real people. These opportunities granted me a lot of insight into the research and client interaction aspects of the field.

Run-On

Bus app for a smoother transit experience.

→

Page updated

Google Sites

Report abuse