Employee Research Best Practices

Overview

Remesh can be introduced at any phase within the employee life cycle to learn directly from your employees how to improve their experience! Here are some best practices and tips to make sure you are engaging employees in the most effective manner as well as information about recruiting employees.

Included in this Article

  1. How it Works
  2. Preparation for Recruitment
  3. Recruit, Invite and Remind Employees
  4. Recruitment Best Practices
  5. Discussion Guide
  6. Live Sessions
  7. Frequently Asked Questions

How it Works

Remesh has two primary product offerings: Live and Flex. You can read about the differences between these two 0fferings here. You will want to adjust your recruitment strategy slightly based upon whether you are conducting a Live or Flex Conversation, which we have outlined below. 

You may also be interested in Reopening your Live Conversation as a Flex Conversation, which allows you to conduct a Live Conversation, then convert the Conversation into a Flex. This can be valuable as it allows participants the opportunity to engage with Remesh Live, a unique and engaging way to share their thoughts, but if they are unable to make it at that day and time they will still have the opportunity to share their feedback asynchronously. Read more about Reopen here!

Preparation for Recruitment

  • Some networks may block the Remesh platform. Review our Technology Considerations with an IT professional to help ensure employees have a smooth experience accessing the Remesh platform.
  • We recommend giving employees at least two weeks notice when recruiting for a Remesh Live conversation. Work with teams that typically engage employees (e.g., Marketing, Comms, etc.) to determine the best cadence and format for reaching out to the group.
  • You will need to include the participant link to the Remesh Conversation in your communication, which will be generated after you create your conversation. You can read more about participant links here.

Recruit, Invite and Remind Employees

  • Feel free to leverage the following template to invite employees to a Remesh Conversation:
  • Timelines will vary slightly depending on what sessions you are conducting. We recommend following the below suggested timelines, adjusting to the needs of your organization.
    • Remesh Live
    • Remesh Flex
      • 1 week before start: Send a calendar reminder blocking time for employees to complete the upcoming Flex Conversation.  You may want to include session information, participant videos and/or participant instructions as well as the participant link.
      • 24 hours before start: Send an email to employees reminding them of the upcoming Flex Conversation.  You may want to include participant videos and/or participant instructions
      • Start time: Send an email letting employees know that it's time to access their Flex Conversation!
      • Throughout the Flex Conversation: While the Flex Conversation is open, we recommend sending email communication reminders. 
    • Remesh Reopen
      • We recommend following the Remesh Live timeline outlined above, without explicitly mentioning the option for a Reopened Flex. This will ensure you capture the largest audience possible in your Remesh Live Conversation. Once the Remesh Live Conversation has ended and has been reopened, you can then begin to follow the Remesh Flex suggested timeline starting at step 2.

Recruitment Best Practices

  • We recommend recruiting participants at a 3:1 or 4:1 ratio. So, if you want to have 100 participants in a Conversation, you should aim to have 300-400 people actually commit to show up and participate. Framing the Conversation as mandatory instead of optional will also drive better show rates.
  • You can invite up to 1,000 participants to a Remesh Live Conversation and 5,000 to a Remesh Flex/Reopened conversation. We recommend having at least 20 people so the algorithms can be fully optimized.
  • Be sure to share context and participant videos ahead of the session to let employees know who they are going to be interacting with and how their data may be leveraged.  
  • Remesh conversations do not have an audio component to them, and operate much like a texting conversation. It may be helpful to remind employees of this, and you can even suggest they have a playlist ready to listen to while they're participating. 
  • If you can, have some of the communications come from someone on the Leadership team so employees know that the Remesh session is being taken seriously and has high visibility. 
  • If applicable, speak with managers of the target employees. Share context and ensure buy in and make a plan for how these managers can encourage and support employees in completing the Remesh Conversation.
  • If you provide multiple days/times for employees to participate in a Live Conversation, try to gauge how many folks will attend each session through a quick survey or a calendar invite.
  • We recommend including the participation/audience link in a calendar invitation for Live Conversations.
  • If conducting a Flex, monitor your Summary Page. If you programmed a question asking for department, you can monitor engagement and target specific departments as needed.

Discussion Guide

  • When engaging employees, you can hold a Remesh Conversation for as long as you need, but we recommend the following.
    • Remesh Live: 30-45 minutes
    • Remesh Flex: 15-30 minutes
  • In addition to standard Onboarding Polls such as age and gender, it can be helpful to include questions on job title, tenure, responsibility level, office location, and other company-specific items. Onboarding Poll questions can then be used to Segment your data. We recommend 10 or fewer Onboarding Poll questions.
  • We recommend starting your discussion guide with instructions, sharing context for the research and reminding employees their responses are anonymous. This can be done either by programming Speaks or pre-recording a brief video and uploading it to your discussion guide. You can find more information about this here!
  • Please note that in Flex sessions, all questions must be answered by participants to proceed. We recommend programming Discussion Guide questions that will be applicable for all participants. If that is not possible, we recommend adding  a reminder to participants in the instructions that they may vote on responses like "Prefer not to respond" in Ask Opinion questions. It can also be helpful to add "Prefer not to respond" poll options where applicable.
  • When asking open-ended questions, try to be clear and direct, and avoid asking more than one question at a time. For example, instead of asking "How do you feel about your job responsibilities? Why do you feel this way?" we recommend separating these into two distinct questions that you send to the participants. 

Live Sessions

  • It can be helpful for the moderator to send messages on the fly to participants stating what you're hearing from participants. You can find a few examples below.
    • Poll: I see many of you mentioned that benefits are important to you. Which of the following aspects of the benefits package is most important to you?
    • Ask Opinion: It looks like the majority of you agree that PTO is the most important aspect of your benefits package. Tell me more, why is PTO important to you?
    • Speak: Thanks so much for your thoughts! Many of you mentioned PTO is important to you because you are caring for a child. We will take this into consideration as we develop our new benefits package.
  • You may also want to plan on reopening your Live Conversation as a Flex. This gives participants the opportunity to join the Live event who can, but provides an opportunity for those who were unable to make it to have their voices heard asynchronously through the Flex.
  • If you intend to host employees on a conference line or be in the same room at the same time as gathering feedback on Remesh, we recommend looking through these best practices. This is optional, as Remesh can be accessed solely from a web browser.

Frequently Asked Questions

  • Can I make a QR code using the participant link?
    Yes! Currently you cannot create a QR code within the platform, but many users have successfully created QR codes with external websites. We always recommend testing the QR code before sharing it with your participants.
  • Can Remesh be accessed by participants on a shared device?
    Yes, Remesh can be accessed on a shared device! Please keep in mind that if you intend to have multiple participants access a Flex Conversation on the same device, the browser will save progress for 24 hours. We recommend utilizing a Chrome incognito window in this instance.
  • What is the participant experience like?
    You can see what the participant experience looks like here.
  • Can I send the link to participants before my discussion guide and details have been programmed?
    Yes! Your discussion guide does not need to be finished when you share the link with participants. We encourage you to share the participant link early then continue developing your discussion guide. If participants clicked the link early, they would see a message stating "A conversation will take place here."