A continuación, te explicamos cómo puedes navegar por los comentarios vagos o poco claros de forma profesional.

Use open-ended questions to uncover hidden details. Instead of asking "yes" or "no" questions, encourage the feedback provider to elaborate on their thoughts. For example, ask "Can you describe what you expected to happen?" By using this questioning technique, you can uncover underlying issues and gain valuable insights that weren't initially apparent.

Handle ambiguous or confusing feedback professionally by using open-ended questions to get clarification. In order to ensure correctness and show that you are willing to learn more, paraphrase what you know. Take a constructive approach to the criticism and see it as a chance for improvement. Take notes on the criticism and the steps you took to make sure you addressed every issue. Take part in a productive conversation to get particular knowledge that will direct your advancements.

When confronted with ambiguous feedback, your priority should be to clarify it. Pose specific questions that prompt the feedback provider to expand on their points. For instance, if you receive feedback that a design "doesn't feel right," inquire about specific aspects causing that impression. Is it the color scheme, the layout, or the user flow? By identifying the specific areas of concern, you can gather actionable insights to enhance your UX designs.

View feedback as an opportunity for growth. Use vague feedback as a starting point for further exploration. Create low-fidelity prototypes to test different design variations based on the feedback received. This iterative approach allows you to experiment and refine the design, ultimately leading to a better understanding of user needs and preferences.

Why it's important: Taking time to reflect on the feedback helps in understanding its context and underlying concerns. How to do it: Contextual analysis: Consider the context in which the feedback was given. Think about the project goals, user needs, and any recent changes that might have influenced the feedback. Identify patterns: Look for recurring themes or issues in the feedback you’ve received from different sources. This can help in identifying underlying problems. Self-assessment: Reflect on your work and see if there are any areas where you felt uncertain or that align with the feedback given.

Keep the big picture in mind. Evaluate feedback based on how it aligns with the project's overall goals and objectives. Prioritize feedback that supports the project's core functionality and user experience. While all feedback is valuable, focus on implementing changes that directly contribute to the project's success.

Why it's important: Not all feedback is equally important. Prioritizing helps you focus on the most impactful changes. How to do it: Impact assessment: Evaluate the potential impact of the feedback on the project goals and user experience. Prioritize changes that have the highest positive impact. Feasibility check: Consider the feasibility of implementing the feedback, including time, resources, and technical constraints. Align with objectives: Ensure that the prioritized feedback aligns with the overall objectives and vision of the project.

Leverage the power of your team. Involve colleagues in discussions about vague feedback. Different team members bring unique perspectives and expertise, leading to a more comprehensive understanding of the issues. Encourage open dialogue and brainstorming to explore potential solutions together. This collaborative approach can uncover insights that might be missed by an individual.

Dealing with unclear feedback requires collaboration. Engage with your team, stakeholders, or the feedback giver to discuss the points raised. This collaborative approach fosters a shared understanding and can lead to clearer and more valuable feedback in the future. Furthermore, it strengthens professional relationships by demonstrating your appreciation for others' input and your willingness to collaborate for optimal UX outcomes.

Once you have a clearer understanding of the feedback, proceed with thoughtful iteration of your UX designs. Implement adjustments that specifically address the concerns raised, and be ready to articulate your design choices. This iterative approach is crucial in UX design, where improvements are continuously made based on feedback from users and stakeholders. It's essential to document all changes and the reasoning behind them; this documentation serves as valuable reference and aids ongoing communication throughout the design process.

Iterate often if needed, but not out of control. Rather than cycles of long batches of work / changes with clinical or ambiguous reviews in-between, sometimes with not enough time for proper use / feedback loops, we start with a functional prototype earlier in the project (sometimes 1 or 2 weeks in), sometimes ugly, and then keep refining, both visual / UX / development. This allows a natural "evolution", focus groups or client tests for specific features, and saves lots of time in the end, while adding flexibility but being able to being focus on the priority of the week day (rather than long batches of checks through a hundred components or views that will be rushed and most will be missed). More flexible and better for client / team too.

Why it's important: Clear communication ensures that feedback is understood and addressed appropriately, building trust and transparency. How to do it: Regular updates: Provide regular updates to the feedback giver about the steps you’re taking to address their feedback. This keeps them informed and involved. Explain decisions: Clearly explain the rationale behind the changes you’ve made and how they address the feedback. This demonstrates your thoughtful consideration of their input. Seek further input: Encourage ongoing dialogue and invite further feedback to ensure continuous improvement and alignment.