Where am I?
I’m tired of boring paper work!
The Driver’s Daily log is a part of the routine of every truck driver.
A document that must be filled in every day in order to certify that the activities are being done within the requirements of the American legislation.
The log includes the hours on the road, the hours that the driver slept and many other information.
A document that must be filled in every day in order to certify that the activities are being done within the requirements of the American legislation.
The log includes the hours on the road, the hours that the driver slept and many other information.
The biggest issue with that mechanism is just one: it has to be done with a pen and a paper. An ecological, economical and also practical disaster.
In October 2016, our team at BLOX Software created the ideal solution for transportation companies: a safe and smart digital daily log.
In October 2016, our team at BLOX Software created the ideal solution for transportation companies: a safe and smart digital daily log.
My role
My role in this project was to design two macro interactions:
1. Drivers submitting Daily Logs from an iOS app
2. Managers viewing all driver’s activities from a web version of the software
1. Drivers submitting Daily Logs from an iOS app
2. Managers viewing all driver’s activities from a web version of the software
Problem
How to transform an official document (that can be asked for by a police officer at any given time) into a digital file, without causing any legal implications?
And how to improve the work routine of drivers and managers, without creating more trouble in their communication system?
And how to improve the work routine of drivers and managers, without creating more trouble in their communication system?
Limitations
Federal requirements: The driver’s daily log is a document that follows federal requirements, so we needed to immerse in all the rules of it.
Remote: We had to keep three remote teams on the loop of information and updates.
Remote: We had to keep three remote teams on the loop of information and updates.
Audience
BLOX Software is focused on B2B, transport and logistics companies, mid sized (from 50-100 employees) with a minimal structure of managers and drivers.
Solution
After talking to our audience, we could understand their needs and develop a software that is focused on their communication challenges.
By following the established system (in BLOX ecosystem), drivers access the software from our iOS app (MyBLOX) while managers access it from their computers.
By following the established system (in BLOX ecosystem), drivers access the software from our iOS app (MyBLOX) while managers access it from their computers.
The creation of the spec was shared with our product manager (located in the USA) in direct contact with our shareholders. After validation, I designed the high fidelity mockups with a full participation of our tech lead.
We developed this process of design to align our investor’s expectations, UX needs and our coding capacity, according to our very small dev team.
We developed this process of design to align our investor’s expectations, UX needs and our coding capacity, according to our very small dev team.
We had lots of discussions and cuts on the scope and then finally we got to our MVP, which was developed on iOS and Web (ReactJS). Our main metric to define success of the feature was the amount of daily logs submitted per day.
Conclusion
In this project, it was interesting to notice the team’s evolution, working together in order to develop a complex functionality.
As a group, we were able to adapt ourselves to all the changes occurred along the process and differing of views that we had at the beginning of it.
In the end, we got to a very satisfying result to all of the involved.
As a group, we were able to adapt ourselves to all the changes occurred along the process and differing of views that we had at the beginning of it.
In the end, we got to a very satisfying result to all of the involved.