top of page
logtrack splash.png


A freelance project to help a client deliver a powerful set of tools to small trucking companies.

Time Frame

Three Business Weeks

August 2022

Task Background

Myself and a team of four other UX/UI design fellows lent freelance services to a start-up client through a partnership with General Assembly.

  • Prototypes of minimum viable product

  • Specification documents

  • Project report

  • Presentation/deck

My Primary Roles
  • Project Manager, stepping in to help with research and design

  • Archetypes/journeys 

  • Research report drafting

  • Presentation direction

Project Overview

LogTrack, a product of the LogAware company, aims to bring enterprise-level tracking and information tools to smaller trucking companies.
logtrack splash 2.png

Mobile App Features

Document Upload  |  Driver Tracking  |  Geofence-Triggered Reminders
Current Job Information  |  Work Status Toggle
mobile wireframe 2.jpg

Click to view more.

Desktop Dashboard Features

Geofencing Notification Setup  |  Document Organization & Sharing
Job Information/Tracking Sharing  |  Live Transporter Tracking
annotated dashboard.jpg

Click to view more.

Our Routes Of Understanding Users

Many logistics-industry platforms that deliver LogTrack's intended features are either expensive, or remain locked behind competitors' marketplaces and/or assigned jobs. LogAware, the company behind LogTrack had features in mind, but required the UX/UI touch to bring it to the right users, who join the industry from all backgrounds.

User Research

In tackling research, due to the nature of the industry, we realized it would be hard to get every detail of certain demographics' day-to-day lives, especially that of truckers, the transporter type the LogAware company targeted. 

In filling in the gaps for our preliminary research, I looked into second-hand research, including YouTube vlogs, to get deeper insights on truckers' day-to-day lives. It made better use of our interview time by allowing us to ask more more pointed questions about how our app could fit in their workday and routine.

Journey Map (trucker).jpg

A rudimentary "user journey" from second-hand research used formulate more targeted and precise questions for user interviews. 

Ideating Our Users

The two-app nature of our product  (a necessary repeated theme throughout this project )  meant that we actually had to do two routes of parallel user research at once, one for each user type. Therefore, we came up with two archetypes of our target users, with two hypothetical user journeys, one for each archetype. 

P5 trucker archetype resize.jpg
P5 ACTUAL trucker journey resize.jpg
P5 tracker archetype resize.jpg
P5 tracker user journey resize.jpg

With this research in mind, we affirmed and revised our foundational goal for the LogTrack platform:

How might we facilitate access to tracking information and documentation, including shipment and driver location, consistently across multiple avenues?
Our research allowed us to affirm LogTrack's value to the space as an approachable service with less walled-off access due to marketplace-tied or company-specific access, bringing together tools that are often not seen together on the same platform.

We also affirmed the usefulness of the LogAware team's desired functionalities in their product, and decided upon which tasks we should focus on prototyping to deliver a minimum viable product. 

Designing A Shippable App

Between our research and the client's features based on their own experience, our team was able to quickly parse what features we wanted to include in the apps, both necessary to the core tasks and secondary in order for these tasks to be completed with ease and clarity. We worked through several rounds of design studios, including one session with our client, and we used feature ideation techniques such as prioritization matrices to finalize what we wished to include. 

In the end, we completed a mid-fidelity prototype and three high-fidelity prototypes, the last of which was eventually delivered to the client.

p5 integral features.JPG
Trucker Tracker Tasks

Because of the peculiar purpose of the platform, our team decided the best way to build out would be to identify the tasks (rather than features alone) that would need to happen between the two apps:


  • View transporter information and on-duty status

  • Live transporter tracking for active jobs

  • Document upload, storage, and sharing

  • Geofenced notifications

This meant, basically, we had to build both ends of each feature, and therefore build each feature twice, with entirely different functions on each app. Further, these features needed to follow a flow that ensured consistent touchpoints between the two apps. Our teams coordinated together in the process of building each app to ensure the tasks featured the proper touchstones appropriate to each app's purpose. 

Testing For Users' Long Haul

Given LogTrack is a user-first platform, once we finished each round of design (one mid-fidelity, three pre-testing high-fidelity) it was fitting to focus our design's iteration upon rigorous user testing (or at least, rigorous relative to our collective boot camp experience so far).


We managed three rounds with 25 users and emerged with results that we quickly learned from. 

Our mobile app saw mostly-consistent improvements with each round of iterations. We were able to simplify flows by allowing copy to match the desired tasks at hand. For instance, we moved job alerts from messaging to a "Jobs" tab, then made this the default window upon opening the app.

Rocky Roads Abound

While mobile went well, once we got to trying to improve our desktop app, things went awry for a brief moment. Due to the scale of the concepts and details that we realized slipped between the cracks, testing came out with less consistent results.

In particular, perfecting our geofencing process became a challenge as we realized users want more transparent control over the process. In the same round we attempted to add these features, we came face-to-face with an odd prototype flow -specifically, cutting out a quick option to geofence due to faulty Figma execution - that clashed with our time constraints before testing.

The tests came back with consistent failure or at least confusion with the feature, and we quickly rushed back in to not only fix this, but flesh out this flow more fully before full product hand-off. Some guerilla tests with users, which we lacked time to make official, proved this revisit to be valuable: possibly more so than if we'd had the intended concept executed. 

geofencing changes.png

Roads Bygone

We believe that if we had more time, we could have fleshed out more features in the ways we wanted and accomplished even more user testing. A lot of our design and project decisions hinged on the best solutions given the time constraints and wanting to move the project forward, and we weren't able to fully step into features such as messaging and Android adaptation.


Regardless, our UX/UI team is more than pleased with the final results, and so was the LogAware staff upon our presentation, after which we handed off our prototype, project report, and specification documents.  We're sure that with this foundation for an SaaS product, the team can help disrupt the logistics industry a little bit where it's needed.

  • Client & business consultation

  • Group facilitation 

  • Consensus activities 

  • Design/concept convergence 

  • Task prioritization 

  • Time management 

  • Report drafting 

  • Presentation construction 

  • Public speaking 

  • User interviewing 

  • Business analysis

  • Second-hand research 

  • Archetypes, personas & user journeys 

  • Design studio 

  • Service blueprints 

  • User flows 

  • Iterative design 

  • Mockup design 

  • Prototype construction 

  • Design sketching (paper & whiteboard) 

  • Figma 

  • Google Drive Suite 

  • Keynote 

  • Zoom 

  • Slack 

Skills Utilized

bottom of page