This site provides a list of program logic models available on the internet.
Program logics are a type of outcomes model which uses diagrams or other methods to set out the steps which occur in a program (or project, organization, policy or sector) leading from low level activities right up to high-level outcomes.
The program logic approach has a lot in common with a range of other methods which draw outcomes models or which set them out in tables of type or another. Outcomes models are used in a number of sectors and disciplines under a range of different names in addition to program logics. These names include - strategy maps, results chains, ends-means diagrams, program theories, theories of change, intervention logics, logframes, and outcomes models. See the types page on this website for a summary of these various approaches.
The traditional way of setting out program logics
A classic guide to the traditional way of setting out program logics is the W.K. Kellogg Foundation Logic Model Development Guide.
Another resource is the University of Wisconsin Extension site on logic models.
The above resources set out how to draw program logics using the traditional approach - dividing the model up into layers. E.g. inputs, outputs, intermediate outcomes, final outcomes etc. and sets out these layers in tables or diagrams. Layering outcomes models in this way is just one option. See the To layer or not to layer page on this site.
Many examples of program logics are provided on this web site. These are listed here to provide an index to program logics which have been put up on the internet. You need to check the source URLs to find out copyright and reuse provisions for all of the program logics listed on this site.
The new paradigm for setting out program logics
The new paradigm is to use the Outcomes Model Guidelines from the outcomesmodels.org site. These guidelines recommend that outcomes models are not divided up into four or so layers because such layering is usually simply an attempt to indicate whether or not steps are measurable, attributable and accountable - something that can be indicated after the model has been drawn (see To layer or not to layer page). The guidelines also recommend a 'modular' approach to outcomes model development which has advantages in terms of presenting and working with a dataprojected model in a group. Modularity also enables parts of a models to be shared between models and provides a very efficient way of quickly putting together a initial draft outcomes model that can then be used as the basis for discussion by stakeholders, a project or an evaluation team.
Many examples of outcomes models drawn using the new paradigm are provided at outcomesmodels.org. You are free to use all of the models at the outcomesmodels.org site for most commercial and non-commercial purposes as long as you acknowledge their use.
Software for visualizing outcomes models
Program logic outcomes models are at their most powerful when they are visualized. Models can be drawn using any type of drawing software, for instance Inspiration or Visio. Alternatively you can use the newly developed DoView outcomes model software which has been specifically designed for building program logics and outcomes models. From mid November 2007 DoView will allow you to build both traditional outcomes models and also build those using the new paradigm. You can even build two versions of same model within DoView.