Loading...
← Back to Home

Monitoring strategy And data collection

Module 5: Monitoring tools

5.3 PVE change capturing tool

Change capturing tool provides a process and a matrix to assess the extent to which changes brought about by the programme have contributed to PVE and provides a framework for reflection on programming implications. This is a tool for monitoring changes during project implimentation, however, depending on the length of the programme and nature of changes, it can also be a useful evaluation tool to assess change over the lifetime of the programme.
Why use it? The tool encourages critical reflection of a programme’s contribution to PVE outcomes, and can help in encouraging learning.

This tool is most useful at the implementation, monitoring and adaptation stage. If used for baseline or context analysis, it is also useful at the design stage. It is important to be aware that data collection methods should be considered at design stage in order to ensure the right methods have been selected for what the tool seeks to measure. It can be used together with:

1.1 Understanding the VE challenge

1.4 Prioritisation of factors

2.2 Articulating change

4.3 Prioritising indicators

5.2 Context monitoring (timeline) tool

Step 1: PVE change capturing guiding questions

Adapt these questions to track and capture change related to the project. Use the questions as stimuli to populate the PVE change significance matrix. This process can be incorporated and used as a monitoring tool on a regular basis, for example, quarterly in a team or at a partner meeting. This encourages monitoring as part of good reflective practice and helps with recognising change and adapting a project accordingly.

  • What are the key issues relating to VE and PVE? Use your context analysis for reference.
  • What other non-VE specific issues in the context are relevant?
  • How have regional (sub-national) and gender differences been addressed (do issues affect different groups differently)?
  • Identify the most salient (highest priority/risk) drivers. Note how and why these were chosen.

  • What approaches did your project take to address these issues? How did your project reduce vulnerability to VE drivers or support resilience? Refer to specific examples.
  • Were any VE factors not addressed by the project? Identify and note why.
  • How did the project address different groups of men and women’s needs differently?

  • What changes did you observe related to resilience or vulnerability to VE for different men and women? Record positive and negative changes.
  • What happened as a result of the activity? How do you know? What evidence do you have?

  • Were there any other changes in the context or other interventions that could have impacted on vulnerability or resilience? (Consider interventions by other implementing agencies).
  • Were there any other changes in the context or other interventions that could have affected the ability of the project to reduce vulnerability or increase resilience to VE?

  • What is the significance of this change? How does this change relate to desired programme changes and impact? Is it sustainable?

  • What new changes have been observed since the last meeting?
  • Review previous changes captured – are they still relevant/applicable?
  • Does new evidence change your analysis of these outcomes in terms of significance or contribution?

Figure 22: PVE change significance matrix
Step 2: Assessing implications for programming

Reflect on the implications:

1

Is this what we expected? If not, why not? Are there gaps/flaws in our analysis or ToC? Does the programme M&E framework need to be reviewed and adapted?

Reflect on the implications:

2

What will we do with the results – what are the implications for our intervention strategy? Should we maximise efforts on the ‘high’-level changes, or focus on how to make the ‘low’-level changes higher?

Reflect on the implications:

3

How can we build on the changes to support better impact?