July 2009 Archives

VoiceThread Adoption: That was Easy!!

| 0 Comments | 0 TrackBacks
Implementing VoiceThread in an Online Class..in 2 Days!
About a week after we released our Hot Team white paper on VoiceThread, I received a request from a faculty member, Evelyn Thomchick, in the Smeal College of Business about it. She has been teaching an online Supply Chain Master's Program course and had recently assigned her class a Negotiations exercise.  She had created 12 teams of 4 to engage in a negotiation where each team represented either 'Raymark' or 'Sentor'. She gave basic case study information about each company, including scenarios for each. She paired the teams off so that Team A negotiated with Team B, Team C negotiated with Team D, etc. In all, there were 6 total negotiations.

The Negotiation Post Hoc Analysis Assignment
By the time Evelyn had contacted me, the students had completed the negotiation exercise (the students used negotiation forums and chats within ANGEL).  She had asked each team to submit a 3-4 slide powerpoint presentation that provided an ad-hoc analysis that covered:
  1. Did your team meet your objective(s)?
  2. Did you follow your strategy? If not, how did it change as you proceeded?
  3. Why did you reach a successful out come or why did you not reach a successful outcome?
She was receiving each team's powerpoint when she reached out to me about possibly using VoiceThread. Her original thought was to have an Adobe Connect session with each team but she was realizing the major scheduling issues for a synchronous meeting for students in this online class. It was at this point she read about VoiceThread reached out to me. She primarily liked the idea that feedback could be provided in an asynchronous environment within a presentation user interface.

How She Used VoiceThread for the Assignment
On a Wednesday, we met at Starbucks to discuss her assignment and the possibility of using VoiceThread. Evelyn quickly grasped how VoiceThread would work and the advantages of it for this particular assignment. By the end of the meeting, she had decided she would do this:
  • She would take the powerpoint slides from each of the teams that negotiated with each other and put them in one VoiceThread presentation. To illustrate, she had Team A and B negotiate with each other. Team A and B sent their ppt slide to Evelyn and she then uploaded the 4 slides from A and 4 slides from B into one VoiceThread.
  • One this 8 slide presentation was set up, she assigned the 4 individuals from Team A and the 4 from Team B to that particular VoiceThread. This way, each team could read the other team's post hoc analysis.
  • She would then give each of the 8 total individuals three days to review the combined analysis and make comments in VoiceThread.
  • In all, she had 6 pairs of teams so she ended up creating 6 separate VoiceThreads
As I said, we met on a Wednesday. Later that week (Friday), Evelyn had uploaded all ppts and assigned them to students. By Monday, students were adding comments.  I asked her to give me access to the VoiceThreads just so I could see how this assignment went. I didn't think much about it until I realized that Evelyn had decided on a completely new technology tool to handle an important class assignment only 4 days before it needed to be up and working!

Results
For the most part, students were also able quickly able to get into VoiceThead, review the slides and make comments. Most of the comments were in text, especially the first day or so. Later, other students started making audio comments via microphone. The bottom line is that the students did indeed engage in conversations via VoiceThread and the feedback was meaningful. There were a couple of small hiccups with some student's access to VoiceThread but they were quickly resolved.

Overall, I think this experience demonstrated the ease of implementing and using VoiceThread, both for faculty and students. Evelyn felt comfortable enough with it to make the decision to use it over the course of a one hour discussion at Starbucks (no, I did not use my P-Card). Even more impressive is that she was up and running 2 days later. And she did this with little to no input from me for getting things set up beyond our initial meeting at Starbucks!

Example VoiceThread from the Assignment
I've embedded one of the VoiceThreads from her assignment so that you can get an idea of how this assignment ended up functioning. If you do not yet have a VoiceThread account, click Register! to create a quick account for free. This should take you less than 30 seconds (VoiceThread does not require a lot of profile information to start).


My last two blogs were all about our exciting work completing the VoiceThread white paper, "7 Things you Need to Know about VoiceThread."  With a nice feeling of accomplishment and pride, I felt good about the quality and uniqueness of our work.  Until this past Tuesday. It just so happens that the Educause Learning Initiative released their version of a white paper on VoiceThread. Initially, I felt a bit of the wind come out of my sails at this strange coincidence. But then I realized that we were the ones who accompanied our white paper with a real VoiceThread!  So yes, ours is officially cooler because of that alone. 

I'll let you decide for yourself on which is 'best' but I think this coincidence underscores some of the momentum of VoiceThread in education.

PS- Vote for ours.
As I mentioned in Part I of this blog, this was my first experience leading a hot team. I thought I'd share some thoughts on the team, a bit of our process and some interesting 'extra' information that I thought I'd share.

Our Hot Team
Luckily, I was made a part of an excellent team for this project that was engaged and worked well together. Just as a recap, our Hot Team consisted of:
  • Dan Berman
  • Cathy Holsing
  • Chris Stubbs
  • Kim Winck
Dan was, until Tuesday, an associate professor of Classics and Ancient Mediterranean Studies (CAMS) at Penn State.  Dan is leaving Penn State for a new position at Temple University.  Dan was on the team because he had actually taken the great leap and used VoiceThread for his online Roman archaeology course. As far as I know (which often isn't much), he is the only instructor to use VoiceThead so far here at PSU. It was great getting to know Dan during this project and I hope to stay in contact with him. Even though I am new to State College, it turned out he and I have a common contact in Garrett Fagan, another associate professor in the CAMS department. Ironically, Garrett is my next door neighbor. But since Dan is moving, I guess I won't see him at the cookouts this summer!

Cathy is a Senior Instructional Designer in Outreach and Online Education for the College of the Liberal Arts. I met Cathy on the Grassroots video Hot Team and she had worked with Dan to setup his VoiceThread for the Roman archaeology class.  In fact, it was Cathy who had presented VoiceThead at an ID meeting earlier this year that gave birth to the idea of doing the VoiceThread hot team. Cathy is wonderful to work with and since we've been on two teams together, I may request her for all hot teams that I participate in.

Chris is a resident instructional technologist here in ETS. At least, I believe that is the title he should have right now. Chris was the 'technology guy' in our group and helped us seek out the critical technical information during our research period.

Kim is in Video Production and Design for the Digital Commons. I first worked with Kim during the Biology 12 project this spring and was glad to have her expertise on hand. Kim really put VoiceThread "through the ringer" from a usability and content creation viewpoint.

A Bit about Process
The team met once a week for almost two months. We explored with the tool as well as researched what others were doing with it. We kept all notes and documents in Google Docs, which works fabulously for such a collaborative writing project. As interesting as that part of the process was, the project became a lot more fun when we started contacting external resources for information (see below). These conversations were key to a deeper understanding of the tool and, perhaps more importantly, allowed us to build some nice relationships.

Obviously, the most unique part of this project was our hot team creating its own VoiceThread, or as we called it, a 'Hot Thread'.  While most of us have written a paper, how many can say they created a VoiceThread? We had limited time to develop it but the creative process was still fun and definitely helped keep the team motivated toward the end of the hot team process.

Speaking with Sources: University of North Carolina and VoiceThread co-founder
In researching VoiceThread, we were able to make some great contacts at the University of North Carolina where they have integrated VoiceThread into their technical infrastructure. Kathleen Kyzer and Suzanne Caldwell were our points of contact and they couldn't have been more pleasant and open to talk with. They are in the ITS Teaching and Learning Center Center at UNC. We provided them with a list of questions in Google Docs and shared it with them.  They replied into that document and then joined us for an hour-long conference call for further discussions.  That conversation was very insightful for all of us on the hot team. Here is the document we shared with them if you are interested.

We also got in contact with one of the cofounders of VoiceThread, Steve Muth. He was great, responding to our requests almost immediately.  Take a look at his direct answers to our questions. I found him very approachable and forthcoming with information. Dan had been in direct contact with Steve when he was developing his VoiceThreads and he remembered Dan quite well (for good reasons, mind you). He had also worked closely with our contacts at UNC during their VoiceThread custom implementation.

If we need to dig deeper into the use of VoiceThread in the future, you can bet we will be contacting Kathleen, Suzanne and Steve!

One last artifact: If anyone has seen enough of the VoiceThread information to be interested enough to try it out, we found this well done Educator's Guide to VoiceThread. It's from Michelle Pacansky-Brock, Director of Online and Hybrid Support Center at California State University.  She was an enthusiastic early adopter and user of VoiceThread. It's a very good 'Getting Started' guide for anyone ready to give VoiceThread a real try within a course.
I have just completed my first experience being a Hot Team lead for developing a white paper here at ETS. As I blogged back in May, our topic is VoiceThread and we have finally completed the white paper titled "7 Things you Need to Know about VoiceThread". I hope you blog readers will give it a quick read (it's only 2 pages) to learn about this unique new tool.

If you would rather go right to the fun stuff, we also started our own VoiceThread that gives you a real sense of how it works and what you can do with it.  We called it our "HotThread". I have embedded the VoiceThread here on this page for you to enjoy- simply click on it to begin. I invite you to make a comment in this VoiceThread to get a real sense of this tool's ease of use.

OR, if you prefer, you can view the full screen version from this VoiceThread webpage.

The VoiceThread Hot Team's "HotThread"



If you find VoiceThead interesting, I suggest visiting VoiceThread and learning more about it. 

In Part II, I will provide some details of the Hot Team experience as well as some additional background information on VoiceThread.

Search