Omnitracs is a best-in-class, end-to-end fleet management software & solutions company from the pioneer of commercial vehicle telematics. They develop software for in-cab platforms used by drivers as well as management and anayltics software.
I was the product owner from the UX perspective and was responsible for the finished products look, feel, feature set, and implementation through communication with the development team. I started with user stories, conducted research, created user personas, wireframes, user flows, high fidelity mockups, usability testing, and ultimately controlling the frameworks and technology used to implement the designs.
Developer handoff and Implementation of designs. Most of the current applications at the time were built in Flash, and Omnitracs was beginning a shift into building more modern applications. There was not a single front end developer and most spent their time building and maintaining the backend. Therefore I had to choose the optimal front end frameworks to use in development that allowed for flexibility and reusability without a large learning curve. I also had to find a better way to hand off my designs in sketch to developers could derive the correct information without having to request more information.
The global navigation bar for Omnitracs Service Portal was static, outdated, and did not provide much use or adaptability to the various applications it supported. My task was to design a modern responsive navigation system that provided context and useful global functionality to the end users.
FBI is an analytics platform that provides reporting tools and insight into day-to-day business operations which allows users have a high-level overview with the ability to drill down to more specific information. The current version of the application was built in Flash, was unresponsive, and customers were very unhappy. I was the product owner from the UX side and I was responsible for addressing customer pain points, creating wireframes, user flows, conducting usability testing, creating high fidelity mockups, handing off designs to developers, and helping with implementation including choosing frameworks to use and giving programming demos over skype.
The FBI Dashboard was designed for high customization and provides a high-level view of information important to each manager's role.
The report page was design to simplify the process of running reports on-the-fly. Start by selecting a report template, choose the desired inputs, and tap "Run".
Data focused. The simplistic layout focuses on the data without cluttering the screen with controls. Any operations such as personalization, scheduling, and exporting can be accessed from the top right of the report which, when selected, will slide in the necessary controls.
Always have access to reports run during a session. The report queue is docked at the bottom of the page and expands to show the current reports and their status. If a report is complete, the user can view that report without going back to the report list.
Scheduling reports is a fundamental function of Fleet Business Intelligence. When a user selects to schedule a report, the scheduling options slide in from the right, pushing the report over to center in the remaining space. The small amount of horizontal space and vertical scrolling structure allows for easy adaptability to mobile devices.
Easily see which reports have been scheduled, whether they are currently active, and where the output is going, and make edits to a set schedule. Editing a schedule presents the same scheduling sidebar.
Admins have the ability to set how reporting metrics are calculated. The page makes understanding the the metrics easily by giving dynamic examples of how each input is factored into the result and shows sample output.
After conducting research and creating user personas, the brainstorming process begins on whiteboard with the project manager to map out concepts and fulfill user stories.
Handing off intricate designs to developers is challenging. Even with using a great tool like Zeplin, some UI components need more clarification. I like to include an explanatory document along with my current sprint deliverables, to provide clarity to developers upfront.
