I have to create complex simulation for sales team to enable them with dealing with different customers. Different type of customer profiles will be included in the simulation. participant will interact with those customers via series of choices questions. Participant choices will change the behaviour/responses of the customer.
Has anyone created such simulations? Can we make such simulations in articulate?
You can create such simulations using Storyline. The complexity of the branching pathways through the simulation will be pretty reflective of the programming effort required.
My advice is to start with a small prototype to forecast programming needs. You may design a single customer interaction to fit into a scene. If following customer interactions follow a similar flow, you may benefit from copying the first scene as a template.
Considerations you'll encounter for a simulation that contains multiple branches and perhaps outcomes:
Leverage custom variables to direct through each customer interaction.
Does an object state, show/hide layer trigger, change to a dynamic variable, running a JavaScript function or even slide advancement provide the experience you want for participants when they make a selection? Can the chosen solution be copied and repurposed easily?
Design a layout that can support elements of your storyboarded content that, for instance, have the greatest number of scenario and feedback text characters. If you're templating a slide, you don't want any surprises later when content doesn't fit.
Will you want to capture participant performance data to report to your Learning System? If so, you will want to design meaningfully named variables that will be understandable when reported.
These are just a few thoughts. To repeat, I think Storyline is up to the task for a pretty robust sales simulation. You just want to make sure you have worked out the details (like the above) before you get into the full build,
1 Reply
Hi Shikha,
You can create such simulations using Storyline. The complexity of the branching pathways through the simulation will be pretty reflective of the programming effort required.
My advice is to start with a small prototype to forecast programming needs. You may design a single customer interaction to fit into a scene. If following customer interactions follow a similar flow, you may benefit from copying the first scene as a template.
Considerations you'll encounter for a simulation that contains multiple branches and perhaps outcomes:
Can the chosen solution be copied and repurposed easily?
These are just a few thoughts. To repeat, I think Storyline is up to the task for a pretty robust sales simulation. You just want to make sure you have worked out the details (like the above) before you get into the full build,
Hope this helps,
Bob Stryker