Outcomes Hierarchy

Example

An outcomes hierarchy for 'an apple a day' program showing possible different causal paths

Advice

Advice for CHOOSING this option (tips and traps)

• This option is particularly appropriate if the activities don't just occur at the beginning of the outcomes chain, but at different stages along it.

Advice for USING this option 

• An outcomes chain is best drawn up at the start of a programme, and concurrent to the design of the ‘logframe’ if one is being used. It will help you better understand the way your outcomes interact and the dependencies between them, as well as to set realistic timeframes to measure progress.
• The development of an outcomes chain also offers a good opportunity to engage your program’s stakeholders in a discussion about the program. Stakeholders might include program staff, clients/service recipients, partners, funders, board members, community representatives, and volunteers.
• Ensure that once the outcomes chain is written it doesn’t just ‘sit on a shelf’ but is frequently reviewed and referred to during project implementation, performance measurement and evaluation.

Resources

Guide

• Funnell, S. and Rogers, P.  (2011) Program Theory: Effective Use of Theories of Change and Logic Models, San Francisco, CA: John Wiley & Sons.

Tool

• Developing Outcome Models: DoView and the Shower Curtain: This short article shows the development of a logic model using two techniques at the same time - a plastic shower curtain and DoView software.

Sources

Funnell, S. and Rogers, P. (2011) Program Theory: Effective Use of Theories of Change and Logic Models San Francisco, CA: John Wiley & Sons.