I recommended conducting user research, but my client considers research and testing to be the same concepts. I am not sure how to explain the difference between research and testing in layman's words.
Can anyone here please advise me on this?
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It only takes a minute to sign up.Sign up to join this community
As @sclarke has already put it, research is done before testing. You can't cook a meal without knowing what the ingredients are. Same with UX, you can't start to test if you don't know what your tests should be.
To know what you should test, you need to know your target audience, to know your target audience you need to research.
Here's my take: User Research is the broader effort, and includes Usability Testing.
User Research also includes maybe the most important work you'll do, getting to know users and their tasks before you design anything. I find the best way to gather this info is to shadow users, simply observing what they do. This knowledge then informs the design decisions you make. Ideally, it determines what thing you build.
(After shadowing for a recent project I concluded that the tool they use is perfectly fine. The users just needed a better layout for the printout they referenced for each task. Of course, a software-development team doesn't want to hear that.)
I'd make it really short and to the point.
User Research is the parent to User Testing i.e there is no research without involving a test process too.
User Research focuses on understanding user behaviors, needs, and motivations through observation techniques, task analysis, and other feedback methodologies. Mike Kuniaysky further notes that it is “the process of understanding the impact of design on an audience.” REF. HERE
It involves the life cycle of the product from the initial design or first prototype iteration (Interaction Research), then the beta version (Testing Research/ User Testing) and finally Production version/Updates (Usage Analytics)
Short answer: They aren't the same.
Long answer: Let's consider what your client is concerned about here. If he's not sure about the difference between both, I can assume he's never done research or testing formally himself. While almost everyone does it informally, the odds and cost of being wrong are much higher.
Research and testing exist at the opposite sides of a design cycle. The research phase will help define the problem and develop a point of view about the people being affected by this problem. Why is this important? It's the foundation of the divergent thinking process, where ideas are generated and the volume of choices makes it more likely that whatever outcome you get will satisfy the end-user. Research is about painting a more clear vision of that ideal future and what it will take to get there (or whether it is even worth going there).
Whereas testing can only tell us about the performance of a single idea turned into a prototype, if the testing uncovers a flaw with the design there is nowhere to go back to and iterate, because the research foundation isn't there.
If you do testing without research and fix the product or service iteratively, based only on the feedback of those you are testing the product with, you'll end up designing a product or service with unclear goals and never know what aspect of it influenced its success or failure. By only looking at testing results it's easy to adopt a framing bias and place more emphasis on the positive results and ignore potential risks.
Proper research will make it evident that bias exists and will provide ways to overcome this by design. We are all biased, that's why we need research, we aren't perfect either, so we need to test. We also don't have infinite budgets, so we need to be smart about reducing the risk of failure.
EDIT: Research can be done at any stage of the design process, in this case, I'm assuming you are trying to bring research at the initial discovery phase.
User testing is research.
There’s formative research which informs ideas - field studies, interviews, other discovery homework, Googling, focus groups, card sorts, etc. - and summative research which evaluates ideas, for example via tree testing, user testing, heuristic evaluation, expert reviews, etc.
You essentially bookend UX design with research anytime you do problem definition up front and then execute and measure design work against that definition.
That’s about as jargon-y as it needs to get, in my opinion. Research is already hard enough to do without definitions and nuances that make it feel like a departmental concern.
As UX is still a very young field a lot of terms have not been properly defined and so are interchangeable.
However, judging by the way you are using them, I would say that in layman's terms User Research is finding out who your users are and what they want and User Testing is finding out how your users interact with your product.
The bit where it can get confusing for your client is that User Testing can form a part of User Research if you're trying to discover how your users interact with the current iteration of your product in order to find out where best to make changes or improvements.
Clarify your terminology. To keep it in layman's terms, specify when in the design process you do each.
Say, "At the beginning, we do exploratory user research to make sure users' real needs and behaviors inform our design requirements. This up-front research includes interviewing real users and observing their behavior in context. Once we have a prototype, we test it with users to see if it works the way we want it to. That's evaluative user research. It includes usability testing."
It's imperative to not only explain user research but also make a simple, jargon-free case for why you need it throughout the design process. Good luck!
Conceptually you are talking about two activities that are complementary and probably are too closely related to separate them into two distinct things.
Regardless of the actual labels that you apply to each of the activities, what you are essentially doing is to try and gain an understanding about the user (i.e. what most people would term 'user research'), and by having a deeper understanding of the user you can then make some assumptions about their behaviour when designing your product and service.
However, you need to validate these assumptions so you apply the knowledge gained about the user in a particular way so as to test its validity (i.e. what most people would term 'user testing'). Where there is a degree of ambiguity is that through the process of validating your assumptions that you also develop a deeper understanding of the user.
So I think it is semantics, but the process of doing research involves observation of the subject, drawing some general conclusions and then testing those assumptions to see if they are sensible to carry over to design. This is an iterative and evolving process, which is difficult to separate into two distinct activities.
I hope that makes things clearer as to why it is confusing to most people.