Participatory Network Analysis

netmap.jpg

Social network analysis is often criticized for being too static, too far removed from the actors involved and too dependent on expert driven analysis.  Often the participants involved in a social network analysis data collection effort never get to see the final outcome.

Participatory network analysis, on the other hand, is a highly participatory approach to mapping out the actors, types of linkages and their level of influence on a problem or situation which you and your team are facing.  It is a workshop type approach which is highly visual using paper, markers, colorful sticky notes and a skilled facilitator.  The map which is produced in the end represents the collective understanding of the situation of interest of those involved and therefore it is important to involve stakeholders who may have different perspectives.  The final map produced may also be digitized and there is very user-friendly software developed for this purpose.  Digitizing the maps also deals with the problem of these maps being too static because they can be easily updated as actors change and new linkages are developed.

So, why would you want to engage your team or collaborators in a participatory network analysis exercise?  There could be many reasons including:

·         To understand better a situation you are involved in or which needs improvement to help guide your efforts before you commit too many resources;

·         To get a full picture of all of the actors (individuals or larger entities) who influence the issue or situation at stake;

·         To help you and your team uncover the hidden drivers that propel or hold you back from achieving your goals;

·         To help you and your team better plan and leverage both your formal and informal influence network.

We are about to embark upon a new year with much uncertainty and a rapidly changing landscape. It could be critical for your operations and your team to take out a little time to map out the situation you are facing.  It is usually always a very enlightening experience as the discussions unfold and the map takes shape.  Our individual cognitive abilities do not allow us to picture in a snapshot the many nodes and connections of our networks of interest and it is therefore extremely helpful to visualize this on paper.   When done in collaboration with others, new insights are always revealed and a more complete picture emerges.   

If you are interested in learning more or need a facilitator to help guide you and your team and collaborators through this highly interactive exercise, do not hesitate to contact Kirsten Collins, principal of AdaptivePurpose (www.adaptivepurpose.org) at kbcollins@adaptivepurpose.org.  Kirsten is a certified systems practitioner and evaluation consultant with over 15 years of experience working with a variety of clients including non-profits, NGOs and government.

Comparing Lean Startup and Systems Thinking Frameworks

Systems thinking exists as a way of reevaluating problems in order to create new and effective solutions. Instead of only concentrating on cause-and-effect relationships between actors, it focuses on relationships, boundaries, and feedback to put more emphasis on the wider picture. The breadth of the systems framework is one of its greatest strengths, as systems thinking is used in both the non-profit and for-profit sectors, especially when the problem at hand is complex. Surprisingly, its adoption to date has been limited. This is in part a result of the change-resistant nature of organizations as a whole, but it is also because systems thinking has limited exposure outside of academic circles. However, select elements of systems thinking have been cherry-picked and applied in practice. Specifically, the lean startup method emphasizes some aspects of the systems framework while ignoring others entirely.

The traditional business model often starts with a five-year plan, an initial forecast of the market, cash flows, and risk. Underlying this plan is the assumption that all of these categories can be anticipated and projected for years into the future. Unfortunately, consumer feedback has no place in this model. In fact, customer reactions are only known with any certainty after large amounts of funding and development have already been poured into a project. Lean startups are different precisely because they use feedback as a tool for developing adaptive business models. At the core of the lean startup method is the minimum viable product, or MVP. These are in a sense prototypes developed with customer input that aim to test the market in order to determine demand. Ideally, the prototypes continue to evolve and are improved at each iteration so that when significant resources are finally invested into the product, the end result will have a much higher chance of success.

Although lean startups are not explicitly systems aware in that for the most part they do not claim to take a systemic approach to product development, their underlying philosophy tells a somewhat different story. Their commitment to customer input evokes the feedback loops found in systems thinking, and the rapid prototyping used in developing MVPs to test the market is similar to the systemic approach to defining boundaries. After all, defining the consumer and the scope of the product is a less theoretical way of determining the actors and boundaries involved in any given system.

However, it is important to recognize that in spite of their similarities the lean startup method is not just applied systems thinking. While lean startups are “aware”, in the sense that they seek to integrate consumer responses with their products, they do not show the same commitment to understanding relationships that characterizes systemic approaches. Evaluating the market and adapting to it are vital to startups interested in using lean methods, but a detailed understanding of the connections between sources of capital or within the general system that they operate in is not. Ultimately, it is important to understand that systems thinking and lean startups rely on compatible frameworks that overlap in some areas but diverge in others.

References:

Ackoff, Russell L. "Why Few Organizations Adopt Systems Thinking." Syst. Res. Systems Research and Behavioral Science 23.5 (2006): 705-08. Wiley Online Library. Web. June 2016.

Blank, Steve. "Why the Lean Start-Up Changes Everything." Harvard Business Review. Harvard Business Publishing, 01 May 2013. Web. 7 July 2016.

Are you Using Systematic or System(ic) Thinking?

Systematic and system(ic) thinking form the basis of two different approaches to problem solving.  System(ic) thinking is concerned with examining the ‘whole’ of a system of interest, while systematic thinking focuses on the parts using a step-by-step, methodical approach.  There is now growing recognition that system(ic) thinking is needed to better address the complex, interrelated, social and environmental challenges we will continue to face in the 21st century.  However, system(ic) thinking capabilities are weak in the west (1)  Why is this? And how can we best combine systematic and system(ic) thinking to develop the solutions our complex global issues? 

Although many of us may have some intuitive appreciation of system(ic) thinking, it is quite weak for many in the west.  This is likely due to the dominance of the ‘Newtonian’, ‘reductionist’ and individualist paradigm in the west, which has shaped our thinking in many ways and influenced how we have structured our society.  The western tradition of schooling has mostly taught us to think systematically, using an orderly, step-by-step approach as dictated by the scientific method.  This is premised on the view that the ‘whole’ of a phenomenon is best understood by examining it parts.  This is good for in depth understanding of the properties of individual elements, and the determination of linear, cause-and-effect relationships.  To understand the ‘whole’ that emerges from the interactions between the individual elements, however, requires system(ic) thinking.    

To build capacity in system(ic) thinking, it could be helpful to raise awareness of the differences between system(ic) and systematic thinking and to recognize that these two approaches need not be mutually exclusive.  Combining systematic with system(ic) thinking, indeed, could be very powerful if done in the right way.

So, how can we best combine system(ic) thinking with the dominant, systematic and linear frameworks (logical frameworks, budgets, performance assessments, etc.) that structure most of our planning, management and evaluation processes? How do we incorporate the complexity of our operational contexts which these frameworks fail to capture?  Can we develop processes to allow for the reflection and learning which system(ic) thinking can facilitate?  What are useful methods and tools? These are questions AdaptivePurpose is exploring with partners and clients and through the emerging community of practice “Complexity&Praxis” which AdaptivePurpose is helping establish. We will have more blog posts on our activities and capacity-building we are doing to help social and environmental change makers build their system(ic) thinking capabilities.

[1] This essay is inspired by and drawn from Ray Ison’s writings for the course TU812 “Managing Systemic Change” at the Open University, UK.  See reference below.

References:

Ison, R. (2010). Systems Practice: How to Act in a Climate-Change World.  The Open University. London, Springer.

What is the Purpose of Feedback?

What is the Purpose of Feedback?

Representing AdaptivePurpose, I attended Feedback Summit 2015 last week held at the Open Gov Hub in Washington DC.  We spent two days discussing feedback and hearing from various organizations on how they are collecting feedback from their stakeholders, beneficiaries, and citizens (the term to be used was a whole other debate).   Everyone there agreed on the importance of collecting feedback and that we need to do a better job across all sectors collecting feedback from those who are impacted by programming interventions.  This seems difficult to argue against, and it certainly seemed obvious to me as an evaluator because collecting feedback is what I do.  It isn’t enough, though, just to collect feedback. What matters is what you do with this feedback? And anyway, what exactly IS feedback in the first place?  These themes were percolating in discussions among the participants, but the focus of the summit was not specifically on the purpose of feedback, rather it appeared narrowly focused on feedback itself.

Read More

What is Adaptive Capacity?

What is Adaptive Capacity?

While adaptive capacity is relatively well understood in natural systems (i.e. biological and genetic diversification, etc.), it remains an elusive concept in the social sphere where there is much talk about adaptation, but no clear understanding of what is required.

Common themes related to adaptive capacity pertain to having flexibility and the ability to adjust to changes (both positive and negative) and to deal with the consequences in a productive way.  Having the ability to instigate change proactively is another common theme.  Adaptive capacity is also closely associated with the ability to learn; to store knowledge and information; to combine different types of knowledge and to access this knowledge, information and expertise when needed.

Read More