Here's how you can effectively convey user feedback to the design team.

Numerical data and surveys will tell you the story that you want to listen to. Be careful it could be fiction. Candid conversations and observation are the most important ways to collect the data. When you are with the right audience, don't bias them by pushing your point of view.. by framing guided questions. Casually bring them to your product, and watch what they do. Don't guide them, correct them, or explain them a thing. Be a part of their journey and empathize with them. Notice what are they thinking, where their thumb is jumping? What kind of movement their eyes doing and how are their expression changing. My biggest learning so far is that data without context serves egos it doesn't serve customers.

Gather user feedback through diverse channels such as surveys, usability tests, and direct user interactions. Ensure you have a rich and comprehensive set of feedback to represent user experiences and concerns authentically. Tip: Utilize a blend of quantitative and qualitative methods to collect feedback. Quantitative data provides measurable insights, while qualitative data offers a deeper understanding through user stories and detailed comments. This combination ensures a holistic view of user experiences.

Review all raw data, categorize them, then assigned 3 levels of priorities. High-priority items are non-negoatiables i.e. users cannot complete their tasks or their experience will be significantly impacted (to business, that means loss of a customer). These are must-change's. Med-priority items present enough challenges that, if resolved, would significantly improve user's experience (or the brand's reputation). Low-priority items indicate nice-to-have's. Improvements are considered add-on's and not critical.

The most effective reports should include clearly categorized issues and their respective levels of importance (i.e. prioritized). The team is primarily interested in what the result mean to them and their jobs. For instance, presenting critical must-change's up front help technical partners instantly see bugs and help them plan their to-dos (e.g. items in the next sprint) accordingly. Offer to deliver raw data if any member is interested in reviewing them - but it is counter productive to include everything. No one reads a long report, everyone reads a great summary!

Present findings as per the needs of your audience. Remember why people attend the meeting in the first place - to obtain data that help them plan their next moves, whether it is a sprint cycle for developers, or message creations for marketers. Present findings according to their impacts on the UX hence the whole product. High-priority items require urgent attention (and changes are non-negotiable or a tough trade off), medium-priority items if addressed would significantly improve UX, whereas Low-priority items are nice-to-have's only. Having your audience in mind when presenting findings means the findings will be listened to and utilized to truly improve UX, the product, and the business.

Facilitating a good discussion involves keeping an eye on both the content and the participants. You want the conversation to be focused, but also allow for exploration. Ensure everyone participates and actively listens, while keeping the atmosphere respectful and collaborative. By monitoring these aspects, you can steer the discussion towards a productive outcome. Pay attention to Group Dynamics, Participation & Engagement and finally Content and Direction.

All the work and time spent on gathering user feedback and conveying it to designers tactfully isn't worth the effort unless you make the required changes. But tackling changes of different magnitudes can be difficult. Start by categorising each change by it's severity, the time taken to implement, and expected impact. Once the prioritisation exercise is complete, discuss with your team on the next course of action. Depending on business input, you might want to go with easier changes that can lead to quick wins or undertake bigger projects that lead to bigger wins in the future.

Rarely does one need to share all raw data. A short report is a report that will most likely be read! However, always offer to share raw data so everyone can understand where the finding summary comes from.