KMSS03: What I have learnt by organising it
I wrote earlier that I didn't have much time for learning and networking during this summer school. I was wrong.
I didn't have enough time to do usual networking, so I missed some interesting people, but working together with others to organise this event allowed building deeper connections with some people instead of scratching the surface of "who does what".
Learning was different as well. I didn't learn much of the program (which is not surprising as I was involved in organising something during 3 days out of 5), but I've learnt a lot about organising a learning event like this one.
So, these are my lessons learnt. They are based on participants' feedback, organisers' debriefing and many one-to-one informal talks. Important conditions to take into account if you think about reusing them:
- This is a summer school, not a conference or a training course. We tried to balance some elements of both.
- It was organised mainly for young KM researchers (although we had enough experienced researchers and practitioners), so you can't rely on participants being active and confident all the time.
Team and process
We worked as a distributed flexible team; most of the program committee members were volunteers and we didn't have any "formal" leader. Most of us met during last year KM Summer School without knowing we will organise this one. After forming the program committee somewhere in beginning of 2003 we didn't have any single face-to-face meeting with all of us, but few people met each other on other occasions. We had to rely on e-mail (somehow threaded discussion didn't work), bi-weekly phone conferences and occasional phone calls. No conference management system, no document-sharing repository, no centralisation…
As some others I'm quite impressed with what we were able to achieve given these settings. But if someone asks me if I would do it this way again, I would say no.
It takes too much energy to achieve results in such a distributed network with no formal commitments (as a volunteer you can always have valuable excuses), no process/communication facilitation and no shared understanding/experiences of organising a learning event like KM Summer School 2003. Too many uncertainties altogether.
So I would work in a distributed network if there is a clear process and responsibilities or if there is shared understanding of how things work. The last one is probably most important: shared values, shared approaches, being on the "same wave" makes sure that you can work on achieving results and not on achieving shared understanding first.
Then there are some practical sides: using conference management system (e.g. free one like ConfMan or ConfMaster), structuring and capturing communication (ideally forum/wiki + file exchange server), a bit more centralisation and face-to-face contact.
Program, sessions, networking
- No presentations after lunch
- Be careful with several presentations in a raw; better think of something interactive in between
- Prepare inexperienced presenters (ask them not to read their paper, focus on few most interesting issues, provoke discussion)
- Ideally make parallel sessions with inexperienced presenters (the risk of getting the whole audience bored is too high :)
- Make more time for questions
- Do background negotiations with "talking too much" people, so they give more space to others to comment
- May be writing down questions on paper can work to give space for more people to ask questions
- Make sure results of small group work are presented
- Do not leave group work for self-organisation, structure the process (and leave more time at the end to continue with self-organised discussion)
- Provide group process facilitators if possible
- Find ways to involve everyone and not only "leaders" talking (e.g. asking everyone to brainstorm on paper first and then discuss results in a group)
- Give reading materials in advance and then don't rely too much on people reading them
Socialising and networking
- Make sure there is a bar/restaurant in the hotel ("common space" in the evening)
- Make sure there is a group of people initiating "having dinner together", so people without established network can easily join
- Longer breaks (at least 30 min)
- Write countries on badges
- Support finding each other by interests
- Scaffold active position (this is a separate topic which I hope to address one day)