Talking with a farmer

How do you build empathy with your agricultural technology customers?

Customer Empathy will be well-known to anyone who has heard about design thinking. So too, for that matter, anyone who has attended an Ag Innovations Bootcamp. Customer empathy is fundamental to creating great design that meets people’s needs. So how do you do it?

Empathy or sympathy?

Often “customer empathy” can sound a bit soft and “fluffy”; and rural professionals won’t want us to “empathise” with them, will they?

It’s easy for us to mistake empathy for sympathy. Both words involve understanding.

  • Sympathy involves understanding emotional or physical hardships, and then offering comfort and assurance.
  • Empathy builds personal understanding of what others are feeling, and the ability to put yourself “in their shoes”.

Embrace what you don’t know

Design practitioners we work with exhibit a similarity – they cultivate a “relentless curiosity”.

You’ve experienced this yourself, with someone who took a deep and genuine interest in your work or hobby. They listened attentively and asked thoughtful follow-up questions. They made you feel as though you were the most interesting person on earth!

Too often, when we venture into the field to talk to customers, we try to validate our own thoughts. We are the experts. We ask questions to qualify the customer, and to quantify the value that our solution will offer.

But what if our intended solution is not what the customer needs? What if there is an opportunity for something even better and more interesting?

Prepared questions will help you start a conversation. Deep listening and genuine curiosity will help us learn more than we could imagine.

Many beats one, and one beats many

How many customers do you need to interview? Will one or two be enough?

It would be nice to think so. Interviews take time to arrange. They take a lot of time and energy to carry out, and they often involve much travel. You can’t usually interview agricultural workers on a city street with a clipboard.

If you interview too few people, it can be hard to distinguish the important from the frustration of the hour. We know that diversity is an essential to high performing teams and great decisions. Seeking diverse views will also help you to create better products or services.

Plan for at least five interviews. You should find both commonality and the breadth of variation between your interviewees.  If you’re finding great diversity (or your first interviews don’t fit your early adopter profile), you may need to find more.

If you need to interview that many, should you consider a focus group instead? Could you get a group of customers in a room or on a Skype call and make more progress?

We don’t recommend this.

Focus groups have a different dynamic to one-on-one discussions. They good for uncovering trends and areas of concern. Detailed insights into the jobs your customers are trying to do are less likely to surface.

Will all users share their experiences and frustrations in a focus group? You may only hear personal experiences from the extroverts. There’s also the risk of “group think”. People may agree with well-expressed comments from others, regardless of their personal experience.

Make the effort to interview customers as individuals, or at most in twos.

Go where they are

In our experience, there is some value in bringing farmers or rural professionals into a meeting room or board room. They are less prone to interruption, and you have more wall space for Post-It notes and diagrams.

Yet you miss seeing the actual environment where they work and will use your product or service. You may also miss the environmental influences that affect the tasks they are trying to do.

Being on the farm or in the customer’s work environment allows them to pick up equipment and show you how they use it. They can point and describe the flow of animals, the pressure of people and machines. You can observe the frustration of sunlight on displays.

Most important: when you bring an end user into the boardroom, they become an amateur designer. This might be valuable, but it also becomes easier to talk in general terms. You may map general processes and forget to delve into experience.

Go to where your customers and end users work. You’ll gain richer insights and higher fidelity than you ever could in the boardroom.

Do we really know what’s coming?

One of the questions I am often asked is: “How does farming in NZ compare with the UK”?

Right now I think it’s a slightly loaded question with all the Brexit talk – subsidies and all that. But in reality given the context of the question is usually in the knowledge I head up a UK-based subsidiary of an NZ agri-software business, what many are really asking is: “How will technology change what we are doing, and is NZ ahead of the UK”?

Now this is a harder question to answer. I guess at a high level I would say adoption of technology in the NZ dairy sector is some years ahead of the UK, but equally, there are big advances in UK arable and hort which one might say are further ahead than NZ. One thing I would say is that NZ farmers are, more typically, open to change and innovation and less wedded to the way it is.

But I think there is something bigger going on than simply comparing one country with another. Sure NZ is a focus for our sector just now because of the way it has, in a generation, turned itself into a very globally focused and innovative economy; one that tops the global rankings for ease of doing business (and one that I would say punches well above its weight, and that’s not just the All Blacks!). No. I think we are witnessing the early stages of an utterly transformative period in global agriculture.

And that’s why I ask the question: “Do we really know what’s coming?” By this I mean, how is technology (and maybe digital and data in particular) going to change the sector?

In short, from where I sit, I would say those of us in the tech world do have a good hunch about what’s coming and the potential impact it will have. But I am not at all convinced the “average farmer” (which is a horrid term) does.

To me it is inconceivable that a farming business (whether in the UK or elsewhere) will be in any way competitive without the use of data-driven decision support tools in the future. The level of accuracy and objectivity that data will deliver (and we are seeing this already) simply puts subjective observation in the second tier of good decision making.

That isn’t to say good husbandry and farming experience have no place in the future (of course they do – I know some brilliant, intuitive and innovative farmers) but those who apply that experience with the latest technological tools will become the Premier League while others languish in the lower divisions.

Give me an example I hear you cry? Ok! A couple of weeks ago I sat down with the CEO of an innovative dairy cow data capture company (based in the UK) that is effectively putting Fitbits on cows. The volumes of behavioural data they are collecting from those animals is now substantial. But it’s what they are doing with it that so impressed me.

By using clever algorithms to understand normal and outlier behaviour of animals they are achieving two great things. The first is the ability to provide alerts flagging animals that are not exhibiting typical behaviour. In other words, “go look at those ones, that’s where you should prioritise your time”.

But the second is what really excites me. Who’d have thought that by analysing cow behaviour data it would be possible to identify lameness, mastitis and other disorders days (even weeks) ahead of when the clinical signs might be observed? I don’t care if you are the best herdsman in the world, it is hard to compete with decision support from data that is identifying things well before they are ever observable by the human eye.

This “power” has the potential to transform the way we run our farms. The application of digital technology will not only potentially save time and labour, it will enable better focus on meeting market requirements, predicting and avoiding problems, and increasingly importantly, be able to provide a substantial evidence base to back and improve welfare standards and all sorts of other production areas currently under scrutiny.

But this future is a far cry from where many on our farms sit currently. Sure there are those that are the early adopters, but I think there is a large majority who simply don’t see this massive change coming, or if they do are in denial.

There are many analogies over the years of where technological change has been transformative and where at the time many did not see it coming: Henry Ford and so on. But it’s the sheer scale of change from tech-driven ag that I think we underestimate at our peril.

The upside is that all this talk of agriculture being a high-tech industry that our children and students should be enthused about is not just talk. It is absolutely true. The more we can find demonstrable examples of great (even cool) innovation, the better it will be for our farming sector, not only because we can farm better, but because we can also excite the right people into the industry.

In my 25-plus years in the ag world in the UK and NZ, never have I felt there is a better time and more opportunity for non-farming people to get involved in the industry, whether that’s in agribusiness, science or on the farm.

And if, as I suspect, we see a reasonably aggressive scaling back of direct farm support in the UK (assuming we Brexit!), that could open the door to a new generation of tech-driven farmers, unencumbered by the past and able to deliver from the potential of the land and associated technology alone. They will be the new competition.

Can’t see it coming? The iPhone is only a little over 10 years old. Things will look very different a decade from now in agriculture. That’s really not very far away. Are you on the train or is it leaving without you?

New grass establishment

#EvokeAg – Making the agritech ecosystem visible and discoverable

We recently attended and exhibited at EvokeAg, the new agrifood international technology event specifically for the food and farming community hosted by AgriFutures Australia.

EvokeAg brought together more than 1100 attendees from across the Australian and wider agriculture and agritech industries, including 100+ attendees from New Zealand and a substantial contingent from Israel. The event featured over 100 speakers from 20 countries, but importantly there was opportunity for all participants to share and be involved.

What was big?

Presenters, panels, exhibitors, and discussions covered a wide variety of topics. A few themes emerged:

  • The start-up and investment ecosystem – more about this below;
  • Irrigation and monitoring systems such as Lindsay FieldNet and Wildeye irrigation monitoring;
  • Automation and robotics (Robotics Plus, Yamaha, Bosch, and more);
  • Data collection, analysis, and the application of artificial intelligence. Comments like “Data is the new gold” abounded.

I’m not personally sure that data is the new gold. I think data is more like an ore that needs to be mined, processed, and refined to extract the real gold. Or maybe data is more like electricity – its intrinsic value is established from use, rather than collection.

Its all about the Ecosystem

We think that the biggest impact of EvokeAg is its impact on the agricultural innovation ecosystem. The event brought together a diverse, fragmented, and sometimes vaporous ecosystem of people and organisations and made it concrete and discoverable in the moment. Examples of groups brought together included:

  • Start-ups and new agritechnology players;
  • Investors, incubators and accelerators, and trade partners; and
  • Research and development organisations and funders.

Making connections

A particular genius of this event was the way that conversations and interactions were facilitated.

  • Braindates, facilitated by an app for discovery and bookings, brought together participants with shared interests, making it easy for those who did not know each other to connect.
  • Careful layout of the food stations, with plenty of tables, seats and leaners for eating encouraged fortuitous conversations, as did the set of food trucks outside providing lunch and evening food around a grassy courtyard.
  • A good blend of exhibitors, lounges, and a “start-up alley” encouraged attendees to look around and interact. Brad and I nearly lost count of the number of people who stopped by the Rezare Systems stand, took a seat and had a relaxed discussion.

The challenge for AgriFutures (the organisers of EvokeAg) and the wider industry is how to capitalise on the positive ecosystem effects to drive growth and innovation. The #growAg initiative announced at the conference, along with AusTrade’s Agriculture 4.0 focus should make a big difference. We’ll play our own part as well – continuing the conversations with those who met with us, and offering an Ag Innovations Bootcamp in early June, an in-depth workshop on design and customer engagement in agriculture, suitable for both start-ups and established Australian agribusinesses looking to innovate.

 

Person in field stares at the sky

Three steps to your agritech product vision

You’re creating the future: a product or service that does not yet exist. How do you ensure your team is on the same page? Do you tell them how they will build it? How it will work? Or do you paint the picture of how it will make people’s lives better?

Your investors and partners are the same. Your product vision is the core of your business vision, so you want key people to understand and love it. Still, formalising your product vision seems like another chore in your busy schedule. You might even fear your idea will lose some of its magic in the harsh light of the day.

A clear representation of your vision:

  • Helps you communicate the vision to your team, your partners, and potential investors. You can be confident that you’ve passed on the key elements and not missed anything out.
  • Inspires others! People who believe and buy-in to your vision will go above and beyond the call of duty to make it a reality.

Here are three keys to get you started on composing your agricultural product vision.

Start with the users

Identify who your intended users are and are not. What problems will you solve for them? How much do those problems matter to your intended users? Are you tackling their problems or forcing your own solution?

The Einstellung Effect is a psychological term. It describes how we can fall in to the trap of applying a familiar approach or solution to problems. When all we have is a hammer, everything looks like a nail. This is a great reminder to us to fall in love with problems, not our solutions. Your agritech product vision should describe the problems you want to solve.

Think big

The eventual picture is larger than your first release. Think about what your vision looks like over the next three, five, or even ten years.

At the same time, your first product release (or releases) don’t need to fulfil the entire vision. Break the plan into bite-size chunks that you can achieve and learn from them on the way.

Trace weak signals and trends

Take a view about the way we will solve problems in two to five years. You’re creating the future, so yesterday’s rules may not apply.

I’m not suggesting divorce from reality. Ensure you have time and space to read, research, and test. Seek to understand how people might work in the future, and how your product might contribute. If your product is a service (to some extent all are), how might it fit with the ways your users want to communicate?

Your product vision is not a product specification. It’s not an elevator pitch either. Whether it is a story or bullets in a slide deck, it’s the way you bring your team and partners with you on the journey. It should help them pull together and solve the problems that count.

As your Agritech product vision evolves, there is one more thing to do: communicate relentlessly. Share your vision with your team and your partners. Evolve it based on what you learn.

New call-to-action
Product team (source: iStockPhoto)

5 tactics of an effective agritech product manager

Why are relatively few agritech products achieving adoption at scale when billions of dollars are being invested internationally every year? New start-ups appear almost weekly. And established companies are shifting from small innovations around the edges to major projects that sit at the heart of business plans.

Yet for all this activity, few product ideas seemingly “make it”.

We work with many agricultural companies – start-ups and established organisations – to help them develop smart digital products and services. In our experience, there’s a strong correlation between a business’s approach to product management, and their success in developing meaningful products or services that get used. The choice of product manager, the scope and objectives of their role, and their level of skill and authority, drives the success (or otherwise) of the product or service development.

The CEO or a Project Sponsor may define the overall business outcomes and vision, and project managers may be concerned with product budget and timeline, but the product manager is at once the “voice of the product” to the business, and simultaneously translates the “voice of the customer” to the development team (this part of the role is also called product owner). They decide the detailed problems the team will try to solve, the relative priority of those problems, and when the solution is complete enough to be put into the hands of customers.

Here are five tactics an agritech product manager can use to be more effective in their role:

1.      Allocate your attention

A product manager juggles many tasks. They must understand scope, be able to prioritise effectively, understand how the team is delivering and what is planned. It’s incredibly hard to do this if the product only gets a small time-slice of your attention.

You won’t be able to effectively manage your product by turning up for a fortnightly sprint planning session. Product managers need to be able to spend time with both stakeholders and the development team. They participate in customer interviews, review the product in showcases put on by the development team, and are deeply involved in product planning workshops.

2.      Build stakeholder relationships

New products and services are built at the intersection of customer or user desirability, business viability, and technical feasibility:

  • Does this product solve a real problem for its users, and can they readily get the benefits?
  • Are customers willing to pay for a solution, and is this solution sufficiently “better” that they will switch?
  • Does this product or service meet the objectives and fit the strategic direction of the company?
  • Is there a business model that makes sense for the company and which could be profitable?
  • Can it be built to operate as envisioned, at a cost the company can justify?

Effective product managers really understand the needs of their users and customers – their behaviours and the problems the product is trying to solve. They use observation and interviews to inform their opinions and seek data from the existing tools or products that customers use.

Product managers must also build trust with the business, effectively communicating how the direction and priorities chosen for the product meet the objectives of the business.

3.      Discover, don’t assume

It’s very tempting to build technology products and services the way corporate computer systems were developed in the past: envisage a solution, document it as a set of requirements, and set the development team to work. When the developers and testers are done, roll out the solution (or pass it through to sales and marketing).

Effective product managers know that detailed customer needs are emergent, and so too must be the solution to those needs. They make use of product discovery activities: carrying out interviews, running experiments, and building prototypes. They know that testing an idea by building a prototype and validating that thinking with real users may not only be an order of magnitude quicker and less expensive than building software, it avoids the huge waste of developing robust, performant, tested software that does not address the real problem.

Software and hardware will still need to be built, but continuously using discovery activities to understand and address customer problems reduces the risk of building a great solution to the wrong problems.

4.      Prioritise value

If customer and user problems and the solutions are emergent, how can you effectively manage the work of a development team (or teams)? How do you decide what gets released to customers, and when?

Effective product managers decide what discovery and development tasks are the highest priority to work on at any point in time. They pay great attention to the “product backlog” – the set of problems waiting to be worked on, ideas waiting to be tested, and validated ideas waiting to be turned into production software. They may visualise these using story maps, or as items on a Kanban board.

This is not “project management”, seeking to most efficiently have all the tasks completed on time and within budget. Rather, the product manager is making value-based decisions about which tasks or stories (feature sets) are the most valuable to do now, and which can be deferred (and might never be done if sufficient value can be delivered to customers and the business without them).

Product managers consider value on multiple scales:

  • Which stories deliver the most value to customers and end users?
  • Which stories help the company achieve its objectives (revenue, customer acquisition, or other outcomes)?
  • Which activities must be prioritised for the product development process to be successful (for instance, prioritising a discovery or validation activity that may change the overall shape of the product)?
  • Which essential dependencies must be built for more valuable stories to work?

5.      Release early and often

This may be an agile mantra, but it remains valid. It’s tempting to hold off putting your product into customers hands until it is “complete”. This is especially the case for established companies who worry about reputational risk.

Delaying until the product or service is largely “complete” misses the opportunity to learn how customers choose to use your product or service. They may pay no attention to that wonderful feature you slaved over and be thrilled by other functions. You may discover that the value you expected just isn’t there, and that you need to “pivot” to a different approach. Far better to do this early than wait until the entire budget is spent.

For organisations worried about reputational risk, limited pilots are a useful tool, whether with a subset of staff or a small group of customers. Early adopters may not fully represent your entire eventual market, but carefully chosen they can provide learning and become advocates to your broader market.

Learn More

We use a variety of tools and techniques to support Product Managers in their role, including discovery techniques and activities, dual-track agile (a team working on discovery and a team developing prioritised stories), and flexible scope contracts that focus on value delivery in a time frame rather than a fixed set of requirements.

New call-to-action