Evaluation 101 Banner
 

Set the Stage for your Evaluation

Stage

Preparing for an evaluation is a lot like preparing for other important activities. You have to determine what information you need, lay out a plan, and make some decisions about how you will proceed.

Gather Background Information

Doing interviews, reviewing reports, searching in dusty archives—whatever it takes—read everything you can to learn about all the aspects and the various nuances of your project. (Escape route: This step is only necessary if you’re starting from the beginning as an evaluator. If you already have a program, initiative, or program in place, then you’ve got the information you need.)

The background information you need is often in the hands of other people—especially if you are an external evaluator— someone who is conducting an evaluation of a project that he or she did not design.

If you have not been integrally involved with the design of the project or program, you should read everything, from reports to memoranda and meeting notes. In fact, review any documentation that helps you better understand the project. And don’t forget to talk to the program designers and other key stakeholders. They’re an invaluable source of information that can help you better understand the project. They will also help shape questions, identify credible sources, and provide encouragement and critical feedback. Finally, they will render the incalculable service of helping you review and interpret your findings.

Together, the information you pull together from these sources will help you develop a conceptual framework or logic model. Many program designers find it very useful to do this, because then you can view at a glance—and discuss with ease—the project’s motivation and intentions, components, strategies, and desired outcomes.

Develop a Logic Model

A Logic Model is used to conceptualize a single intervention, project, initiative, or program. While it is helpful to build one to understand the relationships among the implementation steps of a project, program, or initiative and the intended outcomes and impact of those activities, it works best if all the activities fall within one initiative. For example, if the goal is to implement a new literacy program in a school, then a logic model can depict the activities that will be undertaken to get that literacy program in place.

For a more detailed explanation of logic models, click here. For more information about developing a logic model, go to Lab 1: Logic Model.

Design Plan
  -
  -

 

No doubt you have a lot invested in gaining approval or funding or whatever was needed to plan and implement an project or program, and you initiated it based on a belief that it will work and will benefit the target audience—children, teachers, coaches, instructional aides, parents—whoever it might be. Just getting the pieces in place and “pushing the boat off the shore” and then waiting to see whether the wind comes up or what people say about the experience is not enough to determine its value.

How will you know whether the project or program you have initiated is making a difference?

Remember the 3 BIG questions?
(mouse-over to view them)
Question1
Question2
Question3
These are the high-level questions you need to keep in mind, but before you can decide what data or information to collect, you have to develop an evaluation plan that will make capturing it possible. This is arguably the most critical phase of the process. Clear thinking and careful planning will save headaches later as the data begin rolling in.
Select Methods
  -
  -
  -
    >
    >
    >
    >
    >
    >
 

Interviews...Asking about participants’ points of view.

Interviews?

All interviews work on the assumption that the participants’ perspectives are meaningful, knowable, and can be made explicit, and that their perspectives affect the success of the project. But not all interviews are the same.

There are two basic types:
  • Structured interviews are carefully worded questionnaires designed to ensure that every respondent answers the same questions in the same order. Interviewers are trained to deviate only minimally from the question wording to ensure the uniformity of interview administration.
  • In-depth interviews don’t follow a rigid structure but encourage free and open responses instead. Be aware of the potential tradeoff between in-depth exploration and comprehensive coverage.
When should you use an Interview?
Use interviews when you want to know:
  • What the program looks and feels like to participants and stakeholders
  • What concerns stakeholders about the project
  • What expectations participants and stakeholders have
  • What features of the project stand out the most
  • What changes respondents perceive in themselves as a result of the project

 

Tips on Conducting Interviews
  • Be very familiar with the interview protocol. Read it several times before the interview to ensure comfort with the types and flow of questions.
  • Be prepared to rephrase questions or ask them out of order. Often, interviewees need questions re-worded to understand their meaning. Or they will answer parts of other questions, if it seems relevant to them. Move the interview along with good follow-up questions.
  • Be relaxed. Interviewees can sense your comfort or anxiety. You want the interview to flow as a conversation with specified topics. The more relaxed you are, the more relaxed the interviewee will be, helping the interview flow smoothly.
  • Maintain eye contact. Don’t be so involved with your notes that you don’t show a high level of engagement.
For an example, take a look at the teacher interview protocol.
Analyze Data
 
-
 
-
 
>
 
>
 
>
 
>
 
>
 
-
 
-
Analysis of
Qualitative Data
 
>
 
>
 

Analyze DataYou’ve developed an evaluation design. You’ve determined the best means to collect your data, and then you’ve done it—collected all of it. Now you’re at the point of making sense of all the data available to you. But how do you do it?

Analyses of both qualitative and quantitative data can yield a rich pool of information, but pulling it out of the raw data requires that you follow a few basic steps—carefully. Presenting your findings in a clear and convincing way is the final step in this phase of your evaluation.

What will you do with the information?

This is where the whole evaluation process was leading from the beginning. What decisions can you make based on the data collected? What actions can you—should you—take? This is where you decide what changes you and others want to make to improve the program or what steps to take to initiate a new one. Recall the questions you identified in the beginning.
How did you answer them?
What did you learn?
How will you use this information?
Choice
What did you find?

In some ways, this is the most satisfying stage of your evaluation. After preparing for and designing your evaluation, after collecting and analyzing your data, you can now tell the world (or at least the people important to your project) what you found.

ReportA good evaluation report is clear, concise, and provides adequate evidence for claims and enough explanation to make sure the reader understands your interpretation of the data. It is sometimes tempting to include too much information. When you have collected stacks and stack of surveys and reams of field notes, it is difficult to know “when to say when.” You’ve become invested in each of your data tables, but if the data don’t show anything, leave them out. Be clear about how the evaluation was conducted as well. Everyone involved in developing the school improvement plan or who is affected by the school improvement plan will be interested both in the methods and the outcomes of the evaluation.

Taking action means implementing specific strategies to accomplish your goals—to “put the rubber on the road,” as they say. Develop an action plan based on the data collected. Changes or improvements may focus on the content of the program, format, delivery, staffing, follow-up strategies, activities, setting, resources, and on and on. It all depends on what your data tell you. And all the decisions do not need to be made at one point in time. Collecting data to make course corrections should occur in an iterative way—one change leading to another after the results of the first change are assessed.

Tips on Making Decisions and Taking Actions
  • Consider whether you think the findings are valid for your program. Validate the data by looking for support for one set of data in another set. Do the findings clearly apply to your situation?
  • Determine what actions/decisions are suggested by the findings. Focus on areas to address, but you don’t try to address everything at once.
  • Determine whether possible actions are feasible. The data may suggest changes that are not really possible for you to make—given resources, time, or other constraints.
  • You may need to do additional research or information-gathering on particular strategies or program adjustments. Don’t jump into something without knowing enough about it to know whether it is likely to work for your set of circumstances.
  • Determine how you will know whether the changes/improvements are working. Put a monitoring plan in place that will allow you to watch implementation carefully. Don’t forge ahead without examining how well things are going as you proceed.