Social Network “Fail” Leads to A Renewed Approach to ENG 315

Another semester began this week, and I have been updating my syllabus and wiki site for ENG 315. Last semester, I was quite surprised and delighted by the number of you who asked me about my Wikispaces to Edmodo shift. Well, we learn from our failures, right? This is one that taught me a great deal about digital writing and teaching, and I share a few thoughts here.

First, I realized how dependent I had become on using a wiki, both to prepare for class as well as in class. Each week, I would create a new agenda page and share that with my students. While I could share links in Edmodo, I switched to a Google Doc for the agenda, and that was confusing to many students. In other words, I didn’t find an easy way to put a weekly agenda up and — while I had placed a link to the agenda in Edmodo, asked them to save the doc in their own Google Drive, and sent a link out each week — the document itself became overwhelming. There may have been an easy workaround for this, however that was not the major concern that students had.

Second, I populated our course’s feed with two RSS feeds so they could get updates on educational news and events. There were so few posts from class members in between our regular class meetings each week, that these syndicated RSS feeds would essentially “fill” the front page for the class. Students were not interested in or easily able to search for assignments or posts from their classmates. Again, I could’ve turned off the RSS, and I’m sure that some simple tagging and searching skills would’ve made this a moot point, that it was something that bothered students in a way I had set up our Edmodo course.

Finally, when I would go to use Edmodo in class as a way to take notes on course discussions, or invite them to post a piece of writing, again there seemed to be no convenient way to do this. I could take notes in the Google talk and make a link, or in a post, but that seemed to get lost. Also, when I had students write in class and then post to the wall of the Edmodo course, again became quickly filled with posts and made it difficult to see everything directly.

For each of these problems, I’m sure that I could’ve figured out a way around them, and I know that Edmodo recently released an update as well, so perhaps on these issues would be less of a concern. However, for me and the preservice teachers with whom I work, it just wasn’t the right fit. So, this semester I am definitely going back to a wiki and I will be more intentional about the times we use the wiki as compared to when we choose Google docs.

The other good thing about my “fail” is that it has coincided nicely, or at lease given me a great deal of material for, my experience in the High Impact Teaching Academy that I have then participating in at CMU. Once a month, a group of about 10 faculty, graduate students, and a facilitator from our faculty development center have been meeting to discuss issues related to syllabus design, assignments, implementing writing, assessment, integrating technology, flipping the classroom, and a variety of other topics.

The chance to talk with like-minded colleagues from disciplines across the university has been very valuable. Part of the work that we are doing this year is to create a product that demonstrates substantive change in our teaching practice. I am approaching ENG 315 with a renewed focus the semester, and have created two artifacts over the break that I shared during our first week of class: a “visual syllabus” and this Prezi that outlines my vision for the course. And, I will be moving back to a wiki… so I will share more about thinking later in the semester.

Good luck with the new semester and thanks again for sharing your feedback. A number of readers have told me that the comment features on the blog have not been working properly, and I ever moved a number of plug-ins so hopefully commenting will be much easier.

Creative Commons License This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.

Add Comment Register

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>