A logic model is a succinct representation of important aspects of a program, project or initiative – including what goes into it (inputs), the main activities, changes the program is trying to help bring about (outcomes and impacts). It also begins to describe how a program is going to be evaluated by listing the indicators or the clues that the team will look for to tell if a program is a success. It is often created in a table format, but there is no firm rule about what it should look like. If there was ever a sector who could bring some life into something like the logic model it would be the arts sector – so go nuts! There is lots of overlap between theory of change processes and documents and program logic models. Don’t try to think too hard about what is the difference between them or you might go cross-eyed! If you end up doing one but not the other that is fine! Or if you combine them into a hybrid document that is great too. The important thing is that you are thinking about why you are doing what you are doing and what success will look like.
To gain consensus among the program team
To guide program delivery and evaluation
Usually a Program Manager and/or a program team member takes the lead on developing a program logic model and seeks input from others as needed
As close to the beginning as possible as it is primarily a planning tool
On a computer in a shared document that the full program team can access