Interested in launching a remote user test? In this article, discover the various stages involved in writing user testing protocol and devising usage scenarios that will enable you to both achieve your objectives and build a better experience for your users.
Interesting in listening to the market's views, we asked 100 decision makers from the digital sector about their approach to testing. What emerged was a picture of a contradictory situation, with practical obstacles on the one hand and undeniable benefits on the other.
Users are the sole arbiters of the success or failure of a website or mobile app. Through the ratings and reviews they leave on the app stores, they choose whether to encourage or discourage other potential users. And it's the same with a website: 62% of visitors will abandon it if they encounter browsing difficulties (source: 2016 IBM study). Why conduct user tests? The answer is self evident.
The process of redesigning your website has begun and you're planning to do it in agile mode. Whether it's being carried out internally or together with your web design agency, everything is ready and in place: the scrum master, the agile sprints, the test and learn approach. Or nearly everything that is. Because, bizarrely, you haven't planned as many tests as you have sprints.
Only 4 months long, 201(4) was a very short year. A lot happened during this time: we gathered a community of 1,832 awesome testers, collected 6,590 relevant feedback while testing 30 different sites and mobile applications.