Blue Flower

The vast majority of projects decide in advance exactly what they're going to achieve, and list these achievements under headings like "outcomes" and "indicators".

This is good thing to do in itself - it's always good to have a plan - and is often a requirement of funding.

But too great a focus on outcomes and indicators can risk missing any unexpected changes your work has led to.  Outcomes and indicators also rarely say much about which of the changes that happened were the most important for the people you worked with.

Most significant change technique addresses this problem by focusing on the qualitative, storytelling aspect of evaluation that is so important for establishing the quality of a project's outcomes, as well as their quantity.

Our experience is that even if it is only used in the most, basic, stripped-down way by simply making sure to ask participants without any prompts what the MSC was for them, any project's learning will benefit from being familiar with it.

If you're interested in the fuller version of the technique, the original (and very accessible) guide to it is available from Capacity4dev among various other places.