Monthly Archives: February 2009

Keeping It Visible: The Joys of Offline Organization

Keeping on top of the daily multitude of tasks we all have in our work is like having another full-time job. There are a number of tools available to the most casual computer users, from the tasks and to-do lists in Microsoft Outlook, to Apple’s Project X, to a variety of Web programs like blist.com and Zoho. In IDD, keeping up with the dynamic nature of the academic environment is especially challenging. Anyone stepping into my shared workspace in the IDD offices at the DePaul Center will quickly notice my own low-tech yet cutting-edge (I think) solution to task management: sticky notes and a wall.

It looks something like this: there are three columns of stickies, each headed by a large note which categorizes that column. “Upcoming Tasks” in the left-most column, followed by “Current Tasks” in the middle, and “Items for Inspection” on the right. Projects or tasks that I need to complete, but which are not a priority today go in the “Upcoming” column. Those things I am working on today belong in the middle. If a project is large, I break it up in to smaller pieces that can be completed more quickly. Those finished projects, or tasks that require the review or “inspection” of others to be considered complete, go under that last large sticky.

Though I’d like to, I can’t take credit for this system. I first learned of the sticky-note revolution from my husband, an agile process-management consultant who teaches the sticky-note idea to teams in a variety of fields, from software to education. What the sticky notes do for me is help keep my workload visible to me and to anyone who needs to know what I’m working on and the status of those projects. At a glance, my colleagues can see where my efforts will be focused on a given day, and this knowledge facilitates ready discussion. The portable nature of the stickies also allows me to reprioritize my work each day. I can reach up and peel off a project under the “Current” heading—perhaps a course that has been shifted to future quarter—and replace it with a new, more immediate task. Should I run into a problem with a task, or need more information in order to complete it, I add a “flag” sticky to that task. Flags are a bright color and list the issue to be resolved. They are removed when the impediment is. Of course, the act of moving a completed task to that finished column gives me a boost in a very real, tactile sense which helps keep my motivation to continue on to the next task.

Adapting the sticky note system to my work in IDD keeps me organized, but also flexible, adaptive and motivated to move that next sticky into the “done” column. I love a good Web app as much as the next person, but I also appreciate simplicity and ease with which I can keep myself organized with just a few adhesive note and a good black pen.

Student Toolkit

Here at DePaul, we have the DePaul Online Teaching Series program (DOTS), where we work with faculty to help prepare them for the unique challenges of teaching online. It’s an intensive program that begins with a crash course in designing an online or hybrid course and goes all the way through working with a design consultant to get the course completed and evaluated.

In order to help the faculty effectively accomplish this, we give them the tools they will need to create their course, including a laptop computer, a webcam, a headset microphone, software, and a portable voice recorder. Doing this ensures that they have all the technology they will need to produce a robust, dynamic, and interesting course.

I received a phone call today from an instructor who went through the DOTS program asking about what resources were available to a student who wanted to produce videos to submit to the class. This got me thinking about the aforementioned technology toolkit we give to faculty. At what point will the students need a similar toolkit?

A great deal of focus in course design is often placed on creating instructional materials for the students to consume. For example, they watch a video, read an article, or view a Web site. There is not much focus on student-created content—regardless of whether it is eventually offered up for assessment. The majority of the time, students interact with the material through writing a paper, posting to a discussion board, or taking a quiz.

However, what happens when an instructor would like to send off her students to create materials for assessment similar to what the instructor can produce for the students to consume? Where does a student, especially an online student, obtain the required video camera, microphone, or editing software?

This thought process, combined with a conversation I had the other day about technical requirements for online students, made me wonder if we will see not only tech specs for computers for students in the future, but also what they will need as peripheral devices in order to succeed as a student in an increasingly visual and technical world.

I can’t wait to see where this may lead.

Wikis, We’ve Got Wikis Part II

In my last post, I gave quick overviews of PBwiki, Zoho Wiki and Google Sites. This time we’ll look at three others: Wikispaces, Wikidot, and Wetpaint.

 

Wikispaces

wikispaces.png

Things I like about Wikispaces:

  • WYSIWYG editor is a breeze; love the preview function.
  • Easy to add widgets.
  • Extensive default widget list with video, audio, calendar, spreadsheet, polls, RSS, chat and IM, slideshows, map, bookmark, and custom html plugins.
  • Easy to add a logo.
  • Easy to invite users with a personalized greeting.
  • Built-in user statistics, with an overview and breakouts by members and pages.               
  • Wikispaces badges, which let you easily place a graphic link to your wiki on any Web site. There’s a live-changes badge too.
  • Fairly logical information architecture; easy to find the settings you’re looking for.

What I don’t like:

  • Advertisements on right pane of page. You have to pay to get an ad-free version.
  • Free versions can’t be private; public wiki can be viewed and edited by anyone, protected can be viewed by anyone but edited only by invited users.
  • Private wikis start at $5 per month; custom-permissions functionality starts at $20 per month.
  • Limited, cheesy selection of free skins.
  • Logo size limited to 150 x 150 pixels.

I really want to like Wikispaces. I think the WYSIWYG editor, selection of widgets, and built-in analytics are great features. I don’t like the limits of the free versions; the permissions settings don’t give you enough control over users and access. Aesthetically, the free Wikispaces are a disappointment; if you prefer to have a customized, professional appearance you’ll probably want to go with a paid version to get more functionality. This isn’t a bad free wiki; but it’s not at the top of my list.

 

Wikidot

wikidot.png

Things I like about Wikidot:

  • Mathematic equations on the page—a great feature for educators.
  • Bibliography block and citations feature.
  • Custom code can be easily displayed on the page.
  • Free version has customizable permissions settings.
  • Forum and per-page discussion features.
  • WYSIWYG editor has a preview function.
  • Decent selection of free skins, fairly wide variety.
  • Customizable CSS.
  • Active support community, extensive catalog of wiki code snippets for page customization.
  • Google Analytics.

What I don’t like:

  • WYSIWYG editor is kind of kludgy, more an html editor than a Word-type WYSIWYG.
  • Not as intuitive as other wikis.
  • Plugins hard to find or nonexistent.
  • Have to customize CSS to include a logo.

Wikidot is not the most intuitive wiki to use, but its ability to display mathematic equations, programming code (javascript, html, etc) and academic-text formatting like bibliographic information and footnotes makes it a smart choice for educators. It’s a bit short on easy multimedia features (you won’t find a drop-down of easy-peasy plugins, for example), but with its ability to customize look, feel, and access it’s worth a look for tech-savvy users who aren’t easily discouraged or intimidated.

 

Wetpaint

wetpaint.png

What I like about Wetpaint:

  • Easy, intuitive WYSIWYG editor.
  • Nice selection of multimedia widgets: video, messaging, maps, slideshows, video mail, etc.
  • Multimedia search and embedding is a breeze.
  • Add photo feature makes uploading images, searching Yahoo images, or adding a slideshow easy.
  • Customizable permissions setting.
  • Spellcheck!
  • Add An Edit note feature: leave a description of your edits and/or contribution. 
  • Discussion forum.
  • To-do feature.
  • Google Analytics or SiteMeter for site statistics.
  • Wetpaint Central, a resource-rich online help and support community.

What I don’t like about Wetpaint

  • Limited range of free skins.
  • Can’t customize page layout.
  • $10 – $15 monthly to get an ad-free wiki.
  • Feels a little impersonal.

It’s hard not to like Wetpaint. It’s intuitive, with lots of thoughtful features like spellcheck, discussions, and Google Analytics. And it can’t be beat for multimedia ease of use. For example, you can search for and embed a YouTube video directly from the Add YouTube Video dialog box. No need to leave the wiki, go to YouTube, find the video, copy the code, and then return to and embed the code in your wiki. My complaints are few: I’m not crazy about the aesthetics, and I think the ad-free price is a little steep. However, Wetpaint is extremely easy to use, it offers customizable permissions, and its rich multimedia feature set makes it a good bet if you plan to use lots of video or Web 2.0 apps.

Avatar photo

Just Because They’re Young Doesn’t Mean They’re Tech Savvy

A professor I work with recently decided to use Ning to create an online social network for a course. Like Facebook, Ning provides a space where users can communicate and share links, images, and videos. However, Ning allows instructors to create a space that is used exclusively for course-related collaboration and is only accessible by their students. This increased level of privacy and focused purpose helps everyone involved maintain boundaries between their academic and personal lives.

Shortly after the course began, the professor noticed many of her students were having trouble with basic tasks such as uploading images, embedding YouTube video clips, and writing blog posts. The professor told me, “I have a blog and I’m almost fifty. I was shocked that my students have no experience with blogging.” I wish I could say I was as shocked as she was. Unfortunately, I know this problem all too well and I’ve been writing about it periodically for the past year. Back in February of 2008, I wrote a post about the importance of defining computer literacy. My major complaint at that time was the lack of agreement on a minimum technology literacy level for college students. The lack of computer-literacy requirements and classes to support students who don’t meet such requirements places an unfair burden on faculty. Professors who wish to use new technology in their courses wind up serving as tech support for students who lack a fundamental understanding of interactive media.

Back in November, I also wrote about the misleading stereotype of the tech-savvy millennial learner that I hear about so often at conferences. As much as people love to refer to today’s twenty-something college students as “digital natives,” many of these students are more like “digital resident aliens.” They’ve learned just enough to get by, but ask them something that’s not in their phrasebook and you’ll quickly see how superficial their knowledge really is.

Sadly, the lack of a well-rounded technology education isn’t just failing students in the arts and humanities. Students pursuing technology-focused degrees are also suffering. An article in The Chronicle of Higher Education recently noted that many Web-design instructors are not preparing students for the demands of employers in the field. In “Colleges Get Poor Grades on Teaching Web Fundamentals,” the author cites a survey developed by Leslie Jensen-Inman, an assistant professor of art at the University of Tennessee at Chattanooga. Jensen-Inman interviewed thirty-two professional Web designers and discovered that universities are either encouraging students to overspecialize in a particular piece of software or programming language or teaching outdated tools and techniques that are no longer relevant in the working world.

As a part-time Web-design professor, I found this article vindicating, because it supports my belief that students need a broad range of up-to-date knowledge to become successful designers themselves. In addition, I think the basic skills and knowledge that aspiring Web designers need are becoming increasingly essential for all college students. Knowing how to manage digital files, maintain a blog, participate in an online discussion, embed media in a Web page—these are all skills that will prove valuable no matter what a student’s career aspirations might be. Now we simply need to recognize that this knowledge won’t reach critical mass by osmosis. Hundreds of hours of Wii Tennis or text messaging or Twittering might do a lot to reduce technophobia in a new generation of students, but it doesn’t necessarily increase their understanding of how interactive media works and enable them to transfer knowledge from one tool to another.

Many instructional designers might disapprove of the idea that we should relegate new-media education to a single “Technology 101” course. Instead, they often support an integrative approach in which technology is used across the curriculum as a means to an end for a variety of disciplines. I agree that it’s wonderful to see faculty using technology to improve learning in a variety of subject areas, from philosophy to chemistry to mathematics to the fine arts. However, I think attacking the problem from both sides could help ensure the push for technology integration doesn’t always come from the top down.

A Technology 101 course could help ensure today’s students can live up to the tech-savvy stereotype we’ve already forced upon them. With a little support from the bottom, we might finally see more students pushing faculty to use new tools and helping instructors improve their technology literacy. Until then, I’m afraid we might be stuck in an inefficient, reactive model that attempts to support students once assignment deadlines are looming and panic has set in. This approach is a bit like asking students to drive cross-country after giving them the keys to an eighteen wheeler and an 800 number to call if they have questions as they’re barreling down the highway. Will some of them make it? Sure. But a little driver’s ed up front could prevent a lot of disasters down the road.