Allowing construction companies to surface employee data (Work in Progress)

Tread is a Canadian start-up SaaS platform focusing on moving construction materials easier, faster and more profitably. One solution of the software is its Insights page, that reports on the performance of different aspects of the company. In this feature, we change the way that this data is visualized to be more usable, approachable, and understandable.
  • Product Design
  • 2 Months
  • February – March 2021

Driver Insights

User Problem

Throughout user interviews, support calls and general feedback, many users have commented about their frustrations of not having a clear and easy way to surface a truck driver's historical data.

The use-cases for this feature varies from dispute resolution, speeding tickets and MOT (Ministry of Transportation) guidelines.
Research and questions based off of past user-interviews

Business Problem

Tread uses a Looker integration to visualize Insights data. However, it ends up being a large financial investment with some technological constraints. This feature would allow our team to move away from the integration to give us more freedom.

Pain points with Looker include long load-times, data constraints (there is a maximum amount of data-points it will work with) and general design restrictions.
Current Insights page in Tread using Looker Integration


My first step of ideation was creating low-fidelity wireframes on Invision Freehand to help establish potential features from previous user feedback. At this moment, the features of this product were not set in stone, so we wanted to gain more feedback during our user-testing. Therefore, the wireframes and first round of concepts were very speculative.
Invision Freehand sketches

User Flows

For the first round of user-testing, I created 3 tasks that testers needed to go through: (1) How would you filter to see Craig Landry's driver profile? (2) How would you filter to yesterday's date and see data between 11:00am – 1:00pm (3) How would you see the drivers location at exactly 12:25pm?
Ideal Flow for Task 1: How would you filter to see Craig Landry's driver profile?
Ideal Flow for Task 2: How would you filter to yesterday's date and see data between 11:00am – 1:00pm

User Testing

We tested this feature with three Tread users: two of them are frequent users of the Insights page and one who is unfamiliar with it (as they do not pay for the Insights add-on). As well, each user had a different role in the industry, providing us with different perspectives and use-cases for this feature.
Categorizing the user feedback (each user is in a different post-it colour)

After categorizing the feedback, I created a table that outlines pain-points with the current user experience, user interface, and potential back-end features that could be scoped in. These were shown to the Product Managers and Engineering Team to reevaluate any of our Feature Requirements.
List of user-feedback and feature requests.

Solutioning and Setting the Vision

During our second iteration, our focus was talking with Engineers to understand the scale of creating the feature in a impactful yet efficient manner. With this, we created a series of requirements that will be included in this version:
Feature requirements written by the Project Manager

Final Feature

For the final design, I implemented these revised features, as well as created a new design system for data-visualizations that Tread didn't have before. The Driver Insights lives within the Map page on Tread. It includes details on the drivers route, speeding information, and the project data.

Next →