This document is structured based on a defined design approach.
Define > Research > Ideate > Prototype > Test and Iterate > Implement > Monitor
Granular is a SaaS enterprise software company building farm management software for farmers. The product covers everything from operations, financials and inventory to reporting and analysis.
Currently, the way in which we are capturing information doesn’t allow us to be as granular as we would like. Every time a user changes equipment or operator or pauses a work order, the information is changed and the previous information is lost. Operations on a farm are fast and changing often and we need the way we capture data to be as well.
Task records introduces the way to do so. Now, every time a user changes equipment, the previous record is closed, and a new one is opened.
For this project, the Granular web application needed to surface Task Records so that they could be entered or edited and Granular could begin to surface data throughout the system more accurately.
There are eight different task types that Granular captures and they all record differently types of information. I created an Excel spreadsheet to document what type of data Granular tracks per task. This allowed me to think of a systematic solution across all records and allowed engineering to create components for each type of data which could be swapped in or out.
The first task type to be implemented across web and mobile was Input Application because it could be completed before planting season started; which is an input application task.
I explored a number of different ways UI’s for each component and reviewed how they looked together. The existing UI of modals in the Granular app surfaces a lot of information and uses a lot of color. My goal was to use more white space and lighten the amount of information overload so that the user could easily navigate this modal and therefore, complete it in less time.
Test and Iterate
I created a research proposal and discussed the designs for an Input Application task to gather feedback and iterate the designs. This helped me to iterate on existing concepts and refine the UI and UX.
The final record introduced a refined UI that utilized white space. The component-ization of data made it easy for engineering to build and update. It also created a system that made it easy to expand to remaining task types.
Ultimately, this project was very successful. Now, the data that is captured in the system happens at a more granular level and recording that information via web is seamless.
One improvement I want to make with the introduction of Records is to remove the concept of a Work Order. Within the hierarchy of information, a Work Order is nothing but an assigned Task and, in my opinion, should be regarded as such. With the introduction of Records, it hold even less meaning because it does not encompass the actual information of what happened on a field.