Difference between revisions of "Most Significant Change (MSC)"
From Learning and training wiki
Line 13: | Line 13: | ||
*'''''Looking back over the last month, what do you think was the most significant change in [particular domain of change]?''''' or | *'''''Looking back over the last month, what do you think was the most significant change in [particular domain of change]?''''' or | ||
*'''''From among all these significant changes, what do you think was the most significant change of all?''''' | *'''''From among all these significant changes, what do you think was the most significant change of all?''''' | ||
+ | }} | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | {{Tool|Implementing MSC| | ||
+ | For a successful MSC implementation, it is necessary to create and facilitate the following contexts: | ||
+ | *An organizational culture where it is acceptable to discuss things that go wrong as well as success | ||
+ | *Champions (For example, people who can promote the use of MSC) with good facilitation skills | ||
+ | *A willingness to try something different | ||
+ | *Time to run several cycles of the approach | ||
+ | *Infrastructure to enable regular feedback of the result to stakeholders | ||
+ | *Commitment by senior managers | ||
+ | |||
+ | |||
+ | Implementation steps of MSC technique: | ||
+ | #Starting and raising interest | ||
+ | #Defining the domains of change | ||
+ | #Defining the reporting period | ||
+ | #Collecting SC stories | ||
+ | #Selecting the most significant of the stories | ||
+ | #Feeding back the results of the selection process | ||
+ | #Verification of stories | ||
+ | #Quantification | ||
+ | #Secondary analysis and meta-monitoring | ||
+ | #Revising the system | ||
+ | |||
+ | =='''Step By Step'''<ref>''idem''.</ref>'''== | ||
+ | |||
+ | |||
+ | =='''Building capability for effective MSC'''<ref>''idem''.</ref>'''== | ||
}} | }} |
Revision as of 15:51, 9 December 2009
Most Significant Change (MSC)[1] |
The most significant change (MSC) technique is a form of participatory monitoring and evaluation.
Like monitoring, MSC provides ongoing data about program performance that assists program management. But MSC goes further than most conventional forms of monitoring in that it also focuses on outcomes and impact, involving people in making judgments about the relative merits of different outcomes in the form of MSC stories. In this way, MSC contributes to both monitoring and evaluation. MSC also has the potential to influence organizational learning within an organization, and maybe even within its associated stakeholders. The horizontal dimension is between a group of participants engaged in discussing and selecting the most significant of a set of stories. Vertical dialogue involves exchanges of views between groups of participants at different levels. The vertical dimension is very important if the MSC process is to aid organizational learning throughout the organization. It depends on good documentation and communication of the results of one group’s discussion to the next. The process pf MSC involves the collection of significant change (SC) stories emanating from the field level, and the systematic selection of the most significant of these stories by panels of designated stakeholders or staff. The kernel of the MSC process is a question along the lines of:
|
Implementing MSC |
For a successful MSC implementation, it is necessary to create and facilitate the following contexts:
Step By Step[2]Building capability for effective MSC[3] |
Cite error: <ref>
tags exist, but no <references/>
tag was found