When the Problem is the Problem

Recently I’ve been observing a government agency charged with improving the environmental outcomes of a waterway that flows through an agricultural district. The agency is filled with technical experts who have the job of writing ‘The Plan’, the aim of which is to ensure sufficient environmental flows.

In this context, the task for the Agency was defined in terms of how much water do we need to get back into the river system in order to ensure lasting environmental outcomes?

That definition of ‘the problem’ makes sense, but might other key stakeholders see the problem differently?

If I am an irrigator whose livelihood and lifestyle is based on extraction of water, how might I see this framing of the problem? If I’m the Mayor of a local agricultural community what might I fear? It is clear that the problem is at real risk of being interpreted by water users as “how much water will the government take from me, my farm and my community?”

That’s a pretty scary question to ponder and, and not one likely to inspire positive collaboration.

This experience illustrates how the framing of the problem can be the problem. What to do? Imagine if the water planning problem was defined as more of a dilemma: How do we ensure a healthy river supporting a thriving agricultural sector and vibrant regional communities? Now that’s a different problem, and one which invites people in rather than scares them away. And imagine if all stakeholders came together to create this definition of the dilemma that they all share. That is how to build commitment to work together.

Co-defining dilemmas can be a very powerful part of any attempt to tackle complex water management challenges. By doing this together you can ensure that your problem doesn’t become the problem. If you want to know more about where that task sits in the overall collaborative journey, you might take a look at our collaborative pathway here.