Evaluation Planning – Stage 2: Program Model Development
This stage is intended to enhance the working group members’ knowledge of evaluation concepts and how to use systems approaches for analyzing programs, and develop and fine tune their program’s Logic Model and Pathway Model. In the previous stage we were working with the organization as a whole. During this stage we are working primarily at the level of the program (but there may be some overlap between programs if you are working with more than one program in an organization). Of course, because we take a systems view, we will be considering the broader organizational stakeholder context. But in this part of the Protocol we primarily work with staff of each individual program.
This stage involves several steps that address: Stakeholder Analysis, Program Review, Program Boundary Analysis, Lifecycle Analysis, Logic Model, Pathway Model, Evaluation Scope, Program-System Links, and Reflection and Synthesis. Many of these steps could be completed by the Evaluation Champion alone. However, the process of developing a program model depends on the contribution of stakeholders and is strengthened by collaboration and discussion among program staff. Many of the steps may be performed in a different sequence or in tandem and will build upon each other in an iterative manner.
Q&A
Q: What is the difference between a logic model and a pathway model?
A logic model is a representation of the main components of a program and the theory of change underlying that program. Both the columnar model and the pathway model are types of logic models. These two types have a lot in common, but each also has unique features. Both models include activities, outputs and outcomes. The columnar logic model also includes inputs, context and assumptions. These components provide important information about what it takes to run this program, what environments it is designed for, etc. This information is useful to others who might want to replicate or learn from this program, and may be important aspects to evaluate. A pathway model does not include inputs, context, or assumptions but it has causal arrows between activities and outcomes, creating a graphical representation that highlights the theory of change in a much more specific and detailed way. These arrows make it possible to see and follow the story-lines that explain how the program seeks to achieve its goals. The graphical representation allows for detailed, shared understanding of what the program is and how it works – this forms an invaluable foundation for making good evaluation decisions.
Presentations
- Length 6:58