Niches and mainstreams in our food system

Whenever I attend gatherings in my line of work that address the question how to change the food system for the better, I’m confronted with the recurring pattern of a split in the discussion between niches, developing alternative propositions, and the mainstream, working on improvement of the existing ones. Entrepreneurs that find the space to tinker in a niche are looked upon by the mainstream with slight amusement and bemusement at just how alien that class of innovation is to them. Real change is achieved by a big system making big shifts. Not by gullible projects with cuddly eccentrics, right?

What I would like to point out here is that mainstream forgets itself in this stance. In the mainstream everybody is a good manager, we work by certain protocol towards certain expected outcomes. Everybody participates according to those values. A nested system network, where assembly of the food components fit snuggly like a Matryoshka doll. The emphasis is on execution and optimization of the known business model, not the search for alternative ones. Over longer periods of environmental constants they are unbeatable: a big, efficient, influential, even dominating community.

But when key supports in the business environment start changing, then such value systems become vulnerable. And change is happening, and the rate of it happening is accelerating; whether mainstream likes it or not. The graph below depicts just how fast new technologies diffuse through society. This alone is change enough to radically alter the landscape in which business is done.

Adoption_diffusion_technology

The real question under such turbulence is whether the mainstream is still delivering what the customer wants. Is it still in tune with the customer, and with the empowerment that technological change is providing her? Or is it rather suppressing pressures on the system, for instance, controlling for animal welfare issues by getting activists to shut up, or by downplaying horse meat in beef lasagna is an anomaly? Is the mainstream still in tune? Or, is it practicing elitist technocratic infantilization of the customer, who currently has no real alternative on how to purchase food products?

The reality of our environmental dynamics, combined with the attitude of “how everybody is a good manager”, can now take a whole system down the drain with the same efficiency and speed. One day you might be member of a seemingly robust food security delivery mechanism. The next day, some niche-guy will have figured out how to hack a whole market through empowering customer choice, by actually delivering what costumers really prefer for their basic food requirements. And, trust me, customers simply don’t care if that implies leaving behind a whole industry for another one that provides a better alternative.

My position is that members of the mainstream food network need to revalue the niche. Revaluing the niche, means learning about how what the niche is doing, might apply to the mainstream, instead of doing the opposite. The niche is likely to provide an insanely rich source of actionable customer insights, that the monolith execution network will never discover.

The dichotomy in our discussion is dangerously artificial. It is created by fear, leading to scathing of the tinkerers, with complete disregard of the fact that we’re dealing with competing business organisms in the same ecosystem. What we should have is inspiration leading to the embrace, crediting the tinkerer with the insights they can provide about what factually works and what doesn’t under new circumstances. And, it all starts by treating our tinkerers in the food system in a more inclusive way, not exclusive. As a well known Blankian phrase in Silicon Valley goes:

What do we call a failed entrepreneur? Experienced!

I want to see more of that attitude in food and agriculture.

Your priority is our focus

Over the past few months I have been studying design approaches applied to sustainable development projects in agricultural value chains in developing countries through the lens of human centered design. Here’s a brief insight into my first experience of one of the principals of the human centered design process (exploring and understanding the problem first, before even starting to contemplate potential solutions) and a description of how it has enriched my own understanding of a thematic area in which I used to consider myself to be knowledgeable

What it takes to search for your problem

  • prioritize understanding before anything else. This means creating space (freedom to think, talk, play, and move around) for working on the prime objective of understanding
  • observe in a lateral sense to discover what significance a problem has, and how it is defined and expressed by the users in their own voice.
  • all discussion which takes place with your users has a topic in mind, but no explicit purpose. Voicing purpose in problem exploration will likely lead to crucial assumptions in your perceptions remaining undefined and thus unvalidated (expert’s bias)
  • refrain from doing any analysis on your observations. They will blind your inquiry into the problem. Only analyze after repetitive patterns start appearing in your observations.

The general feeling I got from this method of inquiry was that of being a total slacker, based on a self-invoked perception of not being productive. But the trick is to not let that feeling permit you to cut short the exploration of the problem area by attempting to nail things down too early. Explore until patterns start repeating and you’re likely to stumble on insights that your expertise has never revealed to you before.

The pains of staying away from describing or even conceiving the solution, whilst discovering the problem

Expertise encourages a tendency to look smart by exposing knowledge about a problem area, voiced in the form of solutions. But:

  • your conception of solutions is a mirage. Despite your knowledgeable background, solutions actually mean nothing until the user starts voicing tentative parameters for a solution herself.
  • signaling solutions instigates memes, and the problem definition starts leading its own life
  • voicing solutions is an implicit promise to deliver a specific solution. You are likely to commit to delivering something that in the end won’t address the real problem at hand, if any problem at all.

The challenge I faced here was to drop my fear of discrediting my skills and competencies by not prescribing what should be done. You need to realize that the pay-off for your efforts (recognition, fame, happy responses) lies further on in the innovation process when you are able to define actionable insights. As with the problem search, tendencies towards immediate gratification by proposing solutions will increase the likelihood of introducing concepts that will not lead to feasible, viable nor desirable outcomes.

The reward
The pains of feeling incompetent, and not playing the expertise card need to be seen as an investment. The leverage that this investment provides will allow you to wield a significant force of creativity: focus, as in

  • prototyping solutions with the right focus on a demarcated innovation space -> your users and their problems. This is where you can try out all your creative solution concepts
  • using all relevant capacities and resources to address the need of the user
  • users instantly understanding the intent of your solution, and intuitively tinkering and helping in your process of prototyping because they are empowered.
  • instant recognition of signals of adoption or rejection with users.

The human centered design process thus ensures that your priority remains our focus, throughout.