Sunday, November 13, 2011

Deconstructing My #DemoFest Course - Part 1

During this year's DevLearn 2011 conference I won the DemoFest award for the Software Systems Training category. Being selected for this award really put me on Cloud 9. It is so flattering to have my course selected by the DevLearn attendees. Thank you everyone who attended DemoFest. And a big congratulations to all the other winners of this year's DemoFest. It is a true honor to be in their company.

Over the coming weeks I am going to blog about the processes of designing, developing and implementing my DemoFest course. My intention is to share how I go about putting a course together and to provide the support materials used to design the course. For example, the course design plan, storyboards, communication plans, etc.

A good place start is to first provide an overview of the course and lessons learned as described in my DemoFest submission below.
Why was this project needed? Describe why you built it.
Johns Hopkins HealthCare began transitioning staff to Microsoft Office 2010 applications in February 2010. Staff required training on using the new application interfaces and learning how to complete Office tasks that have changed in the new and updated Office software.

What authoring tools, systems, or technologies did you use to create this project?
Adobe Flash, Adobe Captivate, Articulate Presenter, Articulate Quizmaker, Microsoft Office 2010. Social Media included Twitter, Screenr videos, and Diigo social bookmarks.

How many "learners" will benefit from this program or project?
760 Johns Hopkins HealthCare staff, but the course is being extended out to additional entities within the Johns Hopkins Health System.

How long did it take you to complete this project?
Approximately 120 hours during a two month period. This time does not include ongoing learner support using social media and Intranet pages.

What problems or challenges did you have to overcome while creating this project?
Time constraints, which resulted in not including audio in the course. Limited staff participation in the social media elements, specifically Twitter. The need to use multiple development tools in order to accomplish the project’s design.

What valuable insights, lessons learned, or results did you discover when working with these challenges?
Due to the less-than-expected use of Twitter among staff, there was less participation in the social media elements. In the future, I would put more effort in marketing the benefits and use of Twitter among staff. Also, I would find a way to incentivize its adoption by staff. I learned that the ongoing support implemented on our Intranet pages, Screenr videos, Diigo social bookmarks, and job aids were highly valued by staff and seen as very practical and accessible resources that are continually being used. Also, the non-linear design and easy to navigate course encourages it to be also used as a refresher course. One of my most valuable insights was that the use of whimsical characters was an effective way to market the course, and increased recognition and participation in the project. Using the characters to market the course included placing full-size cut-outs of the course's main character, Captain Upgrade, throughout our buildings, and appearing on LCD screen advertisements, flyers, and on our Intranet.

Below is the link to the Office 2010 course. I have also provided direct links to the learning program's social learning elements.

Introduction to Office 2010

And direct links to some of the social learning elements in the learning program:

In the next post I will describe the design process and share a copy of the course design plan and example storyboards.

Thank you again to all who attended DemoFest and a really big thank you to the eLearningGuild for holding an incredible DevLearn conference.

No comments:

Post a Comment