The next part of the workshop involves distilling and integrating the information from the problem trees, vision, identification of outputs and network maps into the outcomes logic model. The outcomes logic model borrows in part from Bennett’s hierarchy (Bennett and Rockwall, 2000; Templeton, 2005). It is based on the premise that a number of actors will need to be doing things differently if the project is to achieve its vision. It is constructed in table format and each row of the table corresponds to an actor and describes the changes in practice, knowledge, attitude and skills (KAS) that are needed to achieve the vision. It also describes the project strategies to achieve these changes. Project strategies include co-developing project outputs (knowledge, technology, etc.) with stakeholders, capacity building, communication, political lobbying, etc.
|
Actor (or group of actors who are expected to change in the same way)
|
Change in Practice required to achieve the Project’s Vision
|
Change in KAS required to support this change
|
Project strategies2 to bring about these changes in KAS and Practice?
|
|
|
|
|
|
|
|
|
|
|
For example, strategies for developing project outputs would be entered in column 4 of the table. Participants then describe what changes in KAS and practice will result from the development and use of project outputs. In contrast, the scaling strategy often identifies changes in stakeholder knowledge or attitude towards what the project is trying to do, and would be entered in column 3 followed by the cells in the other columns.
This exercise would take about an hour-and-a-half.
Participants will need the materials they have produced in the workshop: the problem tree, vision, network maps and use these as inputs.
The project’s outcome logic model is constructed by filling out the worksheet shown in the table below, based on information contained in the workshop outputs. One worksheet is filled out for each of the four main stakeholder groups-–next users, end users, politically-important actors and project implementors. Different workshop outputs have different starting points in the table. For example, development of the project outputs – identified in the problem tree analysis – requires strategies that would be entered in column 4 in the worksheet. Participants then describe what changes in KAS and practice that will result from the development and use of these products. The scaling strategy(see here for a diagram of the PIPA process), often identifies changes in stakeholder knowledge or attitude towards what the project is trying to do, and would be entered in column 3. Bringing these changes about may involve the development of outputs with those stakeholders, but it may also involve other strategies, such as communication of research findings through face-to-face meetings and medium such as radio programs, policy briefs, journal articles, etc.
Filling out the table starting with project outputs
Filling out the table starting with scaling strategy (changes in attitude)
|
Actor (or group of actors who are expected to change in the same way)
|
Change in Practice required to achieve the Project’s Vision
|
Change in KAS required to support this change
|
Project strategies2 to bring about these changes in KAS and Practice?
|
|
Step 1. Write the name of the actors
|
Step 3. Describe what they would be doing differently when they have this change in attitude
|
Step 2. Describe the change in attitude
|
Step 4. Describe the project strategies. |
| www.hit-counter-download.com |
Page Information
|
Wiki Information |
Recent PBwiki Blog Posts |