Article Review 6
Champion, (2002) Taking Measure: Map out evaluation goals, A master plan can guide you down the rocky path of evaluation, Journal of Staff Development , Fall 2002 (Vol. 23, No. 4)
http://www.nsdc.org/library/publications/jsd/champion234.pdf
Summary: This article discussed the importance of creating a master plan for evaluation of a program before implementing the program. Developing an evaluation master plan takes additional time, but is worth the effort to avoid delays and going off on a tangent.
Two types of program evaluations are summative and formative. A summative evaluation documents the impact of a program and considers if the program should continue, be altered, expand, downsize or eliminated. A formative evaluation monitors and collects data used to make adjustments to meet goals of the program. The author segments creating an evaluation master plan into four phases:
Organize the process: form a steering committee, write a clear description and agree on purpose of evaluation.
Design the evaluation: generate questions, determine method of accumulating data, determine approach (quantitative or qualitative), create schedule, and generate system for collecting and analyzing data.
Prepare report: determine audience(s) that will want/need results, format that results will be provided: reports, presentations, photo displays, charts, etc.
Create work plan: list task associated with evaluation, create timeline, assign work, and distribute master plan.
Implication : When planning a program it can be very beneficial to design the evaluation at the beginning of the process rather then evaluation being an afterthought. It is easier to create a master plan if the program being evaluated has stated indicators of impact and well defined goals then for a program with vague goals. The author made an excellent point for both formative and summative types of evaluation in order to be credible do not use program designers or implementers to perform significant evaluations.
Reaction : This article was well written and provided an overview of how to map out evaluation goals and different approaches to evaluate programs. The author provided adequate detail of phases to consider. I really liked the suggestion of designing the evaluation at the beginning of the program development process so that designer is aware of what needs to be included in the program content thus limiting the need to alter or change the program design for missing evaluation goals.