A wee while ago Xin and I decided that we’d like to design a training course to sell on Open Sesame. Similar to selling something on itunes, it was a bit of a stab in the dark. There was no specific client or deadline.
Like many of you, we followed well known creators in this field (Cathy Moore , Tom Kuhlman and Connie Malamed to mention a few). All of whom offered excellent advice. All of which we largely ignored – often to our detriment – once we started the project.
This is the story of how we created a brilliant, but extremely complex, branching scenario as our very first project for Naturalelearning Limited, the end result and some useful tips we learned along the way.
I’ve included some of the free tools we used along the way. Save yourself a gazillion hours of browsing and jump straight to them.
Let’s start with a sneak preview. The end result was a 90 minute training package about leading virtual teams. The story is set in the future and takes place over a three month period. By the end of it, learners should have acquired some project management skills particularly suited to virtual teams. It took us a combined 300 hours to build from beginning to end. The final package can be viewed here: https://www.opensesame.com/c/virtual-team-virtuoso-parts-1-3-traini...
We didn’t mean for it to become so complex. However, this was a performance based course intended, as Tom Kuhlman puts it, to: “teach principles that guide decisions, like much of the soft skills training…branched scenarios come in handy when you have nuanced situations and are trying to help people think through them and make appropriate decisions”.
And as Cathy Moore explains: “In a branching scenario, decisions made in early scenes affect later scenes.”
And therein lies the rub. Let’s say Lucy has to decide how to deal with a member on her virtual team who is not responding to emails or other messages. How should Lucy respond? Choose A, B or C and get feedback. Here are some resources to help you. Depending on your choice and its consequence, you will go down a particular pathway or you may become stuck and forced to loop back.
The effect is cumulative. The designer needs to remember decisions that Lucy made earlier in the story. Even if your training package draws on established company policies and procedures, there is still likely to be numerous possible correct responses. Pretty soon you end up with a branching scenario that is almost as infinite as the synapses on a neuron. Add to this decisions that need to be made around authoring software, copyright, multimedia and the basic structure and it can quickly become complex and onerous if you’re not careful.
Here is our story and the lessons learned along the way.
Give yourself a deadline and a budget, even if it’s just made up
We were initially pretty open ended about this and since it was done outside of normal hours on our own time we let our creative heads take over our business heads. All well and good but by the time we were finished we realised we’d probably have to sell hundreds of packages to make the time spent on it worth our while. Just as well it was really a ‘test the market’ type of product which we also used to help us establish our own routines for working together on similar projects.
Do a little research (or work with a SME) and then use a flowchart to create your scenario
Working out the scenario and all the possible consequences was the most difficult part for us. We developed the context, our characters and a rough story line first. We tried numerous ways and tools for mapping this out. We needed to produce a flowchart but many of the free tools just didn’t have all the features we needed. An added difficulty was that one of us was a dedicated Mac user, the other a PC user. In the end we discovered that Microsoft Visio worked the best for us. We organised our key messages around an acronym: TRUST. Each letter stood for a key learning point. This proved to be a useful tool for structuring the content.
To offer some flexibility, learners were given three different pathways through the story at the very beginning: easy, medium or hard. The easy pathway would provide hints before a question was answered and feedback afterwards. The medium pathway provided feedback only. The hard pathway provided no guidance although students could access the resources we developed in any pathway. A virtual tutor called Vicki provided the hints and advice. Vicki was one of four free character cut outs that we found here: http://elearningbrothers.com/
Choose your authoring software wisely
Suffice to say that Captivate (which we used) is a very powerful tool which you should consider using for a complex scenario. If you’re thinking more along the lines of what Cathy Moore calls a ‘mini scenario’ where, you make your decision, see the realistic consequence, and figure out if you made a good choice before moving to a different scene representing a different situation, then consider using something like Articulate or iSpring Pro instead. At the time we used Captivate 5.5 and Articulate Storyline had not yet come onto the scene. If it had, we may well have used that instead. Captivate files are big, very big. However, Captivate does have the advantage of freeing you from the Power Point yoke, if you want to do something quite different.
Create a template and a storyboard
We didn’t do this but take my advice and finalise the template first. And by template I mean the background and icon placements in your authoring software. If you’re not using the standard templates provided you need to think carefully about colour schemes, font size etc. It seems unimportant in the beginning but setting it up properly at this stage will save you from tedious rework in individual slides at a later stage. For those of you that are looking for templates, you’ll find a useful collection here:
There is no shortage of storyboard styles out there. In the end, we found that the format you see in the attached file at the top of this blog (Storyboard used for Virtual Team Virtuoso) worked best for us.I worked initially in a Word document and provided the content and instructions for video and audio to Xin who then entered it into Captivate. I’ve attached a copy of our the storyboard we created to this blog. We’ve filled in part of it as an exemplar. We had between 3-5 situations for each of the three Virtual Team project phases. Each situation offered the learner three different responses to a particular challenge. Each response outcome had specific feedback attached to it. If you do the maths, that’s at least thirty different outcomes we had to design.
Once Xin had placed everything roughly in Captivate, I went in and edited in there, using the notes function to ask for big changes I couldn’t manage myself. We worked with our strengths. Xin was quick and capable when it came to working in Captivate, I had more experience with the scenario design.
We both find advice and tips from Connie Malamed’s website (see http://theelearningcoach.com/elearning_design/using-graphics-to-imp...) really useful.
Be aware of the limitations of technology used during development
We began by using this software for voice recording: http://www.ivona.com/en/recordings/ which sounded really great but took a lot of time to record and place at the appropriate position in Captivate. If you changed your mind about the wording, then unlike Captivate built-in text to audio funtion, you couldn’t just change the words and re-generate the audio voice. You had to redo the recording and import back into Captivate. Combine this with our perfectionist streak and the end result was that it took us quite a lot of time to adjust the voice.
In the end, we did a little recording (for example, when our character David spoke as Captivate doesn’t have an automated voice with a Chinese accent) but for the most part we simply used what was available in Captivate. This does have the tendency to sound slightly robotic unfortunately. One of our characters was French but we had to go with a bland English accent for her because neither of us have any French friends and we really struggled to find any digital voices with a French accent.
Embedding video in Captivate is another challenge. Not all video formats work well in Captivate 5.5 when they are viewed in different browsers and platforms. This is where owning a Mac and PC between us was an advantage. We tested our package on Google Chrome, Internet Explore, Safari, and Firefox. We found the format that worked best across all browsers was either MOV or M4V files. Stick to these file types if you can.
Be aware of copyright
Thank G-d for Creative Commons and the public domain. We found our images, icons and audio clips at these different locations:
It was impossible to embed a link to every graphic on every slide so we created an attribution list at the end. After a bit of research, I found that the most appropriate way would be to lay it all out in a table under the following columns: thumbnail, title, creator, url to image/sound, any relevant copyright notices, licence info.
Add a Comment