As promised, here is a summary of the case you shared. It was very helpful and easy to read:
What is this document about:
This is a casestudy of outcome harvesting done by Saferworld company. This company works in complex, conflict-ridden environments, with fast-changing dynamics,
Why outcome harvesting:
They were seeking a MEL approach that would reflect this organisational agenda and concentrate on meaningful evidence, by listening to and valuing communities’ own definitions of what constitutes success.
The Status quo:
- plenty of data on the ‘what?’, but not enough on the ‘so what?’, i.e what difference did it make?
- Rigid nature of the logframe
- unhelpful nature of quantitative measures.
What is Outcome Harvesting:
Outcome Harvesting is an evaluation approach inspired by Outcome Mapping and Utilization- Focused Evaluation. Unlike other evaluation methods it doesn’t start with predetermined outcomes, and measure progress towards them, but rather collects evidence of what has been achieved in the programme or project area, and works backwards to determine whether and how the project or intervention contributed to the change.
Outcome harvesting process followed:
asks a few core questions for data-gathering about the change in behaviour:
• Who did what, when and where?
• How significant is this change?
• What contribution was made by the programme to this change?
shifting attention away from activities (what did we do?), onto the practical, observable shifts in actions by the actors our programmes are seeking to influence (what did they do differently?).
How is this casestudy different:
Outcome Harvesting is largely practiced as an evaluation approach, they wanted to see if it would help then in their regular monitoring. They wanted teams to be able to discuss ‘outcome