Overview of the PIPA process.

Participatory Impact Pathways Analysis (PIPA) is an project management approach in which the participants in a project (project and program are used synonymously from now on), including project staff, key stakeholders and the ultimate beneficiaries, together co-construct their program theory.[1]

Overview[edit | edit source]

The PIPA theory describes plausible impact pathways by which project outputs are used by others to achieve a chain of outcomes leading to a contribution to eventual impact on social, environmental or economic conditions. Impact pathways are a type of logic model, that is, they constitute a model that describes the logic of what the project will do, is doing, or what it did.

PIPA helps workshop participants surface, discuss and write down their assumptions and theories about how their project activities and outputs could eventually contribute to desired goals such as poverty reduction. The description of these assumptions and theories is a description of the project’s (or program’s) impact pathways. PIPA has helped workshop participants with the following:

  • Clarify and communicate their own project’s logic of intervention and its potential for achieving impact
  • Understand other projects and identify areas for collaboration
  • Generate a feeling of common purpose and better programmatic integration
  • Produce an impact narrative describing the project's intervention logic
  • Produce a framework for subsequent monitoring and evaluation

History[edit | edit source]

Participatory Impact Pathways Analysis (PIPA) was first used in a workshop in January 2006 in Ghana, with seven projects funded by the "Challenge Program on Water and Food".[2] Nine PIPA workshops have been held since then for 46 projects. Researchers from the International Center for Tropical Agriculture[3] are developing PIPA.

PIPA developed from innovation histories[4] and work carried out by the Institutional Learning and Change Initiative.[5]] A paper describing the approach has been accepted for publication in the Canadian Journal of Program Evaluation.

PIPA topics[edit | edit source]

PIPA projects[edit | edit source]

PIPA is useful when two or more projects in the same program wish to better integrate. At least two people for each project should attend, preferably the project leader and someone else who knows the project and has time and inclination to follow up on what comes out of the workshop. PIPA also works well when one project wishes to build-up common understanding and commitment from its stakeholders. In this case, two or more representatives from each important stakeholder group should attend.

PIPA process[edit | edit source]

PIPA can be used at the beginning of a project, in the middle or at the end as way of documenting and learning from the project. PIPA describes project (or program) impact pathways in two ways: (i) causal chains of activities, outputs and outcomes through which a project is expected to achieve its purpose and goal; and (ii) networks of evolving relationships between project implementing organizations, stakeholders and ultimate beneficiaries that are necessary to achieve the goal. The workshop process, shown in the diagram, develops the two perspectives in turn and then integrates them.

PIPA Workshop[edit | edit source]

Drawing a project's network in a PIPA workshop

The workshop begins with participants developing a problem tree that links the project goal framed in terms of a challenge or problem to what the project is actually going to do. The approach used for developing the problem tree is based on work by Renger and Titcombe (2003). The problem tree helps participants clarify the key problems / opportunities their projects are addressing, and the outputs (things others will use) that their projects need to produce. Participants then carry out a visioning exercise, which borrows from appreciative inquiry, to describe project success 2 years after the project finishes, based on the adoption and use of project outputs. These three steps (see diagram) usually take about a day to complete and provide the information needed to describe a causal chain of outcomes needed to achieve project success.

The second part of the workshop involves participants drawing the networks of people and organizations already working in the area in which the project wishes to intervene. They then draw the networks that will be needed to achieve the project vision and identify the differences between the two networks. From these differences they identify the communication and influence strategy that the project will need to employ to be successful. The final step is to integrate the causal chain and the network perspectives by drawing a time line that lists what needs to happen from when the project starts until the vision is achieved.

An optional step, if the information is to be used for monitoring and evaluation, is to discuss how projects can monitor their progress along their impact pathways. This can involve identifying SMART (specific, measurable, attributable, realistic and time bound) indicators to measure expected change, and an approach like most significant change to pick up unexpected ones. A key component of any evaluation plan is that project staff periodically revisit their vision, problem trees and network maps and update them based on what they have learned, identify necessary changes to the time line and document the process.

After the workshop[edit | edit source]

The information from PIPA workshops has been used in a number of ways:

  • At a minimum a clean record is kept of the workshop outputs to provide impact hypotheses for any future evaluation of project impact, and also to help in communicating the project's rationale.
  • The evaluators who run the workshops have worked with project staff to write impact narratives, similar to John Mayne’s (2004) performance stories, that explains the logic of the project intervention in a narrative form. The experience is that the discipline of writing a coherent narrative surfaces assumptions that otherwise remain hidden.
  • The information from the network maps has been processed using social network analysis software Ucinet and NetDraw to produce composite maps that show which CPWF projects are working with which organizations. These maps help the basin coordinators do their job.

See also[edit | edit source]

Further reading[edit | edit source]

  • B; Alvarez et al. (2008). "Participatory Impact Pathways Analysis: A Practical Method for Project Planning and Evaluation". in: ILAC Brief No. 17. The ILAC Initiative, Bioversity.
  • Douthwaite, B. et al. (2003). "Impact Pathway Evaluation: An approach for achieving and attributing impact in complex systems". In: Agricultural Systems 78 pp243-265
  • Douthwaite, B. et al. (2007). "Participatory Impact Pathways Analysis: A Practical Application of Program Theory in Research-for-Development". In: The Canadian Journal of Program Evaluation Vol. 22 No. 2 Pages 127-159.
  • Douthwaite, B. et al. (2007). "Impact pathway evaluation of an integrated Striga hermonthica control project in Northern Nigeria". Agricultural Systems. 92 pp 201-222
  • Mayne, J. 2004. "Reporting on outcomes: setting performance expectations and telling performance stories". In: The Canadian Journal of Program Evaluation Vol. 19 (1) pp. 31-60
  • Renger, R. and Titcomb, A. (2002). "A Three-Step Approach to Teaching Logic Models" In: American Journal of Evaluation. 23: 493-503

External links[edit | edit source]

Notes[edit | edit source]

Discussion[View | Edit]

User:Richard Schulte Cannot get the connected image to work, though the filenames are lined up. Also, is this how I am supposed to go about porting wikipedia pages?

Cookies help us deliver our services. By using our services, you agree to our use of cookies.