Arrow to the left
Back to methods overview

Surveys

While we always recommend meeting and talking to users, sometimes surveys can be a great tool to get a bigger amount of user feedback and a good tool for unmoderated usability tests.
Surveys

How it works

While we always recommend meeting and talking to users, sometimes surveys can be a great tool to get a bigger amount of user feedback and a good tool for unmoderated usability tests.

While we always recommend meeting and talking to users, sometimes surveys can be a great tool to get a bigger amount of user feedback and a good tool for unmoderated usability tests.

Infinity symbol icon
Understand
Clock icon
1 – 4 hours
Users icon
Product Owner, Business Analyst, UX Designer, Developer, Quality assurer
Before

1. Define the goal. Settle on what you want to know and why you need to know it. This is important, as surveys with a clear purpose make for better research results.

2. Write a clear survey intro. The intro should clearly state the purpose of the survey, how long it takes to complete the survey, how the data will be used and for how long you intend to keep the data.

3. Decide how the survey will be sent out, e.g. via email to a list of users, via a popup targeting some or all end-users in your product or via social media.

4. Plan the analysis before sending out the survey. This will keep your survey focused.

5. Do a dry run. Invite team members to see how long it takes to answer the survey and watch out for confusion. You will not be there when the users answer it, so try to make it understandable.

During

6. Send it out! Send the instructions and the survey to your intended target group and await the results.

After

7. Analyse the data. Gather your team and look at the data together. Work to identify patterns and list 5 key takeaways each. Group them and align on prioritisation together, e.g. by doing a thematic analysis.

8. Present and share the results with the rest of the team and internal stakeholders.

9. Put the data to good use! A good next step could be to create user stories and make sure that any need for updates or changes in the product gets prioritised and becomes part of the roadmap.

Tips
  • Only ask the questions you need to ask. A survey should take no longer than 3-5 minutes to complete. The time estimate should be clearly stated in the intro.
  • Ask internal stakeholders, support, sales etc. if they have any questions they would like to ask. This can help you see things from different perspectives.
This is some text inside of a div block.

What’s a Rich Text element?

The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.

Static and dynamic content editing

A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!

How to customize formatting for each rich text

Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.

No items found.
No items found.
Before

1. Define the goal. Settle on what you want to know and why you need to know it. This is important, as surveys with a clear purpose make for better research results.

2. Write a clear survey intro. The intro should clearly state the purpose of the survey, how long it takes to complete the survey, how the data will be used and for how long you intend to keep the data.

3. Decide how the survey will be sent out, e.g. via email to a list of users, via a popup targeting some or all end-users in your product or via social media.

4. Plan the analysis before sending out the survey. This will keep your survey focused.

5. Do a dry run. Invite team members to see how long it takes to answer the survey and watch out for confusion. You will not be there when the users answer it, so try to make it understandable.

During

6. Send it out! Send the instructions and the survey to your intended target group and await the results.

After

7. Analyse the data. Gather your team and look at the data together. Work to identify patterns and list 5 key takeaways each. Group them and align on prioritisation together, e.g. by doing a thematic analysis.

8. Present and share the results with the rest of the team and internal stakeholders.

9. Put the data to good use! A good next step could be to create user stories and make sure that any need for updates or changes in the product gets prioritised and becomes part of the roadmap.

Tips
  • Only ask the questions you need to ask. A survey should take no longer than 3-5 minutes to complete. The time estimate should be clearly stated in the intro.
  • Ask internal stakeholders, support, sales etc. if they have any questions they would like to ask. This can help you see things from different perspectives.

Tool recommendations

Below you will find some tool recommendations, but please note that you are free to choose whatever tool you prefer. For some tools we have group wide licenses, in which case access can be requested via licenses@visma.com. Remember that you always need cost approval from your immediate manager.

Google Meet

Google Meet

Real-time meetings using your browser, share your video, desktop, and presentations with teammates and customers.
Mural

Mural

Mural offers both a shared workspace and training, a practical way to collaborate that anyone can learn and apply.
FigJam

FigJam

An online collaborative whiteboard for teams.
Want to learn more?

Get in touch with Visma UX

Drag
Request access