How to test your solution with real users?
Testing your prototype against real users is a crucial stage in the process of creating a product. This is where you test your hypotheses and reveal how effective and efficient your design is. However, we know that it is not always easy to receive criticism or to see that your creation does not work exactly as you expected. That's why it's essential to face this process without ego getting in the way.
Why shouldn't you give instructions?
When you deliver a prototype to a user, it can be tempting to explain how it works. However, doing this could detract from the testing process. Your product should be intuitive and self-explanatory. If every user needs instructions to get started, there are probably usability issues that you need to identify and address.
- Don't accompany each person with "technical support".
- Document the times when the user gets stuck or misunderstands how to use the product.
Why is it important not to guide or correct?
During testing, the main goal is not to prove that the product works, but to observe how the user interacts with it. Guiding or correcting the user would break this genuine observation.
- If a user makes the wrong choice, just take note.
- Observe their decisions without intervening to better understand the actual design.
What does it mean to enunciate the thought?
Enunciating the thought involves asking users to express out loud what they are thinking as they interact with the prototype. This provides valuable insight into the user's logic and expectations, revealing how they perceive and understand the product.
- Invite users to share all the thoughts that cross their minds.
- Write down these comments to identify patterns of behavior and areas for improvement.
How to analyze testing results?
After completing a testing session, it is vital not only to recognize the aspects that work, but also to understand the reasoning behind their success. Likewise, identifying what doesn't work is key to the continued development of the prototype.
How do you identify the minimum viable product?
The goal is to discover what aspects of your product are vital to users. From this understanding, you will be able to accurately define the minimum viable product (MVP), that basic set of features that bring real value to users.
- Reflect on what parts of the product worked and why.
- Analyze user interest in certain features.
How do you deal with distracting elements?
During the testing process, it is also important to pay attention to embellishments or elements that distract the user from the central goal of the product. These can be graphical or interactive elements that, while appealing, detract attention.
- Evaluate which elements do not contribute to the main objective.
- Consider simplifying or eliminating unnecessary components.
What is the next step after testing?
The testing process does not end with the first round of testing. After gathering feedback, it's time to go back to the design board, tweak the prototype, and repeat the test cycle.
- Look at the prototype product with a new critical eye.
- Generate new ideas based on the feedback and results obtained.
- Prepare for another round of testing with the improvements implemented.
Continuous improvement is the essence of Design Thinking, and iteration is fundamental to perfecting your product. Here you not only cultivate a better product, but also empower yourself to be a better creator. Go ahead, your product has an exciting road ahead!
Want to see more contributions, questions and answers from the community?