| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Dokkio Sidebar (from the makers of PBworks) is a Chrome extension that eliminates the need for endless browser tabs. You can search all your online stuff without any extra effort. And Sidebar was #1 on Product Hunt! Check out what people are saying by clicking here.

View
 

Online manual

This version was saved 14 years, 7 months ago View current version     Page history
Saved by PBworks
on January 2, 2008 at 8:08:56 pm
 

Online manual

 

The PIPA Process:

We have used PIPA at the beginning, middle and end of projects as a 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) network maps showing how the actors involved work together, influence each other and influence the general environment for the new knowledge or technology being developed. The workshop process develops the two perspectives in turn and then integrates them through constructing an impact pathways (IP) logic model.

 

Click here for a diagram of the PIPA process.

 

The analysis carried out in constructing the network maps allows the outcomes logic model to more clearly describe the people and organizations who are expected to work together and influence each other to effect the desired change. Traditional logic models, for example logframes, commonly used in the CGIAR system are good at describing causal chains but lack the an actor focus so that they end up containing narrative statements in them without people, for example “rice yields increased by 25% in pilot sites”.

 

We begin the construction of impact pathways in a two-and-a-half day workshop. See here for a brief description of the workshop objectives, process and deliverables, and here for a poster that describes the Impact Pathways Approach.

 

When PIPA works best:

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 some 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 common understanding and commitment with its stakeholders. In this case, two or more representatives from each important stakeholder group should attend. The ideal group size is four to six and the ideal number of groups is three to six. We have facilitated workshops with nine projects developing impact pathways but this leaves little time for individual presentations and plenary, and participants tend to be overwhelmed by too much information.

 

How to conduct a PIPA process:

  1. Draw a problem tree
  2. Derive project outputs
  3. Create a vision
  4. Draw network maps
  5. Develop an outcomes logic model

 

Products:

We have used the outputs of PIPA workshops to develop two main products – impact narratives and evaluation plans.

 

Process Use of PIPA:

Carrying out a PIPA workshop is probably worthwhile even if there is no follow up to develop an impact narrative or evaluation plan. We asked participants in the first PIPA workshop in the Volta basin what had been the most significant change resulting from their attendance. The four responses we received were:

- New knowledge from the PIPA workshop led a project member to a methodology for "Influence Network Mapping" which is showing sufficient promise as to make the front page of the CGIAR eNews in June 2007 (see http://www.cgiar.org/enews/june2007/story_04.html).

- PIPA helped a peri-urban waste water project identify the Ministry of Food and Agriculture and Accra Metropolitan Assembly as key stakeholders and the project subsequently lobbied both organizations to change a crucial by-law.

- A third project attributed their success in organizing a capacity building consultation workshop with end users to the clarification of project outputs through constructing a problem tree in the workshop.

- The workshop motivated the projects working in the Volta basin to meet to identify synergies and share impact pathways methodology with colleagues who had not attended the workshop.

 

Comments (0)

You don't have permission to comment on this page.