This course, designed as a portfolio piece to demonstrate my course design, is geared toward people who have a hard time choosing engaging, good quality fiction books that keep their attention. In the course, participants will find three methods to consider when trying to choose an engaging, enjoyable fiction book for themselves. 

Note: I do not have a current personal license for Articulate so the link for this asset has been replaced with a video of the course I developed.

I considered using microlearning for this course, as many people possibly won't take the time to learn more about choosing good books.  However, due to the the wealth of information I wanted to cover as well as wanting to make the information more engaging as well as actionable, I decided that a course platform, particularly Articulate Rise would be a good choice due to the interactive nature of different Rise components.

I created a storyboard for my Rise course based upon my learning objectives and course material before building it out in the actual platform. I find that planning not only the content, but how it will appear on the page, and seeing it all in one document, allows me to get the bigger picture of the course. It helps me to make consistent design choices throughout modules, see if images or graphics are too similar, and easily go back and forth to revise my design decisions before adding them into Rise. 

While some blocks are easy to change in Rise from one type to another, with interactions, you typically have to start all over if you change your mind about what type of interaction you want to use in a certain space. With this particular course, after creating a module, I decided to go with a different interaction type that would be more actionable, and I was easily able to go back and make this change on the storyboard, instead of wasting time doing all of the editing in Rise.

I find that storyboards are even more helpful when working with stakeholders who have decision-making authority with courses, videos, etc. that you are developing. They help everyone stay on the same page and be able to give input before the video production or course building stages.

I created this course using Articulate Rise 360's course platform. As my storyboard was very thorough, the build time in Rise did not take long. 

I then tested my course, and made some initial changes for better layout, engagement and functionality.  One piece I added was a review activity at the end of the course. My original goal for the course was not to make it feel like something you had to complete to get the test correct, so I left out typical knowledge check questions, and opted for actionable items throughout (ie: adding a book to your TBR list after each section's final tips).  But as I previewed the course, I felt like a culminating activity was missing. I decided to add in a scenario using the built-in simple Storyline feature Rise offers as I wanted a short, simple way to reinforce learning in a real-world, meaningful way. I utilized the MindMeister website to plan my scenario, then built it in Rise's Storyline feature. Select the mind map image or link in this section to view my scenario planning. 

After I completed my own review and revisions, I also had a family member test out my course.  I asked them to focus on ease of use, functionality, as well as making sure the content was understandable, helpful, and actionable. After their review and feedback, I made some additional changes to the course. 

The main takeaway I had was in how I could improve accessibility for the course. 

After designing this course, I found that the knowledge check activity I designed utilizing the Storyline Interaction in Rise is actually not accessible to all users. 

I found a solution through another Instructional Designer I follow on LinkedIn; creating an interaction that still had movement, but that was more text and keyboard-friendly than the Storyline Interaction.  

I improved upon her initial ideas to try to really give it the same feel as the Storyline interaction so that users choosing this option would not feel like they were having a lesser experience.  

I ended up adding both options for participants to choose from; that way if there was someone who preferred text-based activity, even if they didn't need to use it for accessibility reasons, they could choose that path. 

To view this alternate user experience, view the "Applying Your Knowledge" section of the course.