Difference between revisions of "Documentation:At-Event"

From Facilitation Wiki
Jump to navigation Jump to search
(Created page with "=== Documentation Checklist: At the Event === Who is involved: * Facilitator * Documentation lead * Note takers (co-organizers; or participants, taking turns, not more than o...")
 
 
(12 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
=== Documentation Checklist: At the Event ===
 
=== Documentation Checklist: At the Event ===
  
−
Who is involved:
+
* At start of event: explain notes/documentation model
−
* Facilitator
+
** Set expectations regarding shared responsibility for note-taking
−
* Documentation lead
+
** Remind facilitators to ensure notes are captured in their sessions
−
* Note takers (co-organizers; or participants, taking turns, not more than once during the event)
+
** Explain how and when notes will be used and/or made available after event
  
−
Checklist:
+
* At start of session blocks during agenda
 +
** Documentation lead should verify who is taking notes in all sessions per time slot
 +
** Note takers should follow [[Documentation:Process for Session Types|notes capture processes based on the type of session]]
  
−
# Facilitator to explain notes capture model in opening circle
+
* After sessions: Documentation lead gathers session notes
 +
** Engage each note take to confirm submission of notes
 +
** Provide multiple options for submitting notes
 +
*** Email
 +
*** Upload
 +
*** Etc
  
−
# Documentation lead to follow at-event notes capture processes per session type
+
* Managing notes
−
 
+
** Documentation lead should post notes to main notes capture location on a rolling base, in collaboration with note takers.
−
Documentation process of the most popular session types
+
** When naming notes documents, it is advisable to follow file naming conventions, e.g.
−
 
+
*** AspirationEventNameSessionNameNotes.txt
−
* Agenda brainstorming
+
** Save notes in inter-operable, hopefully-open formats:
−
** Documentation lead and/or volunteering participants to transcribe post-it content in text document or speadsheet (as preferred by the organizers), taking each thematic column as a separate list (a bullet-point list on a text document; a column in a spreadsheet)
+
*** Text as .txt or .pdf
−
 
+
*** Images as .png or .jpg files
−
* Spectrogram
 
−
** Documentation lead to collect separately in different lists to be transcribed:
 
−
*** Read statements. And for each of these, take note of the approximate positioning of participants along the Agree-Not Sure-Disagree line and most relevant movements. E.g. "50% Agree, 10% Not Sure, 40 % Disagree; by the end of the debate, 50% Agree and 50% Not Sure".
 
−
*** Top level statements
 
−
*** Other statements
 
−
 
 
−
* Working session
 
−
** Before the session starts:
 
−
*** Facilitator to invite each group to have a volunteering note taker, taking notes on personal device or on paper, following the model agreed with event organizers (online or offline documents, etc.)
 
−
*** Documentation lead to ask each group at the beginning of the session to communicate the name of the note taker (for future reference and contact)
 
−
** At the end of the session:
 
−
*** Facilitator to remember note takers to share notes with the documentation lead
 
−
*** Documentation lead to verify that all notes have been collected, and, if anything is missing, follow up with responsible note taker to agree on collection method and timeframe (recommended: collect all notes by the end of the day the session has been taken place on)
 
−
 
 
−
* Skill share
 
−
** Documentation lead to take note of the titles of the skill share conversations taking place
 
−
 
 
−
* Speed geeking
 
−
** Basic documentation: documentation lead to visit each speed geeking station and take notes
 
−
** More detailed documentation: designate one note taker for each station, to take notes of the all the conversations taking place during all rounds
 
−
 
 
−
# Documentation lead to gather the session notes collected (either as text file, or picture of notes not yet typed up) accordingly to the Aspiration file-naming convention.
 
−
 
 
−
The Aspiration file-naming convention can have multiple parts:
 
−
* Aspiration, if Aspiration is the organization creating the documentation. Use the full name consistently to avoid sorting errors.
 
−
* Organizing entity or project. Write it capitalized or as acronym if longer than 10-15 characters.
 
−
* Name of the meeting. Write it capitalized.
 
−
* Name of the session. Write it lower case.
 
−
* Content type. Write it capitalized, e.g. "Notes."
 
−
* Number, if there is a series of files with same file name and file extension, e.g. multiple photos documenting the notes of the one single session. The first value is 01, then 02 and so on.
 
−
 
 
−
Example: AspirationABCDigitalRightsSummitspeedgeeking01
 
−
 
 
−
Please note:
 
−
Never use punctuation or spaces when creating file names
 
−
Always save pictures as .jpg files and texts as .pdf files
 

Latest revision as of 04:12, 28 July 2017

Documentation Checklist: At the Event

  • At start of event: explain notes/documentation model
    • Set expectations regarding shared responsibility for note-taking
    • Remind facilitators to ensure notes are captured in their sessions
    • Explain how and when notes will be used and/or made available after event
  • After sessions: Documentation lead gathers session notes
    • Engage each note take to confirm submission of notes
    • Provide multiple options for submitting notes
      • Email
      • Upload
      • Etc
  • Managing notes
    • Documentation lead should post notes to main notes capture location on a rolling base, in collaboration with note takers.
    • When naming notes documents, it is advisable to follow file naming conventions, e.g.
      • AspirationEventNameSessionNameNotes.txt
    • Save notes in inter-operable, hopefully-open formats:
      • Text as .txt or .pdf
      • Images as .png or .jpg files
Retrieved from "https://facilitation.aspirationtech.org/index.php?title=Documentation:At-Event&oldid=195"