Yara is the world’s leading crop nutrition company, and a provider of environmental and agricultural solutions.
Overview
At the time, our product suite consisted of three distinct apps, and I was a UX designer on YaraConnect, an app where farmers and retailers exchanged services.
There were hundreds of screens spread across dozens of folders and Figma projects at any point in time, and that made onboarding very interesting – given that the design system was in the middle of a revamp at the time.
My Role
I worked closely with other designers and a design manager, while collaborating with design systems, engineering and design ops. A high-level breakdown of my work included:
- Sprints and ideation for YaraConnect and Yarabodega.
- UX audit for the design systems team.
- Design documentation and standardization for YaraConnect.
Documentation Approach
The existing system hierarchy consisted of features which differed by country, and lived in one of 3 folders: Live, WIP, and archives. The immediate goal was to
- Improve project categorization and identify files faster
- Reduce clutter, streamline communication and handovers
- Maintain a trustworthy reference for all of our work
UX Audit
I started by going through every page on every feature on the live app and collected screenshots of everything, recording the most critical user flows and processes and testing critical user flows, touchpoints for consistency against each version of the live app.
All inconsistencies were documented and fixed, and we collaborated with design system team on component creation and updates.
We collaborated with engineering on fixes and with design system team on documentation, component creation and updates.
"George impressed both myself and the client with a portfolio that demonstrated thoughtful design decisions, strategic thinking, and a commitment to creating intuitive, user-friendly experiences."
Harshit Malik
UX Design
Features were still being added and updated during the revamp, including assisted order flows, stock management and more.
Outcome
By the time this was complete, we had a single source of truth, an intuitive organization of folders, projects and countries for the product teams, and a clear course of action for moving forward.
My goal all through this was to reduce project start-up time, minimize onboarding complexity, and improve cross-functional communication. We shipped several features in 4 months, and streamlined documentation for 14 features across 9 countries.
