Showing posts with label analysis. Show all posts
Showing posts with label analysis. Show all posts

Saturday, 28 November 2015

6 most often used User Research techniques

I find it amazing how often very similar problems require notably different approaches in order to be solved successfully. So far I’ve found this holds true for just about anything in life and, by extension, usability research as well.
Usability research is all about observing and understanding user behaviors, needs and methodologies. Mike Kuniaysky says that it is “the process of understanding the impact of design on an audience.”
It follows that Usability specialists are problem solvers with many tools (research techniques) at their disposal. I bring you a breakdown of some of the most commonly used user research approaches;

Usability Testing

Usability Testing is a research technique which helps us evaluate a product or service by testing it on its representative users. In order to eliminate outside disturbances and allow the researcher to better take notes of the entire process, it is preferably done in a controlled environment such as a lab, but can also be done remotely or in a room where we can ensure no disturbances or distractions. Often it is filmed or videotaped, but doing so is not a requirement as long as someone is closely observing the user and taking notes.
The goal of Usability Testing is to identify any usability problems, collect qualitative and quantitative data and to determine the participants’ satisfaction level with the product or service we are testing.
In order to achieve that, we measure various factors such as time needed to perform tasks, error and success rates, preference for alternative solutions and, of course, users’ subjective level of satisfaction.

A/B Testing

Sometimes also called “multivariate testing,” “live testing,” or “bucket testing”, it is perhaps the most straightforward form of testing.
A/B Testing is merely comparing effectiveness of two different versions of the same design or product by launching them both under similar circumstances.
In context of web pages, A/B Testing would mean launching two different versions of the same web site at the same time. The goal here is to see which version of the web page (A or B, with A being the control version and B being the variation) ends up giving us a higher conversion rate.

Quantitative Survey

A Quantitative Survey is a survey or a questionnaire distributed to a large number of participants; usually a representative sample of our target market, in order to hear their opinions strictly on a subject we are testing and need input on.
It is important that the questions in this type of a survey are closed, meaning that the respondents are choosing from specific selection of answers and are not given an opportunity to expand or elaborate on their responses.

Web Analytics

Used as tools for business and market research, Web Analytics help us assess and improve the effectiveness of a website. Web Analytics are done by collecting, measuring, analyzing and reporting on various web data obtained by web servers, tracking cookies and so on.
By obtaining data from a large number of users we can highlight patterns in navigation and user types as well as focus on answering specific questions such as “How many people visited the site?”, “How many of these visits were unique visitors?”, “How did they come to the site?”, “How long did they stay and how much time did they spend on each particular part of our site?”, “Which keywords did they use in their search which brought them to the site?”, “What keywords did they search with on the sites’ search engine?”, “How does the day of the week or a time of a day affect user habits?” and many, many more.
When performing web analytics we use various software to collect a large amount of data, but it is up to a Usability Specialist to interpret the data and come to concrete conclusions and ideas on how to utilize the data we’ve collected in order to improve the UX.

Focus Groups

Using a Focus Group, a Usability Specialist will lead a moderated discussion with 4 to 12 participants. This discussion will be lead in a controlled environment- just like a Usability Testing session.
The goal of a Focus Group is to gain verbal and written feedback through discussion and exercises and to explore preferences (and reasons for those preferences) among different solutions.
Although Focus Groups are definitely a powerful tool when it comes to system development they are never used as an only source of usability data.
This is because the feedback we receive from Focus Groups is subjective, and therefore should be taken with a grain of salt- especially in cases where the users are asked to describe how they perform activities which span many days or weeks.
Hence, we do not use Focus Groups to assess interaction styles or design usability, but to discover what the users want from the system they are using.
Sometimes what we, the developers, want to give the users isn’t what the users actually need from our websites and apps and this is why Focus Groups are a valuable source of information; they help us align our views with the views and needs of our average user.

Central Location Test

A Central Location Test (or interview) employs both quantitative and qualitative research techniques, as well as visual techniques such as monitoring the respondents’ eye movements and testing for degree of recall of particular elements of a website, app or a product.
In a controlled environment, groups of 15 to 50 people are shown demos or allowed to use products before being interviewed or taking a survey to measure their grasp of the concept, the appeal of various features and the desirability of the product.

CLT is the most suitable method for testing concepts, new or modified products or packaging, advertising effectiveness and sensory research.

References : View Original link to article

About Author:

Ines Anić (@i_anic) is a Content and Administrative Associate at UX Passion, where she writes about UX, UI, design and social media management. She is passionate about UX, Usability, design and video games; and curious about technology, gadgets, IT and the world of startups. Ines is looking forward to connecting with you on LinkedIn and Twitter!
Share:
Continue Reading →

Monday, 4 May 2015

How Web log analysis helps in Revamping an application


For a User Experience Design Team, there is a lot of work to revamp the different kind of 'Websites, web apps, mobile apps' like 'e-commerce, Enterprise apps, service based apps' etc.
Before getting hands dirty in designing a new app, UX team should always start the work with UX strategy and research work. Always identify the prime goals, objectives and User's pain area.
For identifying the User's pain points and insights there are several methods, like User Interview, studies and web log analysis. In this article we are learning about 'Web Log analysis' and how it helps in revamping application.

Web Log 

Web logs are data recorded based upon activity of user on any website or app. Some of the data are given below,
Number of visits and number of unique visitors
Visit duration and last visits
Days of week and rush hours
Number of page views
Most viewed, entry, and exit pages etc.

How Web log analysis helps in Revamping an application

With the help of web log data analysis UX design team can get lot of insights about the application.

1. Hit count log analysis

This data will be helpful in analyzing the usage of  different sections of application. By this we will be able to understand what are our primary functions.

2. Location wise usage analysis

This will help in understand the global usage of application. 

3. Tickets raised against application

This is very imp data because it tells about exact problems which users are facing in application. Analyses of  this data will help in understand the areas of opportunity.

4. Feedback received from user's

From this data we can take the insights and inferences for new application. 

5. Entry and exit pages

This will help in analysis navigation and from where users are dropping off.
Share:
Continue Reading →

Friday, 1 May 2015

Usability of Error messages



While designing ‘Error’ messages or ‘Error’ page for website, mobile site or any application, we should always keep ‘Usability of Error messages’ in mind. Error can come from user or by system (back end) but our system should show error messages properly. Heuristic Principles are the source for getting inspiration for designing it. Some of the key tips mentioned below to make ‘Error’ messages helpful.

Tips for 'Error Message' Usability

1. Don’t use Technical jargon in Error messages

Heuristic Principles - Match between system and real world
Many websites or interfaces show ‘Error’ messages in technical terms like ‘Null object exception’, ‘Java Lang etc file is missing’ etc. First of all understand carefully that normal user is not able to comprehend it. Show the error messages in plain text and in simple language.

2. What Error is occurred?

Heuristic Principles - Visibility of system status
Always show the error upfront to user and written in plain language that user can understand.


3. Reason or cause for this error

Heuristic Principles - Visibility of system statusTell why this error has been occurred, if user has made any wrong action or error is coming from system back-end, show the reason.


4. What should a user do now?

Heuristic Principles - Help user diagnose and recover from error
If error has been occurred and you have told him/her the reason next step is to show what he/she can do now. Like contact admin or choose correct path or make correct entry or wait for some time.


5. Help or direction for further steps

Heuristic Principles - Help user diagnose and recover from error & Help and documentation
Provide complete information about user actions. If user has to contact to Admin then show the contact details about Admin, if user has to wait then show how much time, if user has to make correct entry in any form then help him by providing a dummy entry.6. Be polite and humble

Don’t forget, user is in trouble because some error has been occurred in his/her system. At this time tone of error messages should be polite and relaxing to user.

Showing error messages - 






Best example of presenting Error message  - 





Share:
Continue Reading →