Enhance your conference sessions using the session doc method

Enhance your conference sessions using the session doc method
0

(Christoph Haug) #1

I finally did it! I tried out what happens when the participants of an academic conference session share an online document and use it for joint note taking during the ongoing session. I have previously witnessed people in inter-organizational meetings share a Google document for note-taking and was fascinated by how well it worked.

31 jointly authored pages in 7 sessions

I then thought: why not use this in academic conferences where there is never enough time for discussion? As I prepared my paper for this year’s EGOS conference in Tallinn, I decided to give it a try. I contacted the session organizers and they agreed to give it a try. The result is a 31 page long multi-authored documentation of the seven sessions of the CCO subtheme program (at EGOS conference the participants in one specific stream of sessions stay together during most of the conference).

Part of what is in the document is a summary of what the presenters/papers said, part of it are questions and comments that were never articulated in the actual sessions (but in some cases addressed by the presenters after the session by responding to the comments in writing, in the document). People also provided quite a lot of useful references by pasting them into the document, sometimes after mentioning them during the discussion, sometimes without doing so. One colleague unfortunately had to leave due to a family emergency before being able to give her presentation. Thanks to the our session document, she nevertheless received some feedback from participants who had read the paper.

How the session doc changed our conversation

But all these 31 pages of content may not even be the most important result of the session doc method. I don’t know about you, but I rarely ever read the notes I write down at conferences or workshops - though when I do read them - often after one or more years - I’m usually very glad that I wrote that stuff down. So having that content written down and “archived” is potentially useful. But what’s at least as significant is how using the document changed the way we interacted during the conference. I’d actually like to study this more systematically, but here are some first reflections:

  1. My sense is that the document gave us a stronger sense of being a (micro-)community: we, the group who have so far discussed these things together and who are jointly producing this document. It’s difficult to explain, but I’d say that even the sound of people typing on their laptops during the session suddenly had a ring of “we are doing this together” in them. Because you could look at your screen and see what people are typing.
  2. In a way, the discussion already started during the actual paper presentation, when people where typing in their questions and comments. I believe this helped to create a sense of the key questions or core concerns regarding the presented research and, most of the time, those would then also be articulated in the actual discussion and it seems to me that this also increased the quality of the discussion.
  3. Seeing at least some of the potential comments/questions before they were voiced also provided valuable context for your own thoughts and potential comments. For example, it might make you realize that other questions/concerns are much more pertinent and interesting to discuss, so you hold back until those things have been addressed.
  4. As already mentioned, the document was particularly beneficial for sharing references and for sharing them not only with the presenters (as would usually be the case without a session doc) but with all participants.
  5. The existence of the document made it easier to keep oral contributions shorter and focused on the essence because you could always end by saying: “I’ll elaborate/give you a link/paste a reference” in the session doc". In other words, the available air time was used more efficiently by referring questions of detail to the shared document.
  6. Because questions and comments are directed to the presenter, it is usually deemed socially inappropriate for other session participants to respond to them. In our document, some questions were answered in the document before they were even asked aloud and many people commented on other participant’s comments so that the overall conversation had much less of the typical ping-pong character but was multi-vocal.
  7. I’m not sure if or to what extent the anonymity of the comments played a role, but it is conceivable that opinions voiced by senior colleagues are more likely to be challenged via an anonymous response in the document than in the face-to-face discussion. (More on anonymity at the end of this post.)
  8. The session document was referred to and used not only during the session but also during the breaks as a place where information would be exchanged and discussions continued, for example when a small ad-hoc task force was created during one of the sessions to explore the possibilities for “distributed data sessions”.

So how to set up a session doc?

  1. There are multiple online services that allow you to create shared documents. We used Google Docs. So: Go to docs.google.com and create a new blank document:
    image
  2. Give the document a name (Google won’t accept “untitled document” as a name)
  3. Click the Share button in the top right corner:
    image
  4. Get a sharable link
    image
  5. By default the link will only allow people to view the document. But we need them to have editing permission. So change the link settings to “Anyone with the link can edit”:
    image
  6. Copy the link and share it with you session participants.

Bonus:

  1. Since the original Google link is rather unwieldy, it is a good idea to use a link shortener of your choice (I used bitly.com) to turn it into something like http://bit.ly/EGOS2018-oursession. We had the link written on the whiteboard in our room during all sessions. On day two, it had been wiped off by the cleaners. During the first presentation, someone silently asked me (who was chairing the session) via the session doc to please put the link back on the board as not everyone remembered it.

Regarding anonymity
In Google docs, every user editing the document has their own cursor in their own colour with funny animal names on them, so everyone can see where in the document everyone else is. I first though that the reason why those cursors have animal names on them rather than real names was that people were not logged into their Google accounts (it’s not necessary for editing the doc), but it turns out that even logged in users are represented by random animals. This is just how Google decided to have it.

Beware, however, that this applies only to the editing of the actual document itself (what is written on the page). Comments (which can be added to any piece of text in the document) do bear the real name of the commentator (at least when they are logged into their Google account). This may be confusing at first, but I think it’s a good thing to have commentators properly identified because it allows people to connect the online comments/discussions with real people and talk to them about the matter at hand. This would not be possible if everything were anonymous. In fact, in our final session, people stated that they would have liked to be able to see the real names also on the editing cursors, but at least with Goggle docs, this is not possible.


Workshop: Group Interaction Frontiers in Technology
(Elise Keith) #2

This is exactly the kind of “we’re all doing this together” effect we work to achieve for teams using our software to run their business meetings. Collaborative note taking is so powerful! Love this experiment and would love to see more examples!

In the future, there are other online co-editing tools you might consider. Etherpad (open source) and Quip (not Google) come to mind. Dropbox Paper also works well. All of these get around some of the technical/privacy challenges you run into with Google and people who don’t have Google accounts.


(Mike van der Vijver ) #3

Christoph, thanks, very interesting experiment! How many people were there in these sessions? What is your estimate for the optimum and maximum number of participants to this kind of shared note taking?
Thanks!
Mike


(Christoph Haug) #4

I think most of the time we were between 20 and 30 people.

It’s difficult to pin down because it also depends on the nature of the session and what you want to achieve. So, to start with, let’s assume that the all the people who have access to the document are all in a friendly relationship with each other so that you can exclude the possibility of malicious manipulation of the document or disrespectful comments. Obviously, at a very large and anonymous session, you can’t be sure about that, but at academic conferences as I know them, I probably wouldn’t worry about vandalism even if the document were shared among all, say 1000 session attendees.

The question is, of course, whether editing is still possible practically, if you have even just 10 percent of those 1000 people actively editing the document at the same time.The thing is that in a Google document, for example, the text moves around on the page while typing/deleting, just like it does when you work in any prod processor.This means that if someone inserts an image or a larger piece of text above where you are typing, you may suddenly find yourself on the next page of on a different part of your screen.

We didn’t have any problem with that in our sessions, as we rarely had more than … hm, maybe 3-5 people typing at the same time. More people were contributing to the document, but not simultaneously. My estimate would be that problems may (!) start arising once your have more than 15-20 people actively editing the document. But how many session participants do you need in order to reach 20 simultaneous typers? It depends so much on the type of session and how many people even have a laptop or tablet with them? If I linearly scale up our session, I’m pretty sure that we’d not run into problems with up to 100 session participants and might still be fine well above 100. But there are so many unknowns in that estimate that it’s really just speculation.

I guess the only way to find out is to try…