Technology in Farming & requirements for on-boarding farmers to your agtech solution - BY: John Buju
Underlying this development is the boon of the huge amount of data that a farm now generates. Like every other human being, farmers do book keeping, are active online, and use smartphones. They use such tools to solve problems on the farm, and by doing so, they’re generating data. There is also farm machinery, loaded with sensors generating lots of data. By combining such farm operations data with other data repositories, like open satellite data on water tables, precipitation, and nutrition data from the feed manufacturer, etc, data can be combined into useful applications that can help with farm management.
Despite the opportunity for the developer to build valuable solutions, there are also barriers that significantly obstruct adoption of digital solutions for farm management. An important barrier is created by technology solutions imposing certain implicit requirements regarding a farmer’s level of data saviness, to collect, organize, and distribute data. Even farmers who do understand the value of data management, generally don’t use computer or web-based tools.
The transfer of farm management practice to an online environment, is hardly seamless, and this transfer problem is a problem for many companies and startups that are developing services in this space. More often than not, I see solutions being launched that are at quite a distance from the kind of tech usability that a farmer can muster.
A Thinking Model
A rule of thumb for nailing product design is that you can best meet your farmers where they are. To help position where the farmers you’re targeting are in terms of tech saviness, I’ve developed a model form making farm data personas. This model is presented below.
For each step there are a variety of options available to the farmer to handle their data. These options range from low-tech solutions, like paper-based record keeping, to high-tech solutions, like cloud computing storage, and SaaS (Software as a Service) for analyzing farm performance. (These can of course be adapted to whatever fits the sliding technology scale that matches your own circumstances.)
Next to profiling farmers according to their tech saviness, this model can also be used to indicate what level your solution currently requires your farmers to be in. By comparing these parameters, you can start to see, and understand the gaps.
Making technology appropriate.
Lets take an example of a solution of herd management for dairy farmers. Say you have an idea for a SaaS analysis solution, to offer online software for dairy herd management. You will need to figure out a way to connect all the necessary data flows to feed your analytical solution. You want farmers to somehow get their cows to the cloud for analyzing herd performance, and you’re going to need a way to get them to digitize their input.
In the case that your farmers are still working with paper-based recording keeping, which is likely, you’re probably going to have to physically on-board their data.
Once you’ve identified this gap, the question then becomes what intermediate steps you can build into your solution to take farmers up the tech ladder. Can you redesign your product to include a learning curve, which will take your farmers on a journey to comprehend your solution, take control, and eventually make it fully usable?
The upshot is that agtech initiatives will likely need to design for the farmer’s learning curve. Adoption for agtech solutions will be slower, and acquisition costs relatively high compared to other tech industries. This is something startups in this space will spend of lot of time on, and their investors (if you have any) will need to provide for the adequate runway.
—–
Comments
Post a Comment