Your design proposal was rejected. How can you resolve the misunderstandings that caused it?

Seeking feedback is crucial in product design because it provides diverse perspectives, helps identify potential issues, and uncovers areas for improvement. Feedback ensures that the design meets user needs and expectations, leading to a better user experience.

It's not just about asking where things went wrong but understanding their perspective and what they envision. This approach has turned rejections into rich learning moments for me, refining my designs more than I thought possible.

Pergunte ao cliente ou à equipe o que n?o funcionou na proposta. Perguntas específicas podem revelar pontos fortes e áreas de melhoria. Preste aten??o nas críticas e evite ficar na defensiva. Entenda as preocupa??es e necessidades do cliente. Reflita sobre o feedback recebido e identifique padr?es ou pontos recorrentes que possam ter causado a rejei??o. Com base no feedback, ajuste sua proposta ou desenvolva novas solu??es que atendam melhor aos requisitos do cliente. Mostre ao cliente que você compreendeu as críticas e explique como você planeja abordá-las na revis?o. Use a rejei??o como uma oportunidade de aprendizado e continue aprimorando suas habilidades e abordagens para futuras propostas.

To resolve misunderstandings that led to a rejected design proposal, initiate a constructive dialogue with stakeholders to understand their concerns and expectations. Clarify the design objectives and rationale behind your proposal, addressing any miscommunications or missed requirements. Incorporate stakeholder feedback into revised designs, emphasizing how adjustments align with project goals. Present updated prototypes or visuals to illustrate proposed changes and ensure clarity. Finally, reaffirm your commitment to achieving a shared vision by actively listening and collaborating to bridge any remaining gaps in understanding.

To resolve misunderstandings after your design proposal was rejected: Seek Feedback: Ask for specific reasons behind the rejection. Clarify Intentions: Explain the rationale and benefits of your design. Listen Actively: Understand stakeholders' concerns and perspectives. Collaborate on Solutions: Work together to address issues and find common ground. Revise and Resubmit: Make necessary adjustments and present an improved proposal. This approach fosters better understanding and increases the chances of acceptance.

I lay out all feedback and look for common threads or areas where there seems to have been a disconnect. It's crucial to separate the wheat from the chaff, identifying constructive criticism that can steer improvements. By approaching this analytically, I've turned many a rejection into a roadmap for success. embrace it, learn from it, and let it guide your next steps

As designers we know what empathy is. But more often than not we put ourselves in the shoes of the user. But, putting ourselves in the shoes of clients will also take it a long way. Understanding why the feedback was given, analysing where the feedbacks are coming from will help you make better design decisions.

Start by carefully dissecting the feedback you received. Categorize it by theme and identify recurring issues or suggestions. Prioritize feedback that provides specific and constructive criticism you can translate into concrete design changes. Ensure your revised design aligns with the project's initial goals and objectives. Don't stray too far from the original vision unless there's a compelling reason to do so. Don't get caught up in endless refinement loops. Make targeted changes that directly address the feedback while maintaining the design's core strengths.

Adapt your communication style to your audience. Use technical jargon with developers but focus on user benefits for stakeholders unfamiliar with design terminology. Schedule meetings or demonstrations to walk stakeholders through the revised design. Use visuals like mockups, prototypes, and user flows to clearly illustrate the changes. For your team's reference, update internal design documentation to reflect the revisions made. This ensures everyone has access to the latest design specifications. Frame the revisions as an opportunity to improve the design based on valuable feedback.

Following up with stakeholders after a meeting or presentation, or following up on the status of a project or task. Summarize the key points discussed, decisions made, and any action items assigned. Clearly outline the next steps in the design process and who is responsible for each task. Include any relevant materials discussed in the meeting, such as mockups, presentations, or revised design documents. This serves as a handy reference for stakeholders. Keep your follow-up communication concise and focused. Highlight any roadblocks, delays, or need for additional information or decisions from stakeholders.

Sometimes fighting for your designs are good too. Just taking the feedback and working on it will not always make sense. If you have a logical reason as to why the design feedback will not help the product, speak it out, have a debate, and come to a middle ground.