In enterprise agriculture, timing and trust are non-negotiable. One agritech platform needed to streamline how growers executed field prescriptions—planting, fertilization, and crop protection plans—across two independent systems: its own software and an external equipment management platform.
The technical ask seemed straightforward: make it easier for users to send prescriptions from System A to System B. But the real UX issue wasn’t functional—it was cognitive.
Were these systems linked? Or was the platform simply sending a static file?
And if it was just sending, how do we help users avoid assuming that edits in one system will automatically carry over?
This wasn't a hypothetical UX problem. If a grower updated a prescription but failed to resend it, they could unknowingly execute an outdated plan—applying the wrong chemical, seeding at the wrong rate, or introducing safety and compliance risks. And in agriculture, there’s no “undo” once you’ve rolled out the equipment.
