Friday 11 March 2016

(Inspired by discussion among engineers in a meeting a week ago)
-----------------------------

What should Logic Modelling look like?

There are two options.
Many logic models are in the "forward-line" form of

input --> processing --> output

or can be elaborated for more complex sequence

Input --> process --> output --> outcomes --> impact

Its form puts all cause references at the front of the logic model.
If the project includes other causes at the same moment, these can be difficult to represent.

The advantage of this style of model of its consistency.
It’s easy for people unfamiliar with the project to read the logic model.
(Ref. betterevaluation.org/blog/drawing_logic_model)

The alternative style is an “outcomes hierarchy” where every diagram is refer to the result or impact. This makes more explicit all causes that underpin or derive the outcomes.

However, this type of diagram needs to be carefully designed to make them easy to read, since there is no standard format.

Who should be involved?

Logic models benefit from bringing together different knowledge and perspectives, so it can be useful to involve people with direct experience of similar projects, expert or adviser or licencor and outsiders (like management or vendor) who can ask either “difficult” or “dumb” question about hidden assumptions.

How can you draw a logic model?

Workshop methods can be useful when you want to make it easy for many people to be involved in the process to have the same understanding.
To draw up a logic model in a computer, you can use generic software of Microsoft. Or you can use specialist software, which can also be used in real time simulation but it is very costly.

Review and Evaluation

There is a tool to be planned for evaluation, and it is not a simple task
1. Clarify and communicate intended outcomes and assumptions
2. Make causal assumptions explicit and test how they are supported by evidence (from workshop or philosophy or else)
3. Provide framework and schedule for monitoring and evaluation
4. Tell the story how it works

Quoted a good statement from a reference:
 “Consultatively the process should involve working with a range of stakeholders to draw on their understanding of the outcomes and logic, and also encourage greater ownership of the final program logic diagram.”

-end of story-

References:

1. Weiss, C. H. (1972). Evaluation research: Methods for assessing program effectiveness. Prentice-Hall. Englewood Cliffs, NJ.

2. Department of Premier and Cabinet (DPC)  NSW public sector  http://www.dpc.nsw.gov.au/programs_and_services/policy_makers_toolkit/steps_in_managing_an_evaluation_project

0 comments:

Post a Comment