On the topic of documentation (for community call)
I hope this is the best place to post it to, so people involved in documentation will see it before the community call.
If there’s a better place, please tell me and I’ll repost.
So first of all, thanks to @ireinga for kicking this off, I was frozen in “failure paralysis”, but now it’s better. I’d like to discuss the organisation (which I’d like to keep to the necessary minimum, to keep people most space, while still offering some kind of guidelines that could be helpful) of the documentation/harvesting, and thought it could be helpful if I layed out my thoughts about possible “how tos” before the call. So here we go:
What I’d do before LOTE:
Explain why documenting/harveting is important and valuable and invite people to document / collect what they learned/heared during the different sessions. It can be one person per session or several. If it’s more than one, they can be suggested TitanPad (which someone else would have to explain, please) as a way to work on the document together (unless they’re already comfortable using some other tools like google docs or whatever).
Explain different possible roles:
*day journalist, who captures the flow and what happened besides the sessions/talks
*mischievous question seeker
*whatever other way people come up with and feel called to collect"
Set up wiki with each session listen, for people to add their names to the session they will do documentation on. Take mail addresses to be able to follow up after event for collection of the material. (I have no idea how you did this travel wiki list, but I’d find it very practical for this matter. Can someone either teach me or set that up for documentation of the talks/sessions?)
Possibility to find out what questions people are moved by - what really brings them to the event? That would be a first piece of harvest. A first idea about what is already happening in the group.
Create Wiki, where the harvesting documents will be linked to afterwards, so everything can be found in one place, example:
Link to pictures taken
Link to posting “Records of session 1”
Records of session 2
Personal reflection pieces and harvest of the “collective sensemaking”
What I like about that is that the content can be found easily, but people can still engage on the topic of the session in the separate threads.
- Find last volunteers to document session that aren’t covered in advance.
Should work, I think. We don’t necessarily HAVE to know who’s the scribe for 100 % of the sessions. At least I imagine people will jump in spontaneously if needed. “Worst” case: maybe the speaker will be able to make a summary available? What do you think?
We’ll try to encourage some personal reflection, try to deepen the conversations by finding the questions in the room and harvest people’s insights on a personal level along the way. This will happen on the spot and is rather going to be planned about a week in advance. What can be thought about already are juicy questions
- Ask people to upload their harvest as a post on this forum (in a possible sub-section?) or on hackpad (mail addresses needed for kind reminders). Update Wiki with links in chronological order of talks/sessions.
My goal: Give all the explanations about the “how tos” in advance to not worry about it during event, because I will need space for the not-technology-based offline harvesting. Post it’s and stuff
Please tell me what you think. As I said, I’m not very techie, so I hope this will work in your eyes. If not, I’m looking forward to additional ideas.
“See” you on wednesday (I’ll join shortly after 11:30)