Back to
UX & Content Design
team

How UX Research is Used at QIC digital hub

What is UX research?

As a user experience (UX) researcher, you gather insights on a user’s online behavior patterns, constantly striving for balance in design for customers and business needs accordingly. Think of it as a train, once it’s built, the engineers have completed the major task of getting it to do its job. UX researchers, here, are like inspectors and detectives who constantly monitor it, how it is performing, on the lookout scanning for potential threats, if anything needs the attention of maintenance personnel, and what the primary stakeholder — the customers, think about their experience with it. Then, providing appropriate recommendations to dedicated teams.

In order to form unbiased, factual, and accurate recommendations, UX research is conducted within 4 overall research categories: qualitative, quantitative, attitudinal, and behavioral.

Qualitative asks the questions — Why? How?

Quantitative asks the question — How much? How many?

Attitudinal asks the question — What people say?

Behavioral asks the question — What people do?

These categories are then broken down with different methodologies that can be used to reach conclusive findings, some of these include:

  • Usability Testing: Observing real users as they complete tasks on a product to identify any problems and areas for improvement.
  • Surveys / Questionnaires: Collecting feedback from users through a set of questions to gather opinions, preferences, or satisfaction levels.
  • A/B Testing: Comparing two versions of a product or feature to see which one performs better with users.
  • Analytics: Gathering data on how users interact with a product, such as page views, clicks, and time spent, to understand user behavior and improve the experience.

It is very important to know why you are conducting research and how its results impact business decisions. This not only allows you to plan ahead, but also lets you know which processes to take, what questions to ask, but most important — who to ask those questions to? Sometimes, narrowing down on these questions, you will also realize that primary research is not necessary if user data can be derived with the help of analytics teams.

What do I do as a UX researcher?

I like to consider myself as a sort of ‘corporate nurse’ where I get to listen to user’s concerns and understand their potential pain points. It then allows me to come up with solutions on how their online experience with using QIC products can be improved.

A large part of my job consists of both, primary and secondary researches where I am responsible for:

  • Designing the right approach to a research project
  • Conducting online and offline researches
  • Analyzing competitive market forces
  • Creating and executing UX studies through surveys, interviews, and usability tests
  • Presenting highlights, insights, and conclusions to the product and design teams

A lot of times, it is easy to get prone to our own assumptions which can distance us from what we think is better and what users might find beneficial. These assumptions may not always translate into real-life use cases. A number of things can impact this:

  • Cultural background, people may perceive certain words differently. This can cause a disconnect between what is instructed and what a user understands.
  • If users are native to using technology or if they are someone who were introduced to it later on in life. This can affect how they understand online user flows, or even their ability to trust online transactions with sensitive information.
  • If a user’s sight or physical movements are limited, it may impact how they use technology. Maybe they rely more on voice control features than visual or text based ones.

One of the key reasons why assumptions can form are our own individual biases. Biases exist everywhere in every aspect of our daily life. Human beings are built to recognize patterns and come up with solutions based on past experiences. It is not to say having a bias is a wrong thing. However, when we are conducting research, it is important to list down what possible biases we might have and how they will impact our interpretations.

How do I use UX research in QIC?

A research project starts by defining its purpose, how it will be conducted, who it will include, where it will take place, and how the findings will be implemented. This, of course, is a standard practice for me when approaching a primary research as opposed to secondary. One document template I’ve found very useful is the Google UX Research Template. If you are someone who plans to conduct UX research, I highly recommend abiding by it.

Some of the steps I take in the primary research process include:

  1. Planning: I overview of as many details as possible such as questions to ask, methodologies to be used, KPI’s, number of participants, and how insights will be presented.
  2. Developing: This is the part where I actually have to create the questions and the script for the methodology that will be used — be it surveys, interviews, or a usability test.
  3. Recruiting: In this step, I have to gather participants for the research, depending on the project, who we target to send a research request varies. This can go out in several ways — calls, SMS, WhatsApp, social media, emails, etc.
  4. Conducting: Here, I get to actually do the research, talk to participants, or just something as simple as send out a survey and wait for responses.
  5. Analyzing: The final step in this process is summarizing the results, it is important to look at key findings. A question I like to ask myself here is ‘what information can be derived that can help the product or design team?’

Used Car Market Research

A very important and comprehensive (see what I did there) UX research I conducted was for the used car market in Qatar. The objective of this research was to find all the steps a buyer and a seller must take in order to meet their desired outcomes. This, obviously, starts out with the plan. The questions I had to ask myself in order to create this research plan went something like this:

  • Why are we doing this? This helps me identify what type of questions to ask participants
  • Who are the teams that will benefit from this (a.k.a. Stakeholders)?This impacts how results will be presented and what points to focus on
  • Who do we need to recruit from our customer base? This guides me to know who and how exactly to target participants

My approach when conducting a research like this starts by building a skeleton first. What do I mean by this? Imagine the research plan is DNA in the human body, once we know what needs to be done, we can identify how to build it. For me, it goes something like — skeleton, internal organs, flesh and skin. Once I have filled out as many details in the research plan, I create the ‘skeleton’ which is how the insights will be presented. In this case, it was going to be presented to the design team, therefore, I went for a very visual approach. Next came in the ‘internal organs’ which meant filling in all the details from the user interviews that I had done. Lastly was to add the ‘flesh and skin’ which just meant sculpting the information to limited key points instead of every ‘mechanism’ inside being visible (below is a sample template by Turtle).

What are some challenges I face in my role (at QIC)?

Continuing from the last example, recruiting is one of the main challenges I face in my role. The average conversion rate for interviews ends up being 1–2% from batches of 500 people that I send a participant request for at a time. This is contributed to many things including, but not limited to:

  • People thinking these requests are sent by scammers
  • Them treating me as a customer service agent
  • General unwillingness for their time with very little incentives

All of these are valid reasons for why users are hesitant to partake in these researches. It is important to remember that product and research are relatively new fields in this part of this part of the world. People are not very exposed to the idea of how their feedback impacts the industries around them. Which is fair because sometimes processes and resolutions can take weeks, if not months to get implemented and people, without seeing instant change, assume no one listens to their feedback. Then why bother giving it in the first place?

Moving forward, it has become my priority to make sure that we are able to incentivise our research projects because people’s time is valuable and a simple ‘thank you’ can sometimes not be enough reason to give someone 20–30 mins of your time.

Advice and Recommendations

It is important to remember that you will make mistakes, they are inevitable, but being able to adapt and rectify course is where your strength should lie in these cases. The most common mistakes people tend to make when researching, including myself, are because:

  1. We jumped straight into recruiting participants while not having understood what the end goal is.
  2. We have assumed something to be as factual, creating a confirmation bias that limits our ability to question the root cause of things.

Now, it is important to note you can never be 100% accurate in your findings, but you can get close to 99.99%. That is the goal of each research. I highly advise asking questions to the relevant teams and its stakeholders, clarifying the purpose of why they want a research done, and keeping them in the loop at all times throughout the process. Lastly, I would advise to be unapologetically curious and not fall into the trap of what you already believe to take at face value and perceive it to be true. That’s advice I would honestly give for someone to apply in their day to day life as well.

At QIC, that is what I am making sure that we are able to do to the best of our ability. I absolutely love this role, I enjoy everything it entails, but most importantly, it allows me to gather insights on online users behavior. A very relevant field to the way we engage everyday with the world around us.