A rigorous approach to lesson learning

From KM4Dev Wiki
Revision as of 06:35, 29 July 2013 by Davide Piga (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Original Message

From: Juliana Caicedo, posted on 2010/08/06

Hi everyone,

A newcomer to this group, I’m looking forward to participating in many interesting conversations. I’d like to start by consulting you on an issue I’ve been struggling with: what would be a rigorous (almost scientific?) yet light enough methodology/approach to capturing lessons learned throughout the project cycle. As humans, we all have our own perceptions and biases, so I’m looking for a way to minimize those and extract lessons from an intervention that can become valid/solid evidence to inform a new program /project, perhaps in a different context. I believe that a methodology that is too heavy or cumbersome will just discourage people from properly reflecting and capturing their lessons learned for the good of the organization, but I also think that rigour is important if we are to use those lessons to inform decision making.

Grateful for any insights and experiences that you’d like to share with me.

Juliana

Contributors

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

Juliana Caicedo
Atanu Garai
Nancy White
Arthur Shelley
Juliana Caicedo
Ian Thorpe
Manuel Flury
Christina Merl
Jaap Pels

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]

Further Information