2.06 Pathway Model
A Pathway Model is a visual program model closely related to the columnar logic model. A pathway model overlaps with a logic model in that it is based on the activities and outcomes that are in the logic model.Unlike the logic model, it does not include the details of inputs, assumptions, or context. However it adds a significant element by incorporating the logical connections that lead from an activity to one or more short-term outcomes, and from there to medium-term outcomes and ultimately long-term outcomes. It tells the story of how the program works, in a way that can’t be captured in the logic model. Together, the logic model and pathway model present a very informative, concise picture of the program and how it is believed to work.
The pathway model can be developed using the logic model as a basis for articulating clear and direct linkages between program activities and outcomes. If it has not been done already, discussion should help program staff begin to identify key pathways or “through-lines” that connect the activities to outputs and outcomes in their logic model. One way to think of this is to explain:
[ACTIVITY “A”] leads to [SHORT-TERM OUTCOME “X”],
which leads to [MEDIUM-TERM OUTCOME “Y”],
which leads to [LONG-TERM OUTCOME “Z”].
For example, using the sample logic model in Figure 10 shows that program staff may believe that the activity “Classroom session on module, facilitated by expert volunteers” leads to the short-term outcome “Youth participants learn new science content related to module objectives”, the medium-term outcome “Increase youth excitement about science and engineering”, and the long-term outcome “Increase pool of individuals choosing science and engineering careers.”
Figure 10. Sample Path from Activity to Outcome
Using software such as PowerPoint to create a flow chart can assist in presenting a single pathway or a more complete pathway – a single pathway may look something like that in Figure 11 and a more complete pathway model like that in Figure 12.
Figure 11. Pathway from Activity to Outcome
Figure 12. Program Pathway Model
The working group should continue to create these pathway links until “how the program works” has been described to their satisfaction. This is different from a logic model in that it shows how the components of the logic model are connected.
Look at the completed pathway model and ask:
Are there any activities that are not connected to any outcomes?
Are there any outcomes that are not connected to any activities?
If yes, why do these gaps may exist.
Was something simply left out of the model?
Or, is there a program activity that does not really address the program goals?
Is the program expected to lead to a particular outcome, but does not actually include an activity that would result in that outcome?
The items in the completed pathway model should be consistent with the logic model. The connections between activities, short, medium, and long-term outcomes should be relevant, appropriate and logical. In general, short-term outcomes should rarely be connected directly to long-term outcomes. It is also important to check and make sure that there are not any “orphaned” items. This refers to activities that are not connected to any outcomes or outcomes that are not connected to any activities. If you find that either of these situations arises, it is important to revisit the program boundary discussion. In the case of orphaned activities, ask whether the activity is serving an intended purpose or whether, for example, the activity is included because it has always been done. In the case of orphaned outcomes, ask whether there are adequate activities to address the outcome.
It is also important to review the pathways or explanatory “through-lines” that connect specific activities and outcomes. Make sure that the pathways clearly communicate the “story” or “program logic” and do not dead-end at short- or mid-term outcomes, but rather are connected to longer-term outcomes. In general, the pathway model should efficiently communicate the program logic and should be easily readable (e.g., the number of connections should not be excessive).
See Also: