In class 11 we raised the importance of contextual realities in development. Contextual factors tend to influence what kind of change is possible and what is not. I suggested that the precise aspects of a context that matter differ across challenges and places, but 4 key focal questions are pretty important in all contexts: 1. How disrupted is the context? 2. How embedded are incumbent ways of doing things? 3. How legitimate are change alternatives? and 4. How is power and agency aligned (behind change or incumbents)?
I suggested that we need a way to assess these contextual realities. But often they are not open to the kind of analysis we do--writing papers, doing political economy analysis, and more. I argued that even the best political economy analysis seldom says anything about politics in a bureaucracy, or the precise limits of capacity in a key ministry, or the organizational struggles that lead to coordination failures. These kinds of realities often 'hide' and are only made visible when they are forced out.
I suggested that one can force these realities to make themselves known by identifying problems that local agents care about and then using these problems as entry points to change and as windows onto contextual realities.
Here is the basic argument I made (blogged about it recently as well):
I stress problems as the entry point for development initiatives. I do this because all development is about change, and theoretically I think change only happens if 4 things fall in line:
1. There is disruption in the context (something is recognized to be going wrong, because of a crisis or some disruption to the stats quo);
2. Those who need to change are willing to question the way they do things already (I say that the 'incumbents are weakened');
3. There is an active search for a real and legitimate 'new' alternative (something that can be done and will be fit to context); and
4. The power of agency is mobilized around the 'new' thing instead of the old ways.
I think that problems help to move one in the right direction on all four dimensions.
First, problems are the basis of disruption (if you can convince people in a context that they have real problems you are essentially revealing the basis of disruption).
Second, an awareness of problems allows discussion about the failures of status quo mechanisms (if you have a problem it means that the incumbents aren't working so well).
Third, a clear problem becomes the basis for an honest and directed search for legitimate and contextually relevant solutions (the test of the solution is 'does it solve the problem?' rather than 'does it look good?').
Finally, problems are key mobilizers of groups and power (coalitions, in particular, are groups of agents mobilized to work together to solve common problems that they can't solve on their own).
I don't think opportunities are as effective in fostering change and hence development. I don't think opportunities disrupt contexts, or create the basis for questioning the status quo (unless you ask why the opportunity is not being taken, which sounds like a problem more than opportunity), or focus the search for contextually relevant solutions (opportunities often come with prepacked solutions that often have no relevance to the context), or mobilize power and agency (indeed, literature shows that powerful agents often tend to disperse around opportunities so that they can privatize potential gains).
Because of this, I strongly believe that local problems MUST be the entry point for development initiatives.
This is not to say that using problems in the development process is easy. You need to have mechanisms to identify problems, construct and deconstruct the problems, refine the problem based on emerging experience, and ensure the problem provides some aspirational goal for action and entry points to start executing change. This is like specifying the shape of a problem and ensuring the shape allows action towards finding and fitting a solution.
How do you shape problems as entry points for change? I discuss two methods:
- You construct problems using data, stories and crisis events: to draw attention to the problem and to gain energy around solving the problem. This is really important because many problems have festered for long periods and have not received the attention one would hope. In the literature, people speak of these as 'conditions' that agents have become used to. These conditions are turned into problems when one actually shows that they need to be dealt with. This is done by constructing the problem. In doing construction, one needs to ensure that the case is made for 'why it matters' to a wide set of stakeholders needed to foster action.
- You deconstruct problems using problem trees, Ishikawa diagrams, and more: When problems have festered for long periods it is often because they are complex and scary--people would rather ignore them than try to address them--or the causes of the problems are disputed. I believe that one needs a strategy to get past this challenge and make the problem a useful entry point--not too large, not too disputed, with lots of entry points for action. I use problem trees to break the problems down and make them useful in this way. I use the '5 whys' to probe the real causes of the problem, and build problem trees with a variety of branches--allowing all the competing explanations space in the discussion. The problem tree deconstructs the problem into manageable sub-problems or causes...allowing structured engagement and a view onto the context.
When constructed and deconstructed in this way, problems allow one to introduce some change into the context--there is a sense of disruption, a critical questioning of incumbents, the start of a discussion about alternatives, and a mobilization of agents seeking change (or at least exploring whether change is needed to solve problems).
In the next couple of classes we explore actual experiences with problem driven change, and how problems have fostered views into complex contexts in places where I and others have worked.
Here is the reading list for the class: Download Problems
And the powerpoint: Download Class12MLD1022014
Here is a video describing the way we work with problems at the Building State Capability program at Harvard: