Stakeholders doubt your feedback incorporation skills. How will you prove them wrong in product design?

No communication = No Trust Trust is a function of communication. So Increasing the latter ultimately increases Trust. Also, validate their fears and incorporate their suggestions.

Actively engage with stakeholders throughout the product design process. Attend meetings, ask for their input regularly, and ensure they feel heard and valued. This proactive approach builds trust and demonstrates your commitment to incorporating feedback. Example: Schedule bi-weekly meetings with key stakeholders to review design progress and discuss their feedback. Take detailed notes and share a summary after each meeting, highlighting the feedback received.

Open communication and showcasing the insights gathered is the primary step to address this situation. Scheduling consistent meetings with the stakeholders to have feedbacks and sharing valuable inputs also plays a crucial part.

- Start by understanding their behavior, objectives, and thought processes. - Actively listen to their inputs, show respect, and involve them in discussions. - Be transparent about how you prioritize the backlog and roadmap, clearly explaining the rationale behind decisions. This engagement will demonstrate your commitment to incorporating their feedback into product design.

Schedule regular check-ins, listen attentively to their input, and demonstrate how their feedback is being implemented. This proactive approach builds trust and showcases your commitment to continuous improvement.

In my experience, involving Executive in the demo day of your design sprints is the best format. This way they can experience the raw feedback from the very first experiments with real users. One simple tool I used, is video snippet from interviews placed on a journey map. We call it our Wall of pain.

Maintain transparency about your process for gathering, analyzing, and implementing feedback. Share your methods and timelines, and explain how feedback will be prioritized and integrated into the design. Example: Create a public roadmap or feedback tracker that stakeholders can access to see what feedback has been received, how it’s being addressed, and the expected implementation timeline.

I agree with Samuel; demo days are so valuable. Once, we had high-fidelity mocks (with production data) for our stakeholders to play with. At some point, they forgot that it was a mock and started clicking around with some of the data shown in the mock. This sparked a great conversation that gained stakeholders' trust while, at the same time, it showcased to the stakeholders that we understood and cared. We had a way higher conviction about our product designs afterward.

Transparency in your process is key. Use project management tools like Trello or Asana to share your design process and how feedback is being incorporated at each stage. In one project, I created a dedicated board where stakeholders could see their suggestions, the status of each, and how they were being addressed. This level of visibility assured them that their feedback was not just heard but acted upon.

Make their inputs visible and demonstrate a clear understanding of their objectives throughout the product development process. Use tools to log and showcase their inputs, and explain how you prioritize them based on product vision, short-term goals, customer satisfaction, and business values. This transparency will show stakeholders how their feedback is actively shaping the product design.

Reflecting on my experience of taking feedback from the management, it had always been difficult for me, especially when there was so much effort poured into working on the wireframe, convincing stakeholders, etc. Understanding the 'Why' and 'How' of the the feedback would help in betterment of the product and then acting on it always helps. If it still doesn't make sense to you, be transparent and ask for more reasonings for it. Ultimately, it's your call and you should be the one to know what is best for the product. A third person's perspective always helps 'zoom out' and look at things from a different angle.

Do not be rigid in terms of pushing back the feedback received or implementing it, rather understand - WHY is it important to implement, by WHEN it is needed, WHAT will it impact and HOW it will be delivered. Using an URGENCY vs. PRIORITY matrix here to action on the feedback and keeping it very transparent for stakeholders to see and react is important. That will demonstrate your drive not only towards improving the product but also building confidence with your stakeholders that their opinion is valued. The first step as a product manager is to actively and intently listen to the feedback, understand the use case from their point of view then it should be prioritised accordingly.

Show that you are willing and able to adapt your design based on feedback. Highlight specific changes made as a direct result of stakeholder input and explain the rationale behind these changes. Example: During design review sessions, present before-and-after comparisons to illustrate how stakeholder feedback influenced design decisions. Clearly explain why certain changes were made and how they improve the product.

Demonstrating adaptability can be quite tricky considering that the stakeholders are already challenging the skills. But it is vital to showcase because rebuilding trust is the most essential for the team to value your insights. By being open to change and pivoting as soon as change hits, it showcases the commitment to evolving.

Provide examples of changes made based on feedback, and explain the rationale behind these adjustments. This demonstrates your responsiveness and commitment to improving the product.

Establish a prioritization framework by carefully identifying the tangible and non-tangible parameters to be considered for feedback analysis. Weigh every feedback against the framework and prioritize them. Establish a communication channel to provide status on feedbacks suggested. Clearly communicate the product versions in which the feedback will be considered and associated rationale. Leave the channel open for any additional requests.

Feedback are gifts be thankful for the same if it does not help . Feedback itself is the solution for this , you need to give an update back if the feedback is considered, if not you should communicate why that will not be incorporated. No response is the worst response

Feedbacks form the most important part of product development. It is essential to collect feedbacks from all the stakeholders possible and act upon the ones that are in align with the vision of the company and the product. Contiguous feedback loops will lead to iterating the product which is the most important for a product to sustain the market.

Creating a robust feedback loop is crucial in product design. As a PM, here's how I ensure every stakeholder's voice is heard & valued: - Active Listening Sessions: Regular check-ins where feedback is gathered. E.g.: Bi-weekly open forums where all team members can voice concerns & ideas - Integrate Feedback Early: Embedding feedback in initial design stages. E.g.: MVP iterations based on customer feedback to refine product features - Transparent Follow-Up: Showing stakeholders how their feedback influenced decisions. E.g.: Sharing updates in roadmap meetings & highlighting implemented suggestions - Continuous Improvement: Adopting an agile approach to refine & iterate. E.g.: Sprint reviews focusing on feedback outcomes & next steps

Establish a continuous feedback loop where stakeholders can provide ongoing input and see their suggestions reflected in iterative design updates. This loop ensures that feedback is not only collected but also acted upon in a timely manner. Example: Implement a feedback portal where stakeholders can submit their suggestions and track the status of their feedback. Regularly update this portal with progress reports and changes made.

I believe metrics and KPIs can showcase your feedback incorporation skills! Use metrics such as user satisfaction scores, NPS, task success rates, and engagement metrics as quantitative data to show improvements. Plus, share user testimonials and case studies that underscore the positive impact of feedback on user experience and satisfaction.

Regularly showcase the improvements made to the product design as a result of stakeholder feedback. Highlight how these changes enhance the product and address specific stakeholder concerns. Example: Organize demo sessions or create visual mockups to highlight design changes. Share these updates via email newsletters or during stakeholder meetings to keep everyone informed and engaged.

Conducting demos or dry runs prior to release for features came in as a request via feedback, involving stakeholders who gave the feedback in the process and validating if it fits the purpose as asked for is a good way to showcase improvement and build confidence with them that they are being heard.

Use data and metrics to illustrate the impact of changes implemented based on feedback. This demonstrates the tangible outcomes of listening to stakeholders and reinforces the value of their input.

Showcase tangible improvements driven by stakeholder feedback. Use before-and-after comparisons in presentations to highlight the impact of their contributions. In one project, I created a visual storyboard that mapped the product’s evolution based on feedback. This not only showcased improvements but also validated the stakeholders’ role in shaping the product.

Reflect on the feedback received and the changes made. Continuously learn from this process to improve your feedback incorporation skills. Share your learnings with stakeholders to demonstrate your commitment to continuous improvement. Example: Conduct a retrospective after each major design milestone to assess what worked well and what could be improved in the feedback incorporation process. Share these insights with stakeholders and outline steps for future improvements.

Have a centralised way of collating all feedback that can be easily shared and accessed by all stakeholders. Having a defined process is important here to action on the feedback. I've several times used Monday.com or Google sheets to have information that not only gives WHAT is the feedback but also WHY is it important to implement, by WHEN it is needed, WHAT will it impact and HOW it will be delivered. Using an urgency vs. priority matrix here to action on the feedback and keeping it very transparent for stakeholders to see and react is important. Do not take note of the feedback and go straight to implementation, but have regular checkpoints to drive progress and build visibility around it.

Here's how: 1. Showcase Documentation: - Maintain a record of all feedback received - Highlight instances where feedback directly influenced design decisions. 2. Visualize Impact: - Create mockups or prototypes demonstrating how feedback was incorporated. - Use A/B testing results to showcase the positive impact of implemented changes. 3. Foster Transparency: - Share feedback summaries with stakeholders regularly - Conduct collaborative design workshops to involve stakeholders - Be open to discussing rationale behind design decisions even when feedback wasn't fully implemented. 4. Focus on Outcomes: - Track key metrics that align with the implemented feedback. - Show how changes have improved UX, engagement and other goals.

Keep all the feedback visible to stakeholders, you can use simple excel to JIRA or notion board. But ensure that every thing is captured and all the actions taken are visible to stake holders all the time.