jump to navigation

Standardized visual evaluation plans - quick and effective October 9, 2008

Posted by Paul Duignan in : Using the approach, Communicating outcomes models, Doing evaluation more efficiently, Systematic Outcomes Analysis, Outcomes models, DoView, Easy Outcomes, Evaluation planning, Uncategorized , add a comment

Community Central Web Page Easy Outcomes Evaluation Plan ScreenshotI’ve not had much time to blog recently due to building a number of large outcomes models for public sector organizations; having input into the further development of DoView; and presenting at international evaluation conferences on Easy Outcomes, DoView and related evaluation and outcomes topics. A lot has been happening though, from version 1.14, DoView is now able to create web page versions of its visual outcomes models. I’ll do several postings showing how this new feature can be used. The first is that now, once an outcomes model has been built in DoView, the user can quickly create a web page version of the same model and then have it put up on an intranet or the internet. You can see (and use) a number of examples at OutcomesModels.org. The second great thing is that you can now produce visual evaluation plans will save you a great deal of time. I delivered a paper on this at the recent European Evaluation Society Biennial Conference in Lisbon. (more…)

A Systematic Outcomes Analysis framework for psychotherapy evaluation February 12, 2008

Posted by Paul Duignan in : Doing evaluation more efficiently, Outcomes systems architecture, Systematic Outcomes Analysis, Outcomes models, Easy Outcomes, Evaluation planning, DoView , 2comments

Psychotherapy outcomes model screenshotIn my last blog posting (which you should read before this one) I talked about using Systematic Outcomes Analysis to define the basic tasks one needs to do in quality assurance, monitoring and evaluation and how this can  avoid the need for a protracted theoretical discussion about the difference between quality assurance and program evaluation. I was using the example of an illustrative Systematic Outcomes Analysis framework I set up based on an outcomes logic model in regard to psychotherapy which I’ve posted on the Outcomes Models site. Here’s the PDF of the DoView file. Using the Systematic Outcomes Analysis approach, indicators and evaluation questions are mapped onto the outcomes logic model (indicators are marked with a yellow icon and evaluation questions with a green circular icon). This blog posting looks in more detail at ways stakeholders can use such a framework once it’s been developed. (more…)

Avoiding the question: Defining quality assurance versus program evaluation February 12, 2008

Posted by Paul Duignan in : Using the approach, Doing evaluation more efficiently, Outcomes systems architecture, Systematic Outcomes Analysis, Outcomes models, DoView, Easy Outcomes, Uncategorized , 3comments

OIE Basic DiagramSometimes it’s more useful to avoid initially answering a question that’s posed in a particular way because there’s a better way of addressing the concern that lies behind the question. Such is the case if you’re ever asked to define the difference between quality assurance (or monitoring) and program evaluation.

Seeing the question as a theoretical one and attempting to find a definition which works has some similarities to the situation where you’re building a house and someone keeps wanting you to stop and define, from a theoretical point of view, the difference between the kitchen and the dining room. Now, some people do stuff in the dining room that others do in the kitchen, and some do stuff in the kitchen that others do in the dining room. Still other people don’t really have any theoretical problems because they have a kitchen/dining area where they do both kitchen and dining room stuff.

A more fruitful way of working with the question of the difference between quality assurance (or monitoring) and program evaluation is to attempt to identify all of the stuff (tasks) that you would do under each of these. Once you’ve done that, you can then decide whether or not you need to spend a lot of time defining the difference between the two if everybody concerned is clear about which of the underlying tasks are, and are not, being done by whom.   (more…)

Reporting on outcomes to multiple bodies with different outcomes structures November 14, 2007

Posted by Paul Duignan in : Accountability, Outcomes systems architecture, Using the approach, Outcomes models, Easy Outcomes, DoView , add a comment

In a workshop the other day the issue arose of how you deal with the situation where you have to report to a number of different outside organizations on your outcomes. Now, this is not much of a problem where the outside organizations don’t make any implicit or explicit demands on how you report. The way to proceed in such cases is to simply develop your outcomes model and report back to them on it.

However, with more and more organizations thinking in terms of outcomes, they are starting to have outcomes structures of various types themselves. (more…)

Cutting out parallel processes - the CEO’s responsibility October 11, 2007

Posted by Paul Duignan in : Outcomes systems architecture, Outcomes models, Easy Outcomes , add a comment

Aircraft carrier bridgeOutcomes systems are a CEO and other managers’ way of aligning what happens in an organization with the outcomes it’s trying to achieve. It’s rather like the Captain on the bridge of a large aircraft carrier needing a well functioning communications system which flows all the way throughout the vessel. If they don’t have it, they’re not going to get the carrier to go where they want it to. The outcomes systems in many organizations are like an aircraft carrier which has a confusing mess of communications systems - all sorts of flags flying from the bridge, a telephone system, several radio systems, people shouting, small notes passed to individual sailors etc. All these have been introduced at different times, some are badly designed, some are now not functioning in the way they were originally designed to. Meanwhile, the captain is running around the bridge yelling into phones, scribbling on scraps of paper and waving flags while the carrier meanders around the ocean turning in larger and larger circles. (more…)

Castles of sand - cost benefit modeling September 30, 2007

Posted by Paul Duignan in : Economic analysis, Systematic Outcomes Analysis, Outcomes models, Easy Outcomes , 1 comment so far

BucketA while ago I came across a report of a cost-benefit analysis on climate change in which the author of the analysis admitted that his model may come in for some heavy criticism because it didn’t include any cost for sea level rises. How cruel and heartless of his critics. I don’t know who paid for this particular report or why it was done, so I don’t want to comment on it at all. However cost benefit analyzes which leave out or minimize important costs are a well used weapon in the lobbyist’s armory. Policy makers, the media and the public only have time to catch the bottom line - the cost will be this or that much and then move on. (more…)

What’s the Easy Outcomes site all about? September 20, 2007

Posted by Paul Duignan in : Doing evaluation more efficiently, Evaluation planning, Easy Outcomes, DoView , add a comment

I’ve realized that I’ve not put up a post about the Easy Outcomes site even though it’s been up for a few weeks. Easy Outcomes takes the Systematic Outcomes Analysis approach and applies it using DoView outcomes software. We developed it in response to feedback that the Systematic Outcomes Analysis site is a bit intense for those who just want to work out how to develop a good evaluation plan, but don’t want to get buried in the detail of the approach too soon. (more…)