AgriDigital
Cutting the paperwork out of harvest season
YEAR
2023
TIMELINE
3 months
PLATFORM
Desktop
INDUSTRY
Agtech
ROLE
End-to-end design lead, working with Product and Engineering.
SUMMARY
AgriDigital is a grain management platform built to replace paper during one of farming's most demanding seasons
I led the end-to-end design of document attachment which was the first feature to go through a proper product design process at AgriDigital, and one of the most requested by customers. The goal was to let Growers, Site Operators, Brokers and Traders attach and share documents directly within the platform, eliminating the email chains and paper trails that were slowing everyone down at harvest time.
IMPACT
Customers didn't need a manual
Adoption
92% of subscribed organisations used the feature
The vast majority of customers were attaching documents within the first three months of release.
Usability
Zero support tickets since launch
AgriDigital's users are not typically tech-savvy., farmers are working under time pressure during harvest. Zero support contacts is a strong signal the feature got the design right.
Usage
Daily use across all personas since release
Growers, Site Operators, Brokers and Traders all integrated it into their daily workflow, not just power users.
Volume
8,000+ documents attached in 3 months
A sign that document management had been a genuine pain point as customers used it immediately and consistently.
THE PROBLEM
Managing documents meant leaving the platform entirely
Growers, Site Operators, Brokers and Traders were handling contracts, delivery dockets and invoices through email and paper, completely outside AgriDigital. During harvest, when users are creating dozens of records a day under time pressure, this created real friction. Documents got lost, sharing with third parties was slow, and nothing was in one place.
THE CONTEXT
This was the first feature to go through a proper end-to-end design process at AgriDigital
Document attachment had been on customers' wish lists for a long time. This was confirmed by a research survey run before I joined. When I came on board, it became the first project where discovery, testing and stakeholder collaboration were built into the process from the start. Getting it right mattered beyond the feature itself, it would set the tone for how product design would work at AgriDigital going forward.
DESIGNING FOR EVERYONE
One feature, four very different users.
The main risk with this feature was complexity. AgriDigital's users range from Brokers on desktop to Growers in a paddock and during harvest, nobody has time to figure out a new interface. Every decision was made with that in mind: reduce friction, use patterns people already recognise, and make sure nothing about attaching a document requires thinking.
THE SOLUTION
Designed for the field and the office
AgriDigital's users aren't typically tech-savvy and during harvest, they don't have time to figure out a new interface.
A field worth fighting for.
Engineering proposed removing the document type dropdown to simplify the build. I pushed back because without it, we'd have no structured way to understand what kinds of documents users were actually attaching. That data would be essential for iterating on the feature later. The field stayed in.
USER TESTING
Most of it worked, one thing didn't
I ran remote usability testing with a small group of users across different personas.
👍🏻
5 out of 6 scenarios passed
Users could find the upload functionality without guidance, attach files, manage document types, and share attachments.
👎🏻
One scenario needed more design work
Users couldn't intuitively find where to view and download attached documents from the artefact view.
That was redesigned before release, not after.
THE OUTCOME
A feature that fits naturally into how people already work.
During creation
the feature as part of a form, showing it's embedded in the existing workflow rather than bolted on
After completion
the standalone page showing users can keep managing documents even once an artefact is done
At a glance
the table view with the attachment icon, showing the feature is visible without opening each record
RELEASE
Shipped to beta first, then to everyone
The feature launched to a beta group before full release, giving us two weeks to monitor real usage across different personas and use cases. Users were surveyed at the end of the beta period.
“This feature is amazing! It surprisingly fits absolutely perfectly with what we have been talking about in my office”
“This feature is great and we’re using it constantly - thank you”
From there it rolled out to all users, and has been used daily ever since.
AgriDigital
Cutting the paperwork out of harvest season
YEAR
2023
TIMELINE
3 months
PLATFORM
Desktop
INDUSTRY
Agtech
ROLE
End-to-end design lead, working with Product and Engineering.
SUMMARY
AgriDigital is a grain management platform built to replace paper during one of farming's most demanding seasons
I led the end-to-end design of document attachment which was the first feature to go through a proper product design process at AgriDigital, and one of the most requested by customers. The goal was to let Growers, Site Operators, Brokers and Traders attach and share documents directly within the platform, eliminating the email chains and paper trails that were slowing everyone down at harvest time.
IMPACT
Customers didn't need a manual
Adoption
92% of subscribed organisations used the feature
The vast majority of customers were attaching documents within the first three months of release.
Usability
Zero support tickets since launch
AgriDigital's users are not typically tech-savvy., farmers are working under time pressure during harvest. Zero support contacts is a strong signal the feature got the design right.
Usage
Daily use across all personas since release
Growers, Site Operators, Brokers and Traders all integrated it into their daily workflow, not just power users.
Volume
8,000+ documents attached in 3 months
A sign that document management had been a genuine pain point as customers used it immediately and consistently.
THE PROBLEM
Managing documents meant leaving the platform entirely
Growers, Site Operators, Brokers and Traders were handling contracts, delivery dockets and invoices through email and paper, completely outside AgriDigital. During harvest, when users are creating dozens of records a day under time pressure, this created real friction. Documents got lost, sharing with third parties was slow, and nothing was in one place.
THE CONTEXT
This was the first feature to go through a proper end-to-end design process at AgriDigital
Document attachment had been on customers' wish lists for a long time. This was confirmed by a research survey run before I joined. When I came on board, it became the first project where discovery, testing and stakeholder collaboration were built into the process from the start. Getting it right mattered beyond the feature itself, it would set the tone for how product design would work at AgriDigital going forward.
DESIGNING FOR EVERYONE
One feature, four very different users.
The main risk with this feature was complexity. AgriDigital's users range from Brokers on desktop to Growers in a paddock and during harvest, nobody has time to figure out a new interface. Every decision was made with that in mind: reduce friction, use patterns people already recognise, and make sure nothing about attaching a document requires thinking.
THE SOLUTION
Designed for the field and the office
AgriDigital's users aren't typically tech-savvy and during harvest, they don't have time to figure out a new interface.
A field worth fighting for.
Engineering proposed removing the document type dropdown to simplify the build. I pushed back because without it, we'd have no structured way to understand what kinds of documents users were actually attaching. That data would be essential for iterating on the feature later. The field stayed in.
USER TESTING
Most of it worked, one thing didn't
I ran remote usability testing with a small group of users across different personas.
👍🏻
5 out of 6 scenarios passed
Users could find the upload functionality without guidance, attach files, manage document types, and share attachments.
👎🏻
One scenario needed more design work
Users couldn't intuitively find where to view and download attached documents from the artefact view.
That was redesigned before release, not after.
THE OUTCOME
A feature that fits naturally into how people already work.
During creation
the feature as part of a form, showing it's embedded in the existing workflow rather than bolted on
After completion
the standalone page showing users can keep managing documents even once an artefact is done
At a glance
the table view with the attachment icon, showing the feature is visible without opening each record
RELEASE
Shipped to beta first, then to everyone
The feature launched to a beta group before full release, giving us two weeks to monitor real usage across different personas and use cases. Users were surveyed at the end of the beta period.
“This feature is amazing! It surprisingly fits absolutely perfectly with what we have been talking about in my office”
“This feature is great and we’re using it constantly - thank you”
From there it rolled out to all users, and has been used daily ever since.
AgriDigital
Cutting the paperwork out of harvest season
YEAR
2023
TIMELINE
3 months
PLATFORM
Desktop
INDUSTRY
Agtech
ROLE
End-to-end design lead, working with Product and Engineering.
SUMMARY
AgriDigital is a grain management platform built to replace paper during one of farming's most demanding seasons
I led the end-to-end design of document attachment which was the first feature to go through a proper product design process at AgriDigital, and one of the most requested by customers. The goal was to let Growers, Site Operators, Brokers and Traders attach and share documents directly within the platform, eliminating the email chains and paper trails that were slowing everyone down at harvest time.
IMPACT
Customers didn't need a manual
Adoption
92% of subscribed organisations used the feature
The vast majority of customers were attaching documents within the first three months of release.
Usability
Zero support tickets since launch
AgriDigital's users are not typically tech-savvy., farmers are working under time pressure during harvest. Zero support contacts is a strong signal the feature got the design right.
Usage
Daily use across all personas since release
Growers, Site Operators, Brokers and Traders all integrated it into their daily workflow, not just power users.
Volume
8,000+ documents attached in 3 months
A sign that document management had been a genuine pain point as customers used it immediately and consistently.
THE PROBLEM
Managing documents meant leaving the platform entirely
Growers, Site Operators, Brokers and Traders were handling contracts, delivery dockets and invoices through email and paper, completely outside AgriDigital. During harvest, when users are creating dozens of records a day under time pressure, this created real friction. Documents got lost, sharing with third parties was slow, and nothing was in one place.
THE CONTEXT
This was the first feature to go through a proper end-to-end design process at AgriDigital
Document attachment had been on customers' wish lists for a long time. This was confirmed by a research survey run before I joined. When I came on board, it became the first project where discovery, testing and stakeholder collaboration were built into the process from the start. Getting it right mattered beyond the feature itself, it would set the tone for how product design would work at AgriDigital going forward.
DESIGNING FOR EVERYONE
One feature, four very different users.
The main risk with this feature was complexity. AgriDigital's users range from Brokers on desktop to Growers in a paddock and during harvest, nobody has time to figure out a new interface. Every decision was made with that in mind: reduce friction, use patterns people already recognise, and make sure nothing about attaching a document requires thinking.
THE SOLUTION
Designed for the field and the office
AgriDigital's users aren't typically tech-savvy and during harvest, they don't have time to figure out a new interface.
A field worth fighting for.
Engineering proposed removing the document type dropdown to simplify the build. I pushed back because without it, we'd have no structured way to understand what kinds of documents users were actually attaching. That data would be essential for iterating on the feature later. The field stayed in.
USER TESTING
Most of it worked, one thing didn't
I ran remote usability testing with a small group of users across different personas.
👍🏻
5 out of 6 scenarios passed
Users could find the upload functionality without guidance, attach files, manage document types, and share attachments.
👎🏻
One scenario needed more design work
Users couldn't intuitively find where to view and download attached documents from the artefact view.
That was redesigned before release, not after.
THE OUTCOME
A feature that fits naturally into how people already work.
During creation
the feature as part of a form, showing it's embedded in the existing workflow rather than bolted on
After completion
the standalone page showing users can keep managing documents even once an artefact is done
At a glance
the table view with the attachment icon, showing the feature is visible without opening each record
RELEASE
Shipped to beta first, then to everyone
The feature launched to a beta group before full release, giving us two weeks to monitor real usage across different personas and use cases. Users were surveyed at the end of the beta period.
“This feature is amazing! It surprisingly fits absolutely perfectly with what we have been talking about in my office”
“This feature is great and we’re using it constantly - thank you”
From there it rolled out to all users, and has been used daily ever since.