What do you do if your feedback on UX wireframes and prototypes isn't helpful or constructive?

Try to steer the conversation in line of the customer objectives and UX outcomes. Wireframes are not for design details like color, font types etc. This conversation should be about the customer journey and how the flow will guide the user, keeping UX outcomes at the forefront.

When feedback on UX wireframes and prototypes isn't helpful or constructive, it can be frustrating. Here's what you can do: Seek Clarification: Ask for specific examples or details to better understand the feedback. Encourage Specificity: Request specific suggestions or improvements rather than general comments. Provide Context: Share design goals, user research insights, and constraints to help reviewers understand the design. Educate: Explain UX design principles and the rationale behind design decisions. Iterate and Test: Make changes based on feedback and test with users for validation. Engage in Dialogue: Discuss feedback with reviewers to collaborate on solutions.

The first step is to understand the root cause. Then, engage in open dialogue to clarify expectations and preferences. While doing this, encourage specific suggestions rather than vague criticisms. Ensure to collaborate closely with stakeholders to align on objectives and iterate accordingly. Remember, feedback is an opportunity for improvement, not a setback.

If your feedback on UX wireframes and prototypes isn't helpful or constructive, there are several steps you can take to address the situation: Clarify Expectations: Ensure that stakeholders understand the purpose of providing feedback on wireframes and prototypes. Clearly communicate what type of feedback you're seeking and the specific areas or aspects of the design that you'd like them to focus on. Provide Context: Help stakeholders understand the context of the design decisions by providing background information, user research insights, and rationale behind the design choices. This can help them provide more informed and constructive feedback.

If your feedback on UX wireframes and prototypes isn't helpful or constructive, it's essential to reassess your approach to providing feedback and communication. Firstly, ensure that your feedback is specific, actionable, and focused on the objectives and requirements of the project. Avoid vague or subjective comments and instead provide clear suggestions for improvement based on usability principles and best practices. Additionally, strive to maintain a collaborative and supportive tone in your feedback, fostering an environment where designers feel comfortable asking questions and seeking clarification. Encourage open dialogue and discussion to ensure that feedback is understood and integrated effectively.

Nesse caso para obter mais clareza é importante conversar genuinamente com os usuários e entender de fato qual a dor deles. Elaborar uma matriz csd acredito que fa?a bastante sentido nesse caso também. Assim, terá mais visibilidade e por qual caminho seguir já com os insights mapeados.

I am always a huge advocate for supporting everything you can with user data. I remember one particularly painful meeting with a bunch of senior stakeholders who invested thousands of pounds into a project that wasn't seeing the results they wanted. I had the uncomfortable task of doing some UX research to understand why this was happening and presenting to them. What I found was they built a product that ultimately the customers had no need for and solved no real pain points for them. Presenting this, I made sure to back up every point with a user quote, which helped immensely in providing backup to any irrelevant feedback or comments coming from the senior execs during the presentation.

Listen, you get what you put into it! Only submit quality deliverables! ???? Share Annotated Wireframes - Instead of basic wireframes, provide annotated versions. Use comments, callouts, and even user personas within the wireframe to explain specific design choices and their purpose. ???? Share Interactive Prototypes - Share your Figma prototype that allows stakeholders to experience the user flow firsthand. It’s more engaging and provides clearer insights into user interaction. ???? Share User Research Insights - Share key user research findings to back up your design decisions. I believe this demonstrates a data-driven approach and can have more stakeholder buy-in.

I tend to frame the conversation around usability goals. I simply explain how specific design elements contribute to the user experience. When stakeholders understand the reasoning behind design choices and their impact on usability, they're more likely to buy into the design direction and support its implementation.