Follow email Print print

Best Practices: Mission Building




Start with “why”

Prior to creating a mission, we recommend taking a moment to identify the critical data and key metrics you intend to capture. We’ve often found that the most meaningful and actionable data is the result of focused and intentional mission structure.

  • Prior to creating a new task, ensure that the question you are asking is in line with your initial "why" for the mission. 
  • Still not sure whether to include a question? Ask yourself, what will I do with this data once collected? If it's not actionable, it might be a good candidate for exclusion.

Short & Sweet

GoSpotCheck missions can take many forms, so it can be tempting to get carried away with the number of variety of questions contained within a single mission. We’ve found that in most cases, missions that are succinct, focusing on data that is most important, provide a better experience for users and admins alike.

  • Admins have easier accessibility to the data and metrics that matter most (less clutter)
  • Mobile App Users can complete more missions in less time



Conditional Questions

One of the most powerful ways to create smarter missions is to use Conditional Tasks. These tasks allow you to collect follow-up data, based on an answer to a previous question. Here are a few tips to make the most of them:

  • Y/N: Consider beginning a new question set with a Yes/No question, to indicate whether or not the item in question is present at all. If Yes, you can add conditional tasks to collect supporting details surrounding that item. If No, add a conditional multiple choice task allowing the rep to indicate why the item is not present.  
  • Hierarchy: Conditional tasks are tabbed to the right of their parent task. They are also numbered as follows: 1.) Parent Task 1.1) Conditional Task
  • Task Labeling: For clarity of initial data collection and subsequent data analysis, we recommend including the item name in every conditional question.


Limit Short Answer Tasks

Short answer tasks can be useful to capture observations in the field, however, these free field responses are not quantifiable. We recommend limiting Short Answer Tasks within missions, instead favoring more quantifiable alternatives like Multiple Choice or Multiple Select tasks, populated with your most likely Short Answer responses.


      1. “Is the apple bin on display?” Y/N
           1.1 (on "No" response)
                  “Why isn’t the apple bin on display” (Multiple Choice)
                  a) Seasonal exclusion
                  b) Manager hasn’t put it out
                  c) Store not participating
                  d) Missed Deadline for Display

Scale vs. Multiple Choice

When attempting to collect a range of data, the scale task is a great option, especially for small ranges (1-10). For larger ranges, consider using a Multiple Choice task, populated with number increments/ranges of the most likely responses. (Example: Multiple Choice Task (a. 1-5, b. 6-10, c. 11-15, etc).  This  allows for easier entry on the front end (less user fat-fingering), and better aggregation on the backend)

Task Reporting

It may be helpful to reference how tasks are represented in GoSpotCheck reporting to help determine the best task type for your particular question. Here is a handy guide that may help!



Deploy and Test Your New Mission

The very best way to understand how your Mission will fare out in the field, is to test it on your own mobile device! Experiencing the Mission you've created from the perspective of the team has some amazing benefits:

  1. Catch your mistakes: When creating your Missions, it's easy miss typos, or accidentally require a question you intended to be optional, or choose the wrong task type (e.g. Multiple Choice instead of Multiple Select). Those mistakes, though less obvious in the dashboard, become extremely obvious to your users in the Mobile App. Deploying the Mission to yourself first, helps you identify and correct these errors before they reach your team.
  2. Perfect your Reports: While you're at it, go ahead and submit your Mission Response. When you head back to the Mission Overview page, take a look at the way your tasks are reported. Are they telling the right story? Do the task tiles represent information that you care to review and share? Next, export your data to XLS or CSV format and review the way it is formatted. Will the data provide you with the right information to act? If the answers to any of these questions is NO, now is the time to modify and improve your questions. 

Return to your Mission to edit and repeat the process until you have a Mission that meets the needs of your organization.

Have more questions? Submit a request