I’ve been thinking about user-led learning lately. I have a set of tutorials that we refer to as “tours.” I imagine this term was chosen because the object is to give new users an overview of how to use the various parts of the application to accomplish the main task.
Some Background
Let me give you a bit of history on these tours. Before I was assigned to maintain the project’s documentation, these tours were built as PowerPoint presentations and run through a Breeze engine to create a Flash presentation. (I don’t know if Breeze in that form exists anymore.) Some pages had short videos created in RoboDemo. The presentations contained links to move forward and backward, so the intention was for the user to go from start to finish, similar to taking a tour in a museum: You begin in one place and move through a linear experience.
When I upgraded to the version of Breeze that came out after I took on these files, I found that somehow, multiple videos could play simultaneously. I could start a video on one page, then go to the next page and start that video. I would hear additional mouse clicks. If I went back to the previous page, that video would still be running.
Messy.
I manually moved the content into a new set of HTML pages because I knew that one page loads at a time, so it would be impossible for multiple videos to be running at once. I took the opportunity to learn CSS so I could lay out the pages that way.
› Continue reading…
Tags:
Adobe Captivate,
Captivate,
e-learning,
instructional design,
learning,
technical communication,
technical writing
I’ve been doing my own voiceover for a series of Captivate software demonstrations I’m building. I write a script, record the demo without any audio, and then tweak the script as needed based on what I recorded. Using a free program called Audacity that I found on the Web, I record the voiceover to my computer in separate pieces, manipulate the tracks, and export them as mp3s. Then I import them into the slides in Captivate.
I tend to speak in a quiet monotone, so doing voiceover takes some extra effort. I have to shut myself in a room so that as I read the script, I can speak up loud enough to get varied tones going. That went all right, but it still didn’t sound natural. So I tried something a little different.
I started gesturing a little with my hands while recording. Interestingly, it made a large difference. My tone sounded much more relaxed and conversational. Tonal changes happened in better places. I also read the script with fewer mistakes. So there’s a trick for my bag.
Speaking of something I learned about doing demos, the manager of one of the projects I work on asked me to show one of the demos to the team in a meeting last week. I had included the built-in keyboard tapping sound for typing animations, but I shortened the animations so that the typing went a little faster. The result was about 5 characters per tapping sound. There were some jokes and laughter about this, so I decided it’s probably better to do away with the tapping altogether.
Tags:
Adobe Captivate,
audio,
e-learning,
software demonstration,
technical communication,
voiceover