Capacity Building and Training in Knowledge Sharing and Management: The Knowledge Expedition Approach detailed outline

From KM4Dev Wiki
Jump to: navigation, search

Prior to Day One (0900-0915)

Note: The KE team (refered to below) includes all those who have expressed an interest in taking part in the KE project working session.

Process
  • The Process team (to be identified) develops a process that can be used to elicit stories. They identify at least one person within the KE team who is willing to talk about their experience related to one of the eight themes.
  • ACTIONS: Define process team; Define the person who will share experience
Who wants to join?
Documentation
  • The Documentation team develops a general plan on how the stories will be captured
  • ACTION: Define documentation team; Establish some principles of what documentation should and should not record.
  • Guiding principles: How best to make stories travel separate from the person who experienced them? What is the process, which takes the richest and best raw materials and repositions it to be available for the furthest reach?
Who wants to join?
Day One (Monday, 18 June) Part I
  • Process team conducts the knowledge expedition supporting the KE team member in telling their story
  • ACTION: prepare some small prompts (briefing guidance/trigger questions)
  • Guiding principles: Encourage recollection of key moments to bring it to life: give him/her some time to scribble a few notes by trigger questions and then put them aside and speak from memory. Encourage the teller to place him or herself briefly autobiographically in relation to the material. Set it up so that there is a sense that there is an individual to whom they are telling the story so that it feels like it's individual to individual, personal, even if other people are in the room.
  • ACTIONS: Victoria to send question list.
Process Team
Day One (Monday, 18 June) Part II
  • The KE team including the documenters, share what they heard in the story to reach shared picture in the room. The KE team is then invited to ask questions and draw out more detail.
  • The KE team reflects on the process and suggests ways to improve it
KE Team
Day One (Monday, 18 June) Part III
  • In plenary at end of day all workshop participants are asked to identify/choose one of the 8 KS themes in which they have had experience. The two 'most popular' themes are chosen. (Method to be determine)
  • The KE team asks for volunteers with experiences in one or both of those themes to contribute to the KE's work by telling their stories and having them recorded during the end of the day
  • Guiding principles: Consider time limits and condensedness to make the burden of the ocumentation more manageable. Do both record and ask people to take notes into a template (see template provided by Victoria in KE Dgroups resources: [1] Each voice recording could have a word document template associated with it which will make the documentation easier to draw on later. Stories to be told not to a plenary as a performance but set it up so it feels like one individual telling it to another.
All
Day Two (Tuesday, 19 June)
  • A third party retell some of the chosen materials at the beginning to have a sense of

carrying the actual raw materials through and reincorporating them into the day.

  • KE Team exchanges ideas on the interview process
  • KE team exchanges content looking for common threads, approaches or tools in addressing the challenges
  • Linkages to the KS curriculum project are made
KE team and Curriculum team
Day Three (Wednesday, 20 June)
  • Documenters present the rough outline of the KE product
  • Discussion on how we can learn better from experiences and stories of others and specifically on how we bring in the stories into our own organisations or networks
  • Conceptualisation of KE beyond KM4Dev 2007
KE team