Critical Incident Technique (CIT)From the KM4Dev Community Wiki
CIT is a tool for exploration/planning, evaluation projects and empowerment/animation projects:
Critical Incidents (CI) are short narrative descriptions of situations where there is a problem of a systemic organisational and institutional adaptation, or where there is a problem rising from differences between the interacting parties. Critical Incident Technique is a qualitative tool to analyse and unearth the problem solving behaviour of people. It points a critical problem situation and packs it into a short story. This will trigger off the reflection process of the interviewed person and animate his/her problem solving behaviour. The Critical Incident Technique is situational and relies on the realistic situation of its narrative. The Critical Incidents are either presented as a story only or can be equipped with alternative explanations and feedback. In the case where beforehand “solutions” are prepared and discussed with the interview partners (i.e. the persons interviewed, the interviewees), the interview partners are expected to choose the “best” explanation considering the context.
(works great in the field/at grassroot level, eg. in rural communities, with illiterate people, …; has at the same time effects of awareness raising, empowerment, training - and mostly people find it fun, more fun than eg. a normal survey)
(add your story)
(add your name/contact email)
You can download a short manual on how to use CITs here: http://www.i-p-k.ch/_mgxroot/page_10785.html (Critical Incident Technique in Knowledge Management)
Some background thinking about the principles applied in CITs can be read on Dave Snowden's blog, where he reflects how (ie. from what) we learn and how to get people to talk about failure: http://www.cognitive-edge.com/2007/07/the_evolutionary_advantage_of.php