Research and insight
As designers we always want to keep guessing and assuming at a minimum. Quantitative research helps us answer questions like what do users do and how often, while qualitative research methods tell us how and why.
There are more ways to do research and gather insight and data than we are able to mention.
To choose the method that is most likely to give you the answers you need, you need to know exactly what the question is.
A good tip to get a clear definition of what you want to discover: Ask yourself how you'll use the insight and data you'll end up with. If you're not sure, maybe you're not asking the right question.
Qualitative research
Here's some of the methods Gjensidige designers typically use:
- Usability testing: Give the user one or several tasks to complete on a website or prototype
- Guerrilla testing: Recruiting users and conducting large-scale tests can be time consuming. Sometimes you can just bring your prototype to the streets, and ask passer-bys.
- User interviews: These are especially good for discovering needs, and are commonly used to gather information before we start building anything. The same rules go for interviews as usability tests: a representative sample of users, and prefreably at least 5 of them to start seeing tendencies.
- Focus groups: Much has been said about focus groups, where criticism mostly points the risk of group think. Used with caution it might still give useful insight. Gather 6-8 people within your target group and facilitate a discussion around a topic or set of issues.
- Text understanding: To test understanding of title and lead text: and which expectations your choice of words are creating: Ask the user to predict an article's content based on these two alone. You can also have people read your texts and then ask them to explain the essence of it to you, which lets you understand which parts that stick. You can also ask follow up questions to double check if something is hard to understand.
Quantitative research
It''s not always easy to draw the line between data and analytics and quantitative research. Some draw a sharp line between traffic numbers and event tracking on one side and A/B-testing on the other.
- Fake door testing: Test whether the users show an interest in a product or service before it is developed. More in fake door tests at Contentsquare.
- A/B-testing Want to compare two alternatives? Give half of your users one option, the other half gets the other option. See which alternative performs the best. We have a feature for this in Content studio.
- Tree testing: This is a good way to test both wording and logic in navigation and menus. Give users your information architechture as a plai tree structure hierarchy and ask them where they'd go to find x and y.
- Card sorting: Ask the user to sort topics and headlines in groups for information architecture purposes. Can be done automated as a survey (quantitative) or more qualitatively as interviews or focus groups, which makes it possible to
- Feedback widgets. As hwe all know: The "did you find what you came for" texts in the bottom of a page is by no means an accurat number. It may be useful anyway: For instance will substantial spikes in "no" after a change is a clear hint that this might need a second look.