AgribusinessProduct designSoftware redesign
After the redesign, users started contacting support to praise the system
CHB has been developing software for more than 30 years. CHB Agro manages the farm from inputs to getting the harvest to market. Tog Lab redesigned the system’s experience, from information architecture to components.
What changed
- Immediate responseAfter launch, users started contacting support to say thanks for the improvement, not to report problems.
- Simpler long processesFlows such as invoicing were broken into clear steps, with well-labeled fields.
- A team ready to carry onCustom components for most of the system, with a visual standard for the next screens.
The challenge
A system that supports the entire farm operation piles up screens and processes over the years. CHB wanted to rethink business opportunities through usability, in a sector of major importance to the country.
Long processes
Lengthy steps, such as issuing invoices, wore out the people who used the system every day.
Poorly distributed information
Scattered fields and information made tasks more complex.
No visual standard
Different screens for similar tasks made the system harder to learn.
What we did
From organizing information to the component library.
- AssessmentUsability best practicesA review of the system from the user’s point of view and against usability best practices.
- ArchitectureStructured informationLogical distribution of information, simplified long processes and accurate labels.
- InterfaceA new visual environmentNew colors, organization and user-centered screens.
- ComponentsA library for what comes nextCustom components to support the CHB team as it continues the project.
What this case study shows
Usability is business too
A system that is easier to use changes the relationship with support and with buyers.
Long processes in clear steps
Breaking up lengthy tasks reduces errors and fatigue for people who use the system every day.
Components ensure continuity
The library let the CHB team follow the new standard on its own.
Has your software grown and become hard to use?
We start with a conversation and, if it makes sense, an assessment with the people who use the system.