Dynamic courses which can be tailored by Job Role?

Maybe this post here helps you get started.

This is easily done with branching as per Michael's link above. I would break the content into sections and work out which sections each job role needs to complete the logical order and then determine their paths by the use of a few variables to ensure you aren't repeating content and making the module larger than it need be.

If you are using an LMS the next step could be to capture their role directly from there. This way they wouldn't even know that their is multiple pathways.  

Thanks for this guys.  Most helpful.  I will work my way through this learning.

I have worked through the materials linked above Michael but it wasn't quite what I was after.  Thanks again though.  I was hoping not to run 3 separate courses within the same course.

I am attaching a mock up of the sort of thing I am aiming for, so that I can have a single course whereby users only complete certain elements of it for their job role and then complete an assessment based on the modules they took.

Again, not sure if Storyline 2 and Replay can handle what I need, but it could either be 3 different assessments or one assessment that knows which questions each job role needs to answer.

To give you a bit more of an understanding, we might have a course for administrative staff, another for nurses and another for doctors, to use a clinical system.  Admin staff could be reception staff, Nurses could be Health Care Assistants, Nurses who don't prescribe and Nurses who do, Doctors who will only complete the Prescribing part of the system and those who record within all the clinical areas.

Please see the attachment.  Cheers.

Hi Steve,

In reading what you are trying to do, I was reminded of this project/article which may be helpful: The Making of Electric Pallet Jack. It explains the overall instructional design approach used to create a course (Electric Pallet Jack) for 3 distinct audiences, each with a different training requirement. The course itself was built in Articulate Studio '09, but conceptually, this may help you determine how you could approach your project.

Hope it's helpful.

Nancy

Hi Nancy.

So if I have understood the link correctly, to be able to drop people out of the training and do the quiz, I would need to use triggers (not actions anymore) at the end of the last of their sections to a quiz, building the course from the user with the least tasks up to the user who does all the tasks.

As the likelihood of the training is that everyone would need familiarisation of the screen layout and functions, followed by the most limited tasks to satisfy the user who uses the least of the system (say, a Health Care Assistant), they would need to be the first out of the rest of the content.

If I continue the example, I would then continue with the content that is relevant to both a non-prescribing and prescribing nurse, until I reach the limit of the tasks for the non-prescribing nurse, at which point I trigger them out to another assessment, which leaves me with the user who carries out the greatest number of tasks, the prescribing nurse, whereby the last slide leads to their assessment.

This would be possible but may make the content of the training jump around, as the user has to revisit areas which were already covered for the users with less tasks to carry out.  This could be seen to be a benefit or a drawback depending on how you look at it.

You could argue that this repetition is good for their memory and embedding where data is stored or that jumping backwards and forwards across the system, instead of covering all the tasks when you are in that screen, is more chaotic and hinders their learning.

Have I understood that correctly?  Thanks.

Hi Steve,

I think you are close, although I'm unclear what you mean by "the user has to revisit areas which were already covered for the users with less tasks to carry out." I'm attaching a visual for clarification. Let me know if I am misunderstanding what you are trying to accomplish.

The attached visual shows the branching you could setup for three roles (as Michael and Tristan suggested). Learners make a role selection on the first screen and a variable is set, identifying their role. They are branched to the appropriate module and then move linearly through the rest of the content (that applies to their role) to the assessment.

You could use a single assessment with question banks (for example, a bank containing all assessment questions related to module 1 and another for questions related to module 2 and so on) and use the variable that stores the learner's role (based on the choice selected on that first screen) and conditions to determine which bank(s) of questions to display (for example, if role = user 1, display questions from question banks 2 and 3) and so on.

Hopefully this makes sense and helps you determine how you might do this using Storyline.

Nancy

Thanks Nancy,

It's good to hear that it can be done and that the assessment can be set up into banks of questions which can be grouped based on the job role variable.  That has given us one possible solution, much appreciated.

However, my colleague is wondering if there is a simpler solution as we think it could include a lot of "Variable" settings on the Previous and Next buttons of each slide which would get messy on updates to the course  and we haven't considered the standard wraparound menu sidebar controls around the slides once published (i.e. which menus they can access/see if they want to move around the course etc.).

p.s. the revisit areas bit is related to the software we are capturing for simulations splitting up data entry across multiple screens and tabs in those screens.  By using the suggested variables method (in the form of Pallet Jack), it means only some of the data across those screens can be captured in Module 1 as the lowest Grade Nurse won't use all of it, but the higher Grade Nurse will, meaning I have to split it out into Module 2.

Not sure if there is a smarter way of doing it, so that the other Job Roles see/do everything in one screen before moving on to the next, without repeating the content within the course.

My raison d'etre for having the content feature only once in the course, is all about updating the content in the future.  I don't want to have to be changing 3 sets of the same information, when functionality changes.

I have done this with a few courses - usually with state requirements.  What I usually do is create a T/F variable at the beginning of the course.  From here, I'll set up variables on every slide that say 'If Variable X is True, jump to slide X - if Variable X is False, jump to slide Y'

It sounds like you have 3 roles - so you can have the variable set to number 1-2-3, and then on each slide have the trigger set to 'If Variable A is 1, jump to slide X - if Variable A is 2, jump to slide Y, if Variable A is 3, jump to slide 3'

Hi Eric, if you have a lot of slides, that is a lot of settings that you have to set to jump forwards, and also backwards, to make sure they don't go back to a slide they should never have looked at.

And then if you also include a wraparound sidebar menu (which I assume is still around since I last saw Articulate), you have to take into account what they can access there for navigation too.

Maybe I just have to work through more tutorials to see how it might pan out.

My wishlist:     ;D

The next logical development step to allow this workflow to be easily managed in Articulate might be:

• to allow the creation of all the slide elements of the course, to sit separate to the navigation of the slides
• to select slides, in Story View, for each separate pathway Users need to navigate through the course modules, keeping one Story View updated as it is now, but the ability to view each pathway separately (Pathway View?)
• Drag them into the order in which they need to be completed within each Pathway View which updates the Jump to Next Slide arrows on Story View

This would ensure updates to the materials would dynamically update each Pathway View, if the slides were already in use.  Selecting new slides in Story View could add them into the appropriate Pathway Views, with dragging around also updating the Jump to Next Slide triggers for navigation.

If anyone else has any other solutions to my design problem which may be simpler, I am all ears.

To all of you who have responded so far, thank you for all your help as it has made me understand the structure, benefits and restrictions of what I know so far.  It really has been useful and enlightening.

Back to the tutorials to learn more.