PART A - Brainstorm Session

For the kick-off to our Group Leadership Project, we (Team4Tech) chose to meet using Adobe Connect.  We chose this tool because:

• We were all familiar with it already.
• It was free to us (since MSU has an account).
• We were able to have our professor set up our meeting, as well as help us get started, making a successful session more likely.
• It offered an easy way to record our conversation both via microphone and via chat.  

During the development process, I was able to note some additional features of Adobe Connect that I hadn't before.  This was in response to difficulties I had at first.  I was struggling with a slower Internet connection as well as choppy audio and was limited to TYPING rather than speaking like everyone else.  These glitches resulted in feelings of frustration and disappointment.  I can honestly say that, for the first portion of our session, it was the WORST Adobe Connect experience I've ever had.  One feature that came in handy, though, was the "raise your hand" feature. When my group was busy talking and I wanted to call their attention to a comment I had typed, I was able to "raise my hand".  I also noted the "agree/disagree" options, as well as other generic responses, which I hadn't seen before.  

My experience helped me realize how frustrating it can be to feel "silenced" when trying to contribute to a group.  While I wasn't being marginalized by anyone intentionally, the lack of a fully functioning program made me feel like I was on the "outside looking in", which is a miserable place to be when you long to be involved.  This reminds me of when students don't have technology available (or have sub-par tools) at home and are left feeling further disconnected, rather than connected, by technology.  

While we were brainstorming, our group also used Google Docs to document our "plan of attack."  Thank goodness for Google Docs!  This tool was easy for me to access and the chat feature there worked much more efficiently, too.  Our plan came together nicely and it was really helpful to have a common, editable-by-all document to log our progress.

If I had to develop a similar product again, I might choose a different forum.  While this was our best option with our current circumstances, I found that being limited to a chat feature while everyone else had audio/microphone access left me feeling isolated more often than not.  I also found that I prefer having a typed chat so that you can actually READ what someone wrote if you missed what was said.  Plus, people can't speak over one another.  When I logged on the main decisions had already been made, but by reviewing the chat log all I could see was a few quick "hellos".  The full "meat" of the decision-making process had been verbal, so by not being present at that point (or able to hear), I had missed out and would have to wait to watch the replay to feel fully caught-up. 


I would prefer using a typing-based tool (perhaps even a group chat on Skype) so that everyone could quickly read key points & re-visit them as the discussion progressed.  A typed chat also means an instant "hard-copy" of what was said and eliminates the need to watch a recording to seek out verbal comments.

Thankfully, I have a great group that was able to pull things together effectively, but in terms of tools--while I still love Google Docs, Adobe Connect was less than impressive this time around.  

If you'd like to view our recorded Brainstorm session, click below:
http://breeze.msu.edu/p91777893/