So the thing about DIY tutorials is that even though the technology bar required to build them is pretty low, there are some back-end logistical issues that have to be navigated. When I decided I wanted to try these with some of my distance learning classes, I had to figure out how to create a locally hosted blog, and we ended up doing it in a way that hadn’t been tried before (using Drupal) so we had to go through some rounds of figuring out settings and styling.
Don’t get me wrong, this wasn’t a bad thing to go through for me, or for the library. And when colleagues wanted a similar tool, we were that much further down the road and had some good reasons to try a different tool. Still, when the goal is “I want to get a tutorial up” these kinds of barriers aren’t necessarily what you want to go through.
I realize that a local option wasn’t the only option – if all I cared about was putting up a blog for tutorials quick and fast there are obviously tons of options out there. But that wasn’t the only problem I wanted to solve. I didn’t just want to make tutorials myself, I wanted to do something that would make it easy for all of us to create tutorials and other instructional aids.
The issue of how to share the burden of creating instructional materials has been around for a long time. Learning objects repositories like MERLOT offer lots of options for teachers – the ability to borrow online instructional modules, and the ability to comment on and rate those tools. Shared tutorial projects like ANTS let librarians share tutorials, collaborate on prioritizing and creating tutorials, and also provide a social space to talk about tutorial-related issues. Here, locally, we have CLIP (Collaborative Library Instruction Project) which takes a good step in the right direction – making source files available and shareable, letting librarians share some but not all of the work of tutorial-building.
CLIP is just getting off the ground, so I don’t know what will happen there. But here’s the thing. Whenever I have talked to anyone involved with projects like these, or heard them speaking about the larger issues, they say the same thing – getting participation from educators is really, really hard. They spend a lot of time gathering the content for the repositories themselves, they have a core group of committed people sharing, but getting the concept of sharing — of taking the time to participate in these types of projects and communities – to be part of the normal workflow for teachers is super difficult.
My own experience with the Library Instruction Wiki (now offline due to basement server room flood) left me feeling pessimistic about that project’s stop reinventing the wheel tagline. I have come to believe some things – some things that got me thinking that instead of sharing the final product of tutorials, the way to go is to figure out ways groups of teaching librarians can share a process:
1. Teachers like reinventing the wheel.
This is something Jean Caspers said to me once, and its stuck with me because I think it’s essentially true. Not that teachers don’t want to borrow and adapt and take advantage of other people’s cool ideas and good work, but to really feel comfortable going into a classroom and teaching a group of students something, a lot of us need to feel like we’ve made the stuff we’re teaching ours. And the only way to do that is to adapt, and reshape, and refine. So we don’t want to just point to other people’s handouts and tutorials (sometimes we do, but go with it). We want to make them ours.
And an important part of the cognitive process that a lot of us go through preparing to teach is preparing the materials. I know that when I create a course page for a class, I’m thinking about how I am going to present the material in class, and about how I am going to transition from one topic to the next. And when I make a tutorial for an online class, I want to tailor it to their assignment, and the process of putting it together helps me clarify what they need to know/do for that assignment.
So, it’s not a bad thing that teachers want to reinvent the wheel, not at all. And I think it’s a need teachers have that should be considered by anyone trying to help them work collaboratively.
2. The hard part of developing tutorials isn’t technical, it’s in the content. And that’s the hardest piece to share.
One piece of this is practical – try teaching anyone how to do anything research-related on your campus and see how long it takes before there is some local quirk that you need or want to explain. It doesn’t take long. There’s a reason why the tutorials we’re most likely to share are on topics like plagiarism or citations — things where we are all working on basically the same standards and rules, defined outside of our local institutions.
One piece of this is related to the above point. We want the content to be tailored to the students’ needs – we have strong opinions about how to do research and about how to teach it and about what students need to know about it. I don’t know, I haven’t talked to many people who say things like “I would totally borrow X’s tutorial, but it’s built in Camtasia and I would rather it be in Captivate. The people I talk to are more likely to forgo borrowing a tutorial because they don’t like something about it — they’d like to change the way it explains a concept, or to add just one more piece.
3. There is one sure-fire way to make the technical part hard – that is to tell everyone they have to use the same tool at every stage of the process.
Now this may seem to undercut the whole process-sharing thing I mentioned above but bear with me – I’m really talking about all of the component parts of the final product. If you tell everyone that they have to use the same tool to build webpages, that’s going to leave you with a few people upset yes. You’ll also have a lot of people that don’t really care.
But if you tell them that they have to use the same thing to take screenshots, the same thing to do screencasts, the same thing to create word clouds, or to display bookmarks, or to push useful links — then you’re going to start getting the kind of resistance that makes people decide not to create the thing at all. This is especially true if people have been left on their own to figure out their own best way to do those things before.
So, to get to the point already…
So, Hannah and I were working on redoing our big tutorial – and one of the problems we wanted to address was the bottleneck that occurs when only a few people can edit or make changes to a tool. We also wanted to de-Blackboard our beginning composition assignments, and make them more lightweight and dynamic. Thinking to kill two birds with one stone, we decided to look at content-management-izing our tutorial building process.
The brain trust behind Library a la Carte (an open-source, lightweight CMS for building course pages and subject guides) works down the hall from us, so we had a place to go with this problem. We were initially open to a variety of approaches (including Drupal and WordPress) for building these tutorials, but we ended up deciding that extending LALC to include a tutorial-building function made the most sense.
We launched it barely-alpha, with the fall term beginning composition students. We found a bunch of things that wanted fixing, but even in this sub-optimal situation, there was an awful lot of it that worked well. Now it is in barely-beta, and with about 40 sections of beginning composition using it, the reports we have had about it not working for the students have been in the single digits.
This is what the tutorials look like:
(Here’s a link if you want to look at the whole tutorial. This one is cool because it has modules that feature: images, cartoons, videos and text included. You have to log in to see the quizzes, but not to see the rest)
There’s a few things I really like about it -
First, it allows our teaching librarians to share at a pretty granular (modular) level – I can borrow Hannah’s catalog-using screencast, and put it into one tutorial that is really about how distance students can have books delivered to them by mail, and also into another tutorial that is really about the serendipitous process of browsing for books on the shelves.
And even at that granular level, it lets us borrow-and-then-tweak — keeping things right in most teachers’ comfort zone.
Using an incredibly scientific data gathering method (n=1; n=me) I have determined that instruction librarians just may be more likely to borrow from each other and to remember to share with each other in this format.
Secondly, it solves the problem of where everything is going to live. Because it is integrated with our subject and class guides, the system lets us create tutorials and then automatically puts them on the website, with no pesky decisionmaking steps beyond what to call the thing. Which admittedly, can stymie me for a while, but…
Using the same data collection method (this time n=me and Hannah) I have determined that with this tool available, we are more likely to include tutorials and learning modules in the things we do for our classes, whether we meet with them face-to-face or not.
It also lets the librarian pull in content from elsewhere, so they can use any method they are comfortable with to create the content initially. If I want to store my photos on flickr, and edit with Picnik, that works fine. But so does uploading the photos that I edited with Photoshop. If I want to embed a video I edited with iMovie, I do the same thing I would do to drop in a screencast video I created with Camtasia.
Editing a video module:
It also lets us easily use dynamic content (which sometimes breaks the styling but, live and learn) so if I want to embed a delicious linkroll to recommend links to three different classes of students, I can, and then of course I can update all 3 class pages at the same time when I update my Delicious. Or if I want to do the same thing by embedding a Twitter feed, no problem.
Again, because this is integrated with our class pages system, we’ve already made a lot of decisions about where to share some of our resources. But even though we have a flickr archive, lots of us don’t use that for building the modules. And even though we have a YouTube channel, the videos there can be created in lots of ways.
I have no idea at this point if anyone else is going to start using this, or if it will mostly be used to update our main tutorial and in beginning composition. But I do like the concept of process-sharing, and I think this might be a way that idea makes sense.