Tag Archives: ideas

Instructional Technology

Tell Me a (Digital) Story

This year, I’ve heard more about ‘Digital Storytelling’ than ever before.

I had faculty members ask me about it (can we do it? how? is anyone else doing it?). I’ve seen presentations on it.

Is it weird that I didn’t know it wasn’t just a concept, but an actual structured *thing* until now? I always just thought that ‘digital storytelling’ was simply the use of certain media to convey a story. I thought it could be bent and crafted to suit the needs of a project. Unfortunately, it seems I was wrong. Someone owns the term, and has come up with a methodology. This is great for folks that like the structure, but it isn’t for me. I think Wikipedia might even be confused about this, as their description sounds more like what I thought it was. (Not to be negative about official “Digital Storytelling” – I simply want to describe my exploration of the topic)

So I guess I am not actually doing “Digital Storytelling”.

Not sure what to call what it is that I am working on with faculty who want their students to convey a story and make a connection using various media. Multimedia storytelling? eStories? Heh. Maybe it doesn’t need a name, we just have to actually do it.

So what exactly are we doing here?

1. Set a Goal

The Instructor really needs to define a purpose for this project (not just using technology for technology’s sake). Usually, it is to have the student convey a piece of their experience using various media (audio, video, photographs, text, animation). The message is really the most important part, and has to be developed before the technology comes into play. Consider whether the final project will be viewed by the Instructor, by the class and/or by the public – plan to discuss with the students how the chosen audience should influence how they develop their presentation.

Also keep in mind that students may be resistant to: a) being creative and/or b) using technology. Some students have got the paper writing down and are a little bit afraid of having to open up to a new idea. Some people are naturally more creative than others, or more comfortable with technology than others. All of this will have to be taken into account so that there is a level playing field for all students. This is why I’m focusing on the message – the technical and creative abilities should not overshadow the student’s ability to get the story across. A glossier video production should not automatically equal a better grade.

2. Develop the Stages of the Project

Work with the Instructor to outline the various stages of the project. In most cases, you will have: a topic submission stage, storyboard, final project. There may be other stages, such as a list of media to be used (photos, videos, sound that has already been collected, but not yet assembled). The following are some of the common stages of a project like this.

  • Topic Submission – have the students think about the topic and come up with the ‘story’ they are going to tell. This stage ensures the instructor can keep the students on point with the topic, before getting involved with the technology.
  • Storyboard – the students should start to map out what will actually happen in the sequence. This stage helps the student to prepare for what visuals, audio and text they will need to generate for the project. At this point, the student should have a good idea of what combination of audio, video, photography and text they will be using. They don’t need to actually HAVE it all at this point.
  • Media Collection – an optional stage that is really more of a check point for the student. Has the student been able to collect all of the media they need to complete the project? If not, what changes need to be made to the scope of the project? (i.e. if the student had a hard time getting particular video content, maybe they need to plan to use still photograhy instead.
  • Final Project – assembly of the media, possibly including transitions and motion to add some interest (or not), delivery of a final file in a specified manner (i.e. post to blog, post to Youtube, hand in on USB flash drive).
  • Class Presentation – Present in-person, in front of the class, describing the goal of the project and how it was achieved. Another alternative is to have a virtual presentation where the student posts the final “video” to a blog, and adds a couple of paragraphs of description. Comments from the class could be encouraged.

3. What are the rules?

I like to keep things as free as possible, as you might have guessed. The rules should be based mostly around the message portion, deadlines for creating certain phases (topic, storyboard, final project). I don’t think the rules should force students to use certain technologies/media, or restrict them – provided they are “getting the job done”. It may just be that the end format has to be web-ready, and must be in a format that can be posted to whatever delivery system the class is using (a blog, a Youtube channel, etc.). Generally speaking, text-only is not an option, as it doesn’t follow the spirit of the exercise.

4. What media/technology?

I think that the students should be able to choose from the technologies, based on what they have access to and their comfort with the technology. Some students will do amazing work with simple stills and text, while others may get hung up on adding too much “technology” and miss the point altogether.

Some students will have no trouble with this part – many have access to basic equipment (cell phones / computers that can record audio to WAV and video, etc, comfort with the software – maybe they’ve even posted to Youtube before). Other students will be uncomfortable with the technology and need some extra help finding equipment (recording equipment, scanners) and the software to assemble the final presentation (iMovie, Adobe Premiere, Windows Movie Maker).

We’re currently trying to assemble a list of what resources Ryerson students have, from borrowing equipment to editing in the computer labs. (*Note: Students should be aware that they will likely need an external USB hard drive to save their work-in-progress if working in a lab – they won’t be able to store their files there!)

5. What delivery method?

I think that posting the final “video” to a class blog would be a great option, because it can accommodate the various authors, media types, allow for some commenting, etc. We’re lucky enough to have a blog system at Ryerson that can house blogs that are public or private, so we don’t have to worry about sites hosted on servers in other countries. Another option is to have the videos posted on a public site like Youtube – there are pros and cons to a publicly hosted site, but other schools are doing it. A great thing about the blog option is that students could choose to post their video on Youtube and simply embed it into a blog post on our server.

So… at the end of my long post… this is the framework I’m working with right now. I’m sure this will evolve with more ideas and more input from different people. Whatever it’s called, I think it could be an interesting exercise for all of us!

More on this topic later.

Google, Instructional Technology, Personal Technology

1 Month of Wave: Post the first

I now have a Google Wave account.

I got it a few weeks ago, but haven’t really had the opportunity to try it out in a meaningful way. There’s no point in playing alone… Wave’s potential lies in the ability to collaborate with others. “Potential” is really the key word here. My first experiences with the features and user interface have left me hoping that it will evolve in the right way, but it does fall short in some ways.

What is a wave? It’s hard to describe… it’s like an enhanced wiki tool that you could use in place of email, plus gadgets.

Actually, it’s much more complex than that, especially once you start taking into account the ability to make public waves (so now you have a public forum? a public blog?) and embed waves into other sites (like your existing blog).

This video explains the concept behind Wave pretty well (and it’s pretty funny, too). Also be sure to check the Google Wave Intro at the bottom of this post… it shows some cool features that will be possible in the actual release of Wave.

Can’t see the embedded video? Click here!

One thing to keep in mind is that it is in preview — not even in Beta! There are no guarantees that features will work (and, in fact, I’ve had some work one day and not the next), so you can’t really use it professionally yet. Many of us are just trying it out, to see what we think we can do with it, and provide some feedback on things that just aren’t working for us.

Things I like:

  • Wiki-style group collaboration on documents (asynchronous… and kinda synchronous)
  • The ability to embed tools like polls, map tools, conferencing, etc. (although I haven’t been able to try them all yet)
  • The ability to make your Wave public, and search public Waves on different topics. Very cool!
  • The ability to add things like Twitter into a Wave. Not sure I know what to do with it, but it’s neat that I can.
  • The group of folks attending Educause that decided to try using Wave for sharing conference notes and info… I’m TOTALLY spying on you all!

Things I’d like to see improved:

  • The total destruction of the darn “Done” button you have to click when you’ve made an update to a Wave. Doesn’t seem like a big deal when you’re testing Wave on your own and have a 2-line wave. When you are participating in a BIIIG wave that scrolls forever, and has various long replies, etc. the “Done” button is tricky to find.
  • Long complicated waves can be complicated to navigate. Not sure how to improve this, but I am finding it challenging.
  • Difficulty in locating changes to a Wave. I know there’s a green bar on the side. Doesn’t help if I have to scroll for 10 minutes to find it. Give me a ‘history’ page with a list of changes, like you’d see in a regular wiki. The playback feature seems like a cool idea, but has been useless for me so far.

There are other points, but I’ll save some for my next post. Overall, I do see its potential, and I hope that Google takes the feedback that they are given.

One weird thing that’s come out of this is trolling for account invites. I’ve actually had strangers ask me for a Wave account invite when they saw me post on Twitter that I had an account myself. Weird, no? Unless I know you personally or professionally, please don’t ask me. I want to use my invites to gather a group of people that I can test and collaborate with.

Can’t see the embedded video? Click here!

Some other first impressions:

This series is a (roughly) 1-month attempt to figure out what the heck to do with Wave, with some commentary along the way.

Instructional Technology

Idea Thievery!

Is it possible to steal ideas? Is it bad to steal ideas?

Whose ideas are they anyway?

OK, so I’m not looking to make big bucks by stealing ideas that other people initiated. What I’m really talking about here is the propagation of ideas in this big blogiverse that exists in the even bigger webiverse. As a blogger, I sometimes feel bad when something I post started as someone else’s idea. Maybe someone posted a great video (that I re-post), or someone posts on a particular topic that I reflect on and add to.

How is this supposed to work?

When it comes to instructional technology, I think it’s best when something sparks other discussions. It starts with one idea – and if it’s a good idea, or at least one worth talking about, we’ll start talking about it. Different viewpoints emerge, some posts refer to other posts that refer to other posts, ideas evolve, experienced people offer anecdotes… and then things happen! Isn’t that how it’s supposed to work?

So when you see me post about something I saw on someone else’s blog, it isn’t because I haven’t got ideas of my own… it’s because I want to remember what I read, and my thoughts on it, and I want to ‘pass it on’, so to speak.

Feel free to pass on any ideas you’ve found on my blog! Honestly, I’d be flattered to know that someone was reading, nevermind that someone was inspired to repost something I’ve blogged about!

Until next time…