Like many people have
commented, it’s been enjoyable, surprising and gratifying to see what we
produced in this activity.
And in the end we have
a co-authored document amongst many people within a tight deadline, so whatever
we did has worked.
That’s great and it’s
been fascinating to be part of the process.
For myself, it’s also given me a lot of
food for thought, and I’ve been asking myself whether we’d do it the same way
next time or do anything differently.
Some of the things
I’ve been asking myself:-
· Spontaneous
/ fluctuating leadership roles.
I really like the fact that we didn’t replicate the classic project management
structure by nominating a single coordinator. Coordination roles seemed to move
from one person to another at different times quite spontaneously. I enjoyed that,
but I also noticed there were points of confusion and a lot of us felt a bit
lost at times – would we adopt the same approach re ‘spontaneous leadership’
next time, or would we do anything differently?
· The
proliferation of threads was hard to manage. It was really hard at times to know which thread to follow – David A’s
reclarifying of deadlines was a big help, and Nicola’s ‘STOP! LOOK! One place
Activity 15!’ thread was also quite a relief, but even then we all continued to
post to a lot of different threads. Would we do this differently another time?
· Final
editorship rights. We had no-one
owning final editorship rights – was this a problem? Did we produce the best
document this way? (I’m really happy with the final document, but I felt quite
involved in producing it – I wonder if we all felt the same way?)
· Inclusion
/ leveraging the whole team. Did
everyone feel as involved and connected, or did some people feel excluded?
Timing-wise, I know if I am late to join an activity it is very demotivating
and difficult to join in. I’ve been asking myself if group dynamics require
ways of positively reaching out to people joining at different times to get
involved.
· Is
synchronous communication the best approach? We seemed to embrace opportunities for real-time, synchronous communication
(Elluminate or the chat function in etherpad). For a small team that is
understandable, but if part of the power of groupwork on the internet is to
involve large groups of people (hundreds or thousands?) then don’t you need to
have ways of managing asynchronous communications in a way that people equally
appreciate? I wonder how open-source programmers like those involved in Linux
and Moodle do it.
· Coordinating
with the whole cohort. Felt to
me like this didn’t happen much at all – our thread in Student Café didn’t
attract much interaction. Could we do this a different way next time?