The first reading for this week is from a book called One Shot Workshop, which does a good job of acknowledging how being taught how to teach isn’t something librarians are expected to know. I like the ADDIE system and how the focus is on having a good foundation and constantly working to improve how and what is being taught. The idea of solo design with a sounding board is appealing to me and sounds like what I try to do when working on things since another person who’s not deep in the project will spot things that I don’t. This book also has some useful ideas on how to create effective teams since building a good team is a critical part of getting to good design. I appreciate too the acknowledgment that different workshops end up having various priorities and those are important to consider when setting up the planning stages.
The Yelinek article looks at creating online tutorials, which in this digital world is quite important to know how to do. I like framing things by saying that teaching software is like teaching a procedure since most software is linear in terms of how it functions. I appreciate the focus on figuring out what the students need, in my work with America Reads, I’ve been putting together guides for how to use things. They haven’t always been on what I expect but they’re where help is needed, which is what counts. I think one of the challenges in teaching software is not focusing too much on how to do one thing, some students will want to know the basics and explore on their own. So the evaluation process before and after helps figure out what to focus on and what to change.
In the next article by Johnston, the question is how effective online tutorials are for teaching information literacy, which is a complicated thing to teach well. I like the idea of Graduate Attributes for undergrads because it helps to create a strong start for any student. I found it interesting that only a small number of students completed the survey since so much care was taken in the creation of the module. Hopefully they will consider redoing the survey to gain more information. It seems as if the online module could be useful for James Cook University but more detailed information and analysis will help. This article feels like the first step of many and not the completion.
For the last article, Griffis looks at how to create Pathfinders with screen capture tools, which can be important for demonstrating how to use software. Trailfire seems like a useful tool since it is webbased and focused on how to get to information same with Jing and the focus on screen casts. I know when I was learning programming being able to watch a screencast of a program helped me a huge amount since just reading what I needed to do didn’t always translate. The flexibility of Wink seems as if it could be immensely useful by providing still and moving images. Slideshare is a good resource but I think can be limiting depending on the type of information being taught. I look forward to seeing how these tools can be used with the ideas introduced in the One Shot Workshop book, because a tool needs to be thoughtfully used or else a tutorial won’t be of assistance.