Edited by Anna Greathead, Wednesday, 15 Jan 2020, 13:11
Not going to lie - I am finding this hard.
I see no reason to assume that the other four people in my group are slacking off - after all I disappeared for a week to go on holiday, there are days I don't do any OU work at all due to other commitments and sometimes my dipping into H817 is unfocused and little more than a passing glance. (Although one of them has been AWOL all week!)
That said - I am frustrated that we haven't really completed what we were supposed to. There was a flurry of urgency in the week - an online poll, a WhatsApp conversation, a Padlet was set up, emails were sent and then not much has happened collaboratively since then. I have done some things, including a Wiki document which could morph into the final project; but I am painfully aware that I can't do this alone and that I might be getting it all wrong! I'm even paranoid enough to have wondered if the others have set up a separate group from which I am excluded due to my evident ineptitude!
Collaboration is clearly a good thing. I don't think there is any real argument about that. But collaboration between people who are complete strangers, living in different times zones to one another, all collaborating in their spare time and with a ague brief as to what they're aiming to achieve is, let me assure you, hard work!
So here's my check list of what would make this task easier!
1. Everyone participating from the beginning. At first there was a lot of waiting around for all of the group to join in. In hindsight this wasted the first half of the week. Whilst it's very democratic to want input from everyone before getting started it's impractical when you are unsure that everyone will give any input.
2. Clearly designed brief with examples. We are all new to H817 and (I guess) many people are also new to the Open University, Post Graduate Studies and MAODE too. The brief we had was hard to pin down. It would have been better if it had been more 'essay' structured - 'outline the strengths and weaknesses of a chosen technology and evaluate how said technology has encouraged innovation or represented innovation in e-learning. Use examples from your own and / or other contexts'. Having to create a scenario and agree on it took ages. If a scenario is what is needed for later than give us one!
3. Accept that contribution will be uneven and sporadic. Different people will be able to contribute to any project differently. One of our group set up a Padlet - great idea in theory but it was not immediately editable. I set up what I thought was a Wiki page which everyone could edit but it turns out to have been as secure as a bankers vault and I had to copy and paste it in an email to someone else to publish properly! I am most free on Tuesdays and at weekends. I usually cannot manage any study on Fridays. I imagine my group mates have similarly complicated schedules.
4. Use WhatsApp, Messenger or some other proprietary platform to communicate. Exchange email addresses. If I were to make one recommendation to the OU it would be to make the forums a lot more like a Facebook comments thread. I am literally on Facebook for my entire waking life. My phone is rarely more than a foot away from me and any and all Facebook notifications are seen within minutes. Ditto WhatsApp, Messenger, email. I open my OU page maybe once or twice a day. It's rare that an OU forum post needs my immediate attention but I could answer a query more immediately or ask a question and get a quicker response if it were more like Facebook. Our group WhatsApp group has been the place where most of our informal discussion has happened and from which we have directed one another to the work we've begun.
5. Try and replicate the situated group experience by exchanging the odd joke! A shared love of Red Dwarf (and red wine) led to a short but fun exchange. As a consequence I feel more connected to one of my group mates and therefore more able to effectively work with them.
6. Don't expect the situated group experience to be very similar to the distributed group experience I have concluded that asynchronicity is the key issue. We are working on the same thing but not at the same time. We cannot, therefore, be certain that we are sharing fully the aims, objectives, vocabulary and understanding necessary to produce effective work. There will be misunderstandings and there will have to be compromise.
Asynchronous Collaboration
Not going to lie - I am finding this hard.
I see no reason to assume that the other four people in my group are slacking off - after all I disappeared for a week to go on holiday, there are days I don't do any OU work at all due to other commitments and sometimes my dipping into H817 is unfocused and little more than a passing glance. (Although one of them has been AWOL all week!)
That said - I am frustrated that we haven't really completed what we were supposed to. There was a flurry of urgency in the week - an online poll, a WhatsApp conversation, a Padlet was set up, emails were sent and then not much has happened collaboratively since then. I have done some things, including a Wiki document which could morph into the final project; but I am painfully aware that I can't do this alone and that I might be getting it all wrong! I'm even paranoid enough to have wondered if the others have set up a separate group from which I am excluded due to my evident ineptitude!
Collaboration is clearly a good thing. I don't think there is any real argument about that. But collaboration between people who are complete strangers, living in different times zones to one another, all collaborating in their spare time and with a ague brief as to what they're aiming to achieve is, let me assure you, hard work!
So here's my check list of what would make this task easier!
1. Everyone participating from the beginning. At first there was a lot of waiting around for all of the group to join in. In hindsight this wasted the first half of the week. Whilst it's very democratic to want input from everyone before getting started it's impractical when you are unsure that everyone will give any input.
2. Clearly designed brief with examples. We are all new to H817 and (I guess) many people are also new to the Open University, Post Graduate Studies and MAODE too. The brief we had was hard to pin down. It would have been better if it had been more 'essay' structured - 'outline the strengths and weaknesses of a chosen technology and evaluate how said technology has encouraged innovation or represented innovation in e-learning. Use examples from your own and / or other contexts'. Having to create a scenario and agree on it took ages. If a scenario is what is needed for later than give us one!
3. Accept that contribution will be uneven and sporadic. Different people will be able to contribute to any project differently. One of our group set up a Padlet - great idea in theory but it was not immediately editable. I set up what I thought was a Wiki page which everyone could edit but it turns out to have been as secure as a bankers vault and I had to copy and paste it in an email to someone else to publish properly! I am most free on Tuesdays and at weekends. I usually cannot manage any study on Fridays. I imagine my group mates have similarly complicated schedules.
4. Use WhatsApp, Messenger or some other proprietary platform to communicate. Exchange email addresses. If I were to make one recommendation to the OU it would be to make the forums a lot more like a Facebook comments thread. I am literally on Facebook for my entire waking life. My phone is rarely more than a foot away from me and any and all Facebook notifications are seen within minutes. Ditto WhatsApp, Messenger, email. I open my OU page maybe once or twice a day. It's rare that an OU forum post needs my immediate attention but I could answer a query more immediately or ask a question and get a quicker response if it were more like Facebook. Our group WhatsApp group has been the place where most of our informal discussion has happened and from which we have directed one another to the work we've begun.
5. Try and replicate the situated group experience by exchanging the odd joke! A shared love of Red Dwarf (and red wine) led to a short but fun exchange. As a consequence I feel more connected to one of my group mates and therefore more able to effectively work with them.
6. Don't expect the situated group experience to be very similar to the distributed group experience I have concluded that asynchronicity is the key issue. We are working on the same thing but not at the same time. We cannot, therefore, be certain that we are sharing fully the aims, objectives, vocabulary and understanding necessary to produce effective work. There will be misunderstandings and there will have to be compromise.