Lab
Goal
To measure is to know
Be certain your solution works and is relevant for the end-user. Will your design work out the way you intended it to?
![research strategy lab](/img/lab.png)
A/B Testing
![A/B Testing](/img/cards/lab-AB-testing.png)
Why?
A minor change in a design may alter user behaviour in ways that are hard to detect in a usability test. An A/B test allows you to compare real-world user behaviour across different versions of the product.
More infoBiometrics
![Biometrics](/img/cards/lab-biometrics.png)
Why?
To get objective data about users' attention and physical state.
More infoField Trial
![Field Trial](/img/cards/lab-field-trial.png)
Why?
Participants never act completely naturally in a lab setting, so consider testing your product in the 'wild'. This can be particularly valuable when real-life disturbances are important for your design, as is the case with mobile apps.
More infoOnline analytics
![Online analytics](/img/cards/lab-web-analytics.png)
Why?
Gain insights from real usage statistics in order to continue improving a website, app or social media campaign after it is in use, or monitor it's use for marketing purposes.
More infoSecurity test
![Security test](/img/cards/lab-security-test.png)
Why?
Connected products and online services are prone to misuse by rogue users. Security tests identify weaknesses of the system and thus help prevent misuse.
More infoThinking aloud
![Thinking aloud](/img/cards/lab-thinking-aloud.png)
Why?
Understand the reasons behind user behaviour, or uncover the mental models of the user in a usability test.
More infoUsability Testing
![Usability Testing](/img/cards/lab-usability-testing-anim.gif)
Why?
Detect problems users have with your design and correct these before the product goes live.
More infoWizard of Oz
![Wizard of Oz](/img/cards/lab-wizard-of-oz.png)
Why?
A Wizard of Oz: acting out the systems functionality, can help when a system has not been build yet, but a realistic user test is necessary to drive design.
More info