Pathfinder: Scenario Based Content Development


In Path Finder, learners navigate their way through either a linear or branching scenario. When presented with a decision, the user is tasked with selecting the best answer, which will determine where he or she is taken next.

This Guide

This guide details the different elements of Path Finder and the best ways to organize its content into a fully functioning scenario script. Additionally, a word document is attached to this article that provides several scenario examples.
For additional assistance, please email

Preparing Your Content

When preparing your mLevel content it is important to focus on these three elements:

Decision: The decision in Path Finder will serve as the question or scenario you intend for the user to answer. An example of a decision would be: Your first customer of the day comes up to you and says “Which device has the longest battery life? I am often times traveling for my job and need a phone with and exceptional battery.”

Choice: The choice(s) will serve as the answers to your decision. Path Finder allows for any number of choices to be created, however as a best practice, we tend to keep choices between 3-4. An example of some choice(s) would be:

1. Samsung Galaxy Note 3 or Google Nexus 5
2. Samsung Galaxy Rugby Pro
3. Blackberry Z10 or iPhone 5C

Keep in mind that with the Pathfinder game the administrator has the ability to assign a grade for each choice. Answers can be considered correct (100%), partially correct (50%), and incorrect (0%).

Feedback: The feedback will serve as the user’s guide in determining why the answer they chose was either correct, incorrect, or partially correct. This element grants the user the ability to now learn in real time why the choice he or she chose received a certain grade.

Defining your Path

Once you have familiarized yourself with the components of the Path Finder activity, it is now time to plan out your Path Finder structure. The Path Finder activity supports two different types of scenario design: linear and branching. Once you have determined which type you would like to use the next step is laying it out in flowcharts like the ones below.

Linear Scenario:


  Key Points – A linear scenario:

  • Puts a user down a prescribed path
  • Allows the user to encounter multiple types of scenarios
  • Provides the user with an instructive learning experience

Branching Scenario:


 Key Points- A branching scenario:

  • Helps the user recognize and challenge assumptions
  • Teaches the user how to recover from mistakes
  • Allows the user to navigate long or complex processes

Draw It Out

Once you have determined the structure that best fits your content and goals it is now time to “white board” it out. Here you may use any program such as Excel, Word, Power Point, or even good old-fashioned pen and paper!

Writing the Scenario Script

Once you have determined the structure and developed the flowchart it is now time to begin scripting your Path Finder activity. When scripting your activity, we break down the flowchart into what we call scenes. In the Path Finder activity we have the option of creating three types of scenes:

1.) Question/Statement Scene: This scene will house your decisions along with your choices and feedback that we will be providing the user with.

2.) Non-Decision Scene: This scene will be used to drive navigation throughout the scenario that the user is engaging in. 

3.) End Scene: This scene will signify the end of the activity for the user

After choosing the scene we would like to create, we then have the ability to add slides to those scenes. The four types of slides are:

1.) Title Slide: Here you will give a title to your Path Finder mission. An example of this would be: “Selling Smartphones in Various Customer Scenarios”

2.) Text Slide: Here is where you will set the scene for the end user. Here the administrator should provide information that will reveal to the user what they will be experiencing in the game environment. This is also used to add a deeper understanding of the situation prior to a question being asked. An example of this would be: “In this activity you will learn how to assist customers in choosing a Smartphone that best suits their needs. Use what you've learned in previous activities to match up a device with what they are looking for.”

3.) Image Slide: Add any imagery that will enhance the user's overall experience.

4.) Video Slide: Allows you to include a video the user can watch to either enhance their knowledge or to ask questions on. For information please visit our video support article.

Scenario Scripting Template

After familiarizing yourself with the various elements of the script, it is now time to start scripting out your Path Finder content. Below you will find a basic example of how scripting document may be organized. Keep in mind that there is no “set in stone” answer here, which ever scenario planning and scripting process you are comfortable with can be utilized.

Scene 1: Question Scene

Title Slide: Title of activity (Only has to be done once)
Text Slide: Description text setting the scene for the end user.
Question: Here you will outline the decision that the user will encounter.

Scene 2: Question Scene

Question: Here you will outline the decision that the user will encounter.

Scene 3: Question Scene

Question: Here you will outline the decision that the user will encounter.

Scene 4: End Scene

End Scene: Here you will outline the message the user receives when they reach the end of the activity. Keep in mind that you may have multiple end scenes depending on the structure you choose.

Getting Started in Mission Manager

After your Path Finder mission has been planned out and scripted, you are now ready to move into the mLevel platform. Once ready to move into Mission Manager, work with your Account Manager to schedule a training session with your Customer Advocate. They will be able to assist and support you as you upload draft one. For more information in regards to the building of Path Finder within the platform please see: Path Finder: Creating a scenario-based activity

If you have any additional questions regarding Path Finder please email

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk