Testing with limits!
User testing is one of the most important parts of the design process. It’s like receiving scores from real-time users. Even if you conduct it for a tiny feature, just take time. It is not something that can be drawn just in hours.
I recently had the opportunity to perform user testing for the app basense. The result highlighted the fact that I never considered it a problem.
I will break down the steps that I followed.
I simply followed the rule of 4Ws and I reached a result that was satisfactory for me. WHY, WHO, HOW, WHAT. (I omitted the fifth "W"—"Where"—since our product is more global in scope.)
1. Why
To do a test, you should know why you are conducting this test. Are you having a problem selecting a feature, or are you testing single-screen or you are testing the entire platform? Are you testing to know your users or are you testing to know your product?
All in all, The motive should be clear.
Tip: remember, it is very easy to get lost while moving forward with user testing. So always stick to your motive.
All in all, The motive should be clear.
Tip: remember, it is very easy to get lost while moving forward with user testing. So always stick to your motive.
2. Who
Now you have a motive to conduct user testing, here comes the second part of the process. Who is the one you are looking for as your user? When I was studying UX back in 2021, I didn’t completely understand the usage of persona. But in real life, it is really helpful. Persona helps us figure out who our target audience is. We can define factors such as age, gender, educational qualification, technical proficiency, or any other factors we need in our potential users.
Tip: Create at least 2-3 personas for your product to tackle a broader target audience.
3. How
Conducting user testing can be intimidating. What method to pick, was one of the most challenging parts for me. We did many tests within our team (alpha testing) and it didn’t seem the right option to go for another internal user testing. We wanted the perspective of a real potential user.
To figure out the right method for your purpose, consider factors such as budget, facilities available, your product requirement, etc.
To figure out the right method for your purpose, consider factors such as budget, facilities available, your product requirement, etc.
Tip: There can be more than one adequate user testing method serving your purpose. If such a situation comes, I simply list the pros and cons. I then compare which method is the heaviest in the pro list and lightest in the cons list.
4. What
Now that you've identified the appropriate user testing method for your product, the next step is to determine the exact questions to ask your users. To ensure a structured and effective testing process, it's helpful to create a “script”.
The way you approach your users for every task defines the success path the user is going to follow. Hence, you should always pick the easiest and most approachable language so the users don’t feel intimidated by the task.
Here are some steps I followed for user interviews:
a. Prepare a script in advance to guide the session.
b. Make sure the user feels comfortable before starting.
c. Create realistic task scenarios for them to complete.
d. Keep the questions short and simple.
e. Explain the task clearly, but avoid explaining the product—that's what they're here to figure out.
f. Pay attention to their reactions, expressions, and how they approach the task.
g. Encourage users to share their honest opinions.
h. Remind them that there are no wrong answers.
a. Prepare a script in advance to guide the session.
b. Make sure the user feels comfortable before starting.
c. Create realistic task scenarios for them to complete.
d. Keep the questions short and simple.
e. Explain the task clearly, but avoid explaining the product—that's what they're here to figure out.
f. Pay attention to their reactions, expressions, and how they approach the task.
g. Encourage users to share their honest opinions.
h. Remind them that there are no wrong answers.
By following these rules, I ensured that I was there to observe and learn from the user’s experience, rather than to direct or correct them during the testing process.
5. Recreate the Testing Environment
Once you've prepared a standard script, use it consistently with every user. This way, all participants have the same experience, and it helps prevent any bias in their responses.
6. Analyze the findings
Now comes the time when all the responses will be noted down in a systematic way for the entire team to understand. Here is how you can do that:
Gather Data: Collect all notes, recordings, and feedback from the tests.
Find Patterns: Look for recurring issues or similar suggestions from different users.
Prioritize Issues: Rank problems based on how often they came up and how much they impacted the user experience.
Quantify Data: Analyze any numbers or ratings to spot trends and measure performance.
Synthesize Insights: Combine user comments with data to see what’s working and what needs fixing.
Make Recommendations: Suggest specific changes or improvements based on the analysis.
Discuss Findings: Review the results with the team to ensure everyone agrees with the recommendations.
Document and Share: Write up the findings and share them with the team, including all evidence and context.
Voila! You’ve got your user testing results ready. If this is your first time, it’s normal to miss some details or forget things. That’s okay. Learning from these experiences will help you do even better next time. :)