Monitoring Impacts of Project reports and other written outputs

From KM4Dev Wiki
Revision as of 16:57, 6 October 2010 by Davide Piga (Talk | contribs)

Jump to: navigation, search

Original Message

From: Grant Ballard-Tremeer, posted on 2009/02/18

I'm currently trying to develop a methodology for monitoring the impacts of project reports, policy briefs and other briefing papers. In one particular project which is producing these sorts of products we could quite easily track dissemination - where copies generally go, how many copies are distributed, potentially even who downloads/receives what - but that tells us little about who actually *reads* the reports, and even less about whether anyone uses them.

While this is clearly related to the earlier discussions on the monitoring of networks we haven't yet identified much best practise in this specific area.

Any suggestions and experiences would be warmly welcomed.

Contributors

All replies in full are available in the discussion page. Contributions received with thanks from:

Grant Ballard-Tremeer
Jane Lennon
Peter J. Bury
Simon Hearn

Related Discussions

Summary

Detailed Description

[the meat of the topic – clearly, crisply communicated summary of the topic. Where relevant, a brief story – no more than 1-2 paragraphs - of how this topic has been turned into practice, ideally from the KM4Dev archives? If the example is long, separate into a separate subsection]

Examples in Application

[One or a few practical examples and references that illustrate the topic or show how it is done in practice]

Recommended Resources

[Links to publications, websites, contacts and general resources shared in the e-discussion]