Normal user UX knowledge

Learn, share, and connect around europe dataset solutions.
Post Reply
Arzina3225
Posts: 26
Joined: Sun Dec 22, 2024 6:26 am

Normal user UX knowledge

Post by Arzina3225 »

Environment that matches your website or app
With today's prototyping tools, you can get a realistic representation of your concept much faster. So why not test it on the street or on location? The more realistic a group of testers is and the closer a version of the concept comes to reality, the better your test results will be. Depending on the content and market of your product, you can also test more selectively on location to simulate the potential user group. In a bookstore for a book app, or in a cooking store for a recipe site, etc. So in 2018, more on the street, in the shops or in the café!



8. Keep a digital diary
Keeping a user log yourself has long been a good way to gather user information. You give a user the product for a while and let them document what they did, what they encountered during the process and what they think of it all. Fine information in itself, but you are still documenting someone's interpretation. Often you also don't see a lot of things.

Screen capturing
Many devices often have the option to record the screen ( screen capturing ). Of course, you can use this perfectly to register what a user is actually doing. You register from moment to moment malaysia phone number list what goes wrong. And if a path is followed correctly, you also register this at a detailed level. Not only because the user tells you so. You can still ask what they think of it, but the actual interaction moments are documented much more specifically.

Image

9. Cognitive walkthroughs
Instead of using end users to test your solution, you use a cognitive walkthrough (COG-walk) to have a few experts perform a similar test. These are often UX designers or researchers. The condition for the session is that the experts have not yet been involved in the product or solution (so a fresh perspective). Furthermore, the person who contributes the design is not allowed to defend themselves or explain why they chose a particular solution.


The idea behind a COG walk is that an expert knows what is wrong with a product just as well when he or she starts using it as an average home user. He or she is basically a user with a lot of knowledge of UX. With a COG walk you have the additional advantage that a session of 1-2 hours with multiple UX'ers ​​provides a lot of feedback in a shorter time. You do not need a whole test day with a test with a specific user every hour. There is also less chance of socially desirable answers, because colleagues are generally critical of each other and - if all goes well - are less likely to mince their words.
Post Reply