|
![]() | ||||
|
Back to Connections archives |
Implementation - Designing and Conducting an Evaluationby Jessica LeavittCommunity Connector Staff "There is no one best way to conduct an evaluation." It depends upon the people involved and their situation.1 When preparing for an evaluation, evaluators decide upon evaluation questions. Now, after deciding the questions to address, the evaluation team must decide what information is needed to answer those questions, and from whom and how the information can be best obtained. Begin with a Flexible Design It is critical to have as a base a "flexible and responsive [evaluation] design" that is linked to your highest priority questions.2 This flexible design can be achieved by: Determine data -collection methods The Kellogg Handbook argues that "no single evaluation method can document and explain the complexity and richness of a project."4 Thus, in making decisions about methodology, there is no one correct approach but instead a range of options to choose among. One is not inherently better than the other, but quantitative methods will provide different information than qualitative; interviews do expose different issues than will tests and assessments or document reviews. How then to choose the evaluation design? Patton argues in the first place that it is important to involve intended users in methods decisions5 . If the design makes sense to the intended users, the credibility of the results will be increased, as will the likelihood of the results being utilized. After ensuring the involvement of intended users, an initial step in deciding upon a design is to navigate the difficult decision of whether to use quantitative methods (essentially counting and measuring) or qualitative (essentially asking and interpreting how a project functions and what that means to the people involved). One position, advocated by the Kellogg handbook, is essentially that both methodologies have much to offer and should both be used. Qualitative methods can "help the evaluator understand the context of a project;" the context then "sets the framework for a meaningful understanding" of quantitative data. Patton has a more complicated response to the issue, arguing that, in place of quantitative v. qualitative, evaluators should seek simply to create fair/ conscientious designs by presenting both (or multiple) sides of issues, and being aware of, and presenting, the evaluator's own biases.6 Patton argues further that neither quantitative nor qualitative can be evaluated as good or bad methods in the abstract; it all depends upon the purpose of the project being evaluated, and the goals of the evaluation. "The more a program aims at individualized outcomes," he posits, "the greater the appropriateness of qualitative methods. The more a program emphasizes common outcomes for all participants, the greater the appropriateness of standardized measures of performance and change."7 In addition to the question of whether to approach evaluation from a quantitative or qualitative stance is the question of what data collection method to use. Should you, for instance, employ observation, interviews, written questionairres, tests and assessments, or document review? The Kellogg handbook suggests that in making the decision evaluators must be informed by considerations of: resources available; sensitivity to participants/ respondents; credibility; and importance of the information.8 Collecting data "Collect only the information you are going to use, and use all the information you collect."9 Once you have decided upon evaluation questions and the methods to employ, you are ready to collect data. A valuable first step to avoid unnecessary work and to utilize to the fullest work that has come before yours is to examine and learn from existing information about "your target population, community or project." When you perform the data collecting outlined in your evaluation plan, you should remain open to the possible need to "revise data-collection strategies based on initial analyses. What is working? What is not working? What pieces of data are still missing?"10 Data collection and methodology design should be flexible, responsive, and iterative, focused constantly on realizing the primary purpose of the evaluation.
Footnotes:
Originated: 2/24/99 | Maintained:
si.cn@umich.edu | ||||