
Helping Farmers Thrive:
Creating Their Essential App


FarmIQ, Lead Product Designer
Oct 2022 – Jan 2025
App stickiness
32%
far surpassing the 20% SaaS benchmark for exceptional engagement.
App stickiness
17.5%
year-on-year increase.
FarmIQ's mobile app wasn't working for farmers in the field. It was slow, hard to use, and built around a desktop mental model that didn't survive a paddock. Farmers were going back to paper notes in the paddock and re-entering data late at night, often with gaps and inconsistencies.
FarmIQ is a map-based farm management SaaS used by farmers to plan, record, and make decisions across their operations. Farming is high-pressure and hands-on: regulatory obligations, seasonal deadlines, dirty hands, patchy internet, and decisions made mid-paddock. The app needed to match that reality, and it didn't.
I led the redesign of FarmIQ's mobile app and its sister web application, setting direction, building principles, and guiding a team of 3 through a sequence of releases that gave farmers their farm at their fingertips.
App stickiness reached 32.4%, a 17.5% year-on-year increase, far surpassing the 20% SaaS benchmark for exceptional engagement. Mobile closed to within 4% of web. The app went from something farmers struggled with to something they relied on every day.
“
I’m using FarmIQ as I shift the stock through the gate and don’t have to worry about it when getting home.
Chris Hursthouse · Haddington, Hawkes Bay · 220ha lambs and bull-beef

Recording data in the moment, no catching up at night.

Farmers making fast decisions in the field.
My Role
Lead Product Designer, FarmIQ. Led 2 Product Designers and a Graphic Designer. Partnered with PMs, Engineering Leads, Customer Success, and on-farm subject matter experts, from early roadmap planning through to staged releases.
The Situation I Walked Into
When I joined, the IQ app had one feature: a basic mob move record. The legacy Classic app, the one farmers relied on, was being retired. Everything farmers needed had to move to IQ.
The challenge was two-sided. For farmers: the app needed to be simple and fast enough to use in the moment, recording in the paddock rather than catching up at night. For the business: it needed to drive adoption and retention whilst reducing the support burden that came with a fragmented, inconsistent experience.

IQ app when I joined: one feature.

IQ app when I left: 12 recordings, tasks, diary & notifications.

Retiring the classic app (far right).
The Calls I Made
1
Framed the problem at the ecosystem level
We mapped on-farm tasks, off-farm obligations, and the data sources behind both. This surfaced the high-pressure moments (e.g. time-sensitive records, compliance checks) and clarified where one screen could replace three separate steps.
2
Established decision principles for farm-first products
We defined principles like "Time-to-confidence over clicks," "Local first, sync later," and "Show status and consequence together." These guided every design trade-off and anchored cross-functional decisions.
3
Prioritised a small set of essential workflows
Instead of trying to do everything, we selected 3–5 workflows that farmers use constantly under pressure (e.g. quick record capture, in-field map updates, compliance summaries). We sequenced design and delivery by impact x feasibility.
4
Evolved patterns that reduce cognitive load
We introduced a pattern set: context cards that surface the next best action, offline-first inputs with safe-sync and clear conflict resolution, map-centric summaries with immediate drill-down, and record once, reuse everywhere.
5
Embedded continuous validation
I acted as the voice of our customers, making continuous validation a standard part of every project. We ran small, focused research touchpoints with farmers to confirm we were solving the right problems and used their feedback to guide iterations. This kept our work grounded in real on-farm behaviour.
The Solution
The essential app centres on a live, map-anchored home built around how farmers actually work: outdoors, on the move, often with no coverage. Two things are effortless: recording what just happened, and seeing what needs attention now.
Farmers can tap directly on the map or stock list to access fast-path workflows with pre-filled context, location, mob, last state. They record offline and sync safely when coverage returns. The common path is obvious; edge cases are supported without cluttering the main flow.
Over the project lifecycle, the app grew from one recording type to 11, plus full Tasks and Diary features and app notifications. Every release was grounded in field research.

Checking stock in the paddock.

Recording health treatments offline.

On farm exploratory research.

In the paddock observing customers.

Diary: farm-wide view for in-field decisions.

Tasks: highest adoption feature.
The Shift
The Classic app went from carrying the majority of mobile usage to 19%. IQ went to 39%, closing to within 4% of web.


The Outcome
32%
increase in App stickiness
a 17.5% year-on-year increase, far surpassing the 20% SaaS benchmark for exceptional engagement.
38%
of customers now use IQ regularly
just 4% below web, showing mobile has become a core tool for on-farm decision-making.
With conservative measurement, we also saw strong behavioural signals:
Time-to-confidence for key workflows
Rework entries after introducing "record once, reuse everywhere"
Support tickets on released features
Task completion in low/no coverage areas
Customer satisfaction on routine tasks
“
The biggest thing it’s helped me with is just streamlining my day, so that I can use my cellphone doing animal health treatments on the job, as I’m doing it - nothing to do when I get home.
Corey Caseley · Glendonald Station, Wairarapa · 1,000ha sheep

“
Trying to hit a target carcass weight, to have that data right there at your fingertips it’ll help us track those variations in farm practices that then have an effect on the bottom line.
Alistair Bird · The Grange, North Canterbury · 565ha sheep and cattle

“
I’m using FarmIQ as I shift the stock through the gate and don’t have to worry about it when getting home.
Chris Hursthouse · Haddington, Hawkes Bay · 220ha lambs and bull-beef

What I Learned
1
Clarity beats features
Farmers need fewer decisions at the moment of action, not more options.
2
Offline-first must be trusted
Clear sync states and predictable conflict resolution were what got farmers to actually record in the paddock rather than wait until they got home.
3
Principles prevent wasted time
When trade-offs are explicit, teams deliver faster with fewer reworks.

