Tuesday, March 12, 2013

[tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] [tremeex] Sometimes It’s Good to Stop Your Learners Before They Get Started

Sometimes It’s Good to Stop Your Learners Before They Get Started

Link to The Rapid eLearning Blog

Sometimes It’s Good to Stop Your Learners Before They Get Started

Posted: 12 Mar 2013 01:58 AM PDT

Articulate Rapid E-Learning Blog - are you sure you want to click that next button

In my elearning workshops we discuss the parts of elearning courses that are common to most courses. One of the goals is to get participants to think through the common parts of a course and then determine how much of that can be prebuilt to save time.

For example, most likely the course will have welcome and exit screens. They may not look the same for each course, but odds are that both will exist. Why not build a template that has a screen reserved for the welcome and exit process of the course? At this point, you're not assigning a look or feel; you're just making a space for it.

Introducing the Gate Screen

Another common part of many courses is what I like to call the "gate screen." It's a screen that serves as a gate by stopping the flow of information until the learner is ready to move on. Generally, there are two types of gate screens: introduction and feedback.

Introduction Gate. This gate usually appears prior to the start of an interaction. It pauses the course to provide some introductory information and instructions. Then when the person is ready, she can advance.

Articulate Rapid E-Learning Blog - example of an elearning gate screen

Feedback Gate. The feedback gate does the same thing as the introduction gate—it pauses the flow and provides some information which is usually the result of a decision the learner's made. This type of gate is very common as feedback in elearning quizzes. Make a choice and hit submit. Up pops the feedback screen. Read the feedback and then click the next button (or possibly go back to make a different choice).

Articulate Rapid E-Learning Blog - example of an elearning gate screen for quizzes

Both of these gates are essentially the same because they stop the flow of information, let the person regroup or get oriented, and then move on.

As I stated earlier, these are fairly common in the construction of elearning courses. And since that's the case, why not plan for them in your design before you get started?

  • Create a placeholder for the gate screens in your initial design so you don't forget to add them in during the production process.
  • Plan the look so that it fits your course design. The last thing you want is a Frankencourse. I usually use the same design for both gates and then just change the buttons and placement of them for each screen.
  • Determine the user experience. How will they work and will they seem intuitive to the flow of the course?

The two gate screens are essentially the same. They're gates that stop what you're doing; get you to focus on something; and when you're ready let you advance (or go back). And odds are that they'll be in your next elearning course. So why not save some time by putting them in the production queue before you get started?

Do you use gate screens in your elearning course? If so, share with us how you use them.


Tidbits

Work with me and the Articulate community! There's a cool opportunity to be part of what we're doing in the Articulate community. You can learn more about the job here.

What you'll need:

  • Writing samples. Look over these blog posts to get a sense of what we do: Word of Mouth & E-Learning Heroes.
  • Portfolio that shows your best elearning skills.

We won't start to look at the applications until after the Learning Solutions conference so that should give you plenty of time to put together samples of your best work.

*Also, check out all of the other open positions at Articulate.


Upcoming workshops for 2013:

  • March 20 & 21: Durham, NC (ASTD). Two workshops. 
    Day 1Rapid E-Learning Workshop.
    Day 2Articulate Storyline Workshop.
  • April 2 &3: San Diego, CA. Two workshops. Sign up before it sells out.
    Day 1 – General elearning tips & tricks.
    Day 2  – A hands-on Storyline session.
  • April 16 & 17: Austin, TX. Two workshops.
    Day 1Rapid E-Learning Workshop.
    Day 2Articulate Storyline Workshop
  • May 14 & 15: London, UK. How to Become a Rapid E-Learning Pro: Two-day master class filled with lots of hands-on activities.
  • June: Philadelphia, PA. Details coming.
  • June: Portland, OR. BlueVolt eLearning Conference. Join the Articulate community team for a series of how-to sessions using the Articulate elearning applications.
  • June 12 & 13: Miami, FL. Two workshops. Details coming.
    Day 1 – Rapid E-Learning Workshop.
    Day 2 – Articulate Storyline Workshop.
  • September: Greensboro, NC. Details coming.
  • September: New York, NY. Two workshops. Register here.
    Day 1 – Rapid E-Learning Workshop.
    Day 2 – Articulate Storyline Workshop. I'll also be presenting at the evening chapter meeting.
  • October: Baton Rouge, LA. Details coming.
  • October: Los Angeles, CA. Details coming.
  • November: St. Louis, MO. Details coming.

Download your free 46-page ebook: The Insider's Guide to Becoming a Rapid E-Learning Pro


--
Posted By tremeex to tremeex at 3/12/2013 09:11:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:11:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:11:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:11:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:11:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:11:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:11:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:11:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:11:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:11:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:12:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:13:00 AM

--
Posted By tremeex to tremeex at 3/12/2013 09:13:00 AM

No comments:

Blog Archive