What do you do if user testing feedback challenges your design process as an Information Architect?
User testing is a vital part of the design process for information architects, as it helps you evaluate how well your information architecture (IA) meets the needs and expectations of your users. However, user testing can also reveal some unexpected or conflicting feedback that challenges your design decisions and assumptions. How do you handle this situation and use the feedback to improve your IA without compromising your vision and goals? Here are some tips to help you cope with user testing feedback as an information architect.
User testing feedback is not a personal attack or a sign of failure. It is an opportunity to learn from your users and gain insights into their behaviors, preferences, and pain points. Instead of being defensive or dismissive, try to be open-minded and curious about what the feedback means and how it can help you improve your IA. Remember that user testing is not a one-time event, but a continuous process that allows you to iterate and refine your design based on user feedback.
-
Here are some steps that we can take 1. Analyze the Feedback 2. Understand User Needs 3. Collaborate with Stakeholders 4. Iterate and Test 5. Validate Changes 6. Document Learnings 7. Continuous Improvement By following these steps, we can leverage user testing feedback to enhance the design process as an Information Architect and create more user-centered and effective solutions.
Not all user testing feedback is equally valid or useful. Some feedback may be based on subjective opinions, personal preferences, or specific contexts that may not apply to your target audience or general use cases. Some feedback may be contradictory, vague, or unclear. Some feedback may be influenced by external factors, such as the testing environment, the tasks, or the moderator. As an information architect, you need to analyze the feedback objectively and critically, and filter out the noise from the signal. Look for patterns, trends, and themes that emerge from the feedback, and use data and evidence to support your analysis. Avoid cherry-picking or ignoring feedback that does not fit your preconceived notions or hypotheses.
-
Analisar e principalmente identificar os feedbacks como úteis, seguindo um bom roteiro de entrevista ou teste de usabilidade evitamos enviesar o processo. Cabe ao bom designer saber retirar um insight de um comentário, você luta tanto no teste para não enviesar o projeto, recomendo tomar um tempo para reunir todos os comentários e encontrar padrões e consistências entre os feedbacks de diversos usuários e não se limitar a somente um.
User testing feedback is not only for you, but also for your stakeholders, clients, and team members. You need to communicate the feedback clearly and constructively, and explain how it relates to your design goals, research questions, and success criteria. Use visual aids, such as screenshots, diagrams, or prototypes, to illustrate the feedback and show how it affects the user experience. Avoid using jargon, technical terms, or acronyms that may confuse or alienate your audience. Focus on the problem, not the solution, and avoid jumping to conclusions or recommendations without sufficient evidence or rationale.
User testing feedback can be overwhelming and tempting to act on immediately. However, you need to prioritize the feedback based on its impact and feasibility, and balance it with your design constraints, resources, and timeline. Not every feedback needs to be addressed or implemented right away. Some feedback may be more urgent or important than others, based on how it affects the user goals, tasks, or satisfaction. Some feedback may be more feasible or realistic than others, based on how it aligns with your project scope, budget, or technical capabilities. Use a matrix or a framework to help you prioritize the feedback and decide what to do next.
User testing feedback is not the end of the design process, but the beginning of a new cycle of iteration and validation. Based on the feedback, you need to make changes to your IA and test them again with your users. You may need to adjust your navigation, labels, categories, or search features, or create new ones, to improve the findability, usability, and accessibility of your information. You may need to use different methods, tools, or techniques, such as card sorting, tree testing, or wireframing, to test your IA and collect feedback. You may need to involve more users, or different types of users, to validate your design and ensure its relevance and suitability. The goal is to create an IA that meets the user needs and expectations, as well as your design objectives and requirements.
-
Um novo ciclo sempre se inicia assim que obtemos um novo insight, geralmente o processo flui da seguinte maneira: 1 Pesquisa 2 Definição 3 Teste 4 Implementação E o processo é cíclico e não linear, sendo assim, ao chegar em qualquer etapa, identificando assim um novo insight que possivelmente mude o curso do projeto, teste a hipótese, e volte a pesquisar e definir.
Rate this article
More relevant reading
-
Information ArchitectureHow can you effectively discuss your experience with user testing?
-
User ExperienceWhat are the common reasons for A/B testing failures and how can you identify them?
-
Information ArchitectureHow can you select user testing methods that match your project's goals and scope?
-
Information ArchitectureYou're faced with feedback challenging your IA approach. How will you navigate this obstacle?