On 6 Jun 2012, at 14:07, Mike Ellis <[log in to unmask]> wrote:
> I don't know how or whether we can solve this but ideally there would be a capital budget and then a project iteration budget as well as an operating budget. Oh, and a gin and tonic budget too...
Including a post-launch community management budget...
IMHO, digital projects should always have more front-end and formative evaluation than summative. Even then, if you're doing testing without the ability to make changes in response then you're wasting your time and money - a depressing thought when many projects don't have timelines or flexible outcomes to allow this, and aren't able to share what they've learnt about what didn't work as well as what did.
On that note, I'm curious about the institutional and personal reasons people find it difficult to share less than completely positive results, whether from iterative or summative evaluation. Any thoughts?
Bridget's summary of the problems with summative evaluation seemed pretty definitive to me, but I'd love to know more about the 'Theory of Change'.
Cheers, Mia
>
****************************************************************
website: http://museumscomputergroup.org.uk/
Twitter: http://www.twitter.com/ukmcg
Facebook: http://www.facebook.com/museumscomputergroup
[un]subscribe: http://museumscomputergroup.org.uk/email-list/
****************************************************************
|