Creating Asynchronous Sessions (users login at different times)

Asynchronous Sessions are useful in situations where not everyone who needs to join a session is available to do so at the same time. This article discusses how to create an effective Asynchronous Session. 


Before creating a session, determine the goal of the session, and the process needed to achieve that goal. 

Example: The goal of my session is to determine the most important actions required to kick of xyz project.

The answers to the considerations below will determine if participants will need to login multiple times to complete different steps in the session.

  1. Will participants need to add content? 
    • Do you want participants to discuss the content they are adding, or just add ideas?
      • If discussion is required, is review required to ensure the group understands each item?
    • Will you need to categorize ideas, or combine duplicate ideas before moving to the next activity?
  2. If content is already provided:
    • Do participants need to discuss this content through comments?
      • If discussion is required, is review required to ensure the group understands each item?
    • If discussion is not needed, is a vote required? 
      • If a vote (assessment) is required, does it need more than one criteria (e.g. likelihood and impact, or immediate impact and revenue)
      • What kind of scale should be used? (e.g. point scale or check boxes)
    • Is more than one vote required?
      • Will the results of my first vote need to be further reduced through a rank type vote?
  3. If one or more voting activities are utilized, is another step needed to determine action on the results?
    • Is an action plan needed?
    • Is further analysis on the voting outcomes needed?



When creating an Asynchronous Session, considerations should include:

  • A simple session design
  • Instructions required for users to move through the session on their own
  • Length of time the session will remain open for participants to participate

Best Practices

  1. Navigation - Only display the activities participants will need to complete in their first login.
    • e.g. A participant logs in and lands on the welcome screen. The only activities they can see are 3 crowdsouce activities which address different questions or topics. 


Leader View - The leader has used the toggle switches to turn off The Plan and The Background sections, as well as agenda items that the participant should not view yet.Leader_View.jpg

Participant View - The participant can only see and engage in the activities enabled by the leaderParticipant_View.jpg


  1. Activity Views
    • Determine how participants should be able to respond to a crowdsource:
      • Responses only
      • Responses and Comments?

Leader View - The leader has comments turned off and has turned off the participant's ability to add questions.

Participant View - Can only respond to the question, no comments allowed.


  1. Next Activities
    • Participants may need to login again to complete the next activity after the leader has moved content into another crowdsource, a vote, or matrix activity.
    • Based on your session design, set this expectation up front and give participants timelines for each phase.
  2. Setting up a vote
      • When setting up a vote activity in a asynchronous session, determine if it is desired for participants to view the results. Because they are able to login again, seeing the results may cause participants to change their vote. 
          • To turn off a participant's ability to view results, turn off the "Allow Thinkers to change the view/see results" setting. (Click the gear wheel on the activity to get to these settings.)



    • Setup a simple to follow vote. Make descriptions easy to understand, and give directions in the details area under Items in the Ballot Items column.

Leader View


Participant View

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



Article is closed for comments.