One thing I have really found usefull is to have regular meeting with users to understand their requirements and get their feedback. Performance issues can be challenging since at time it is difficult to pin point the exact causes. Here it helps to understand what is acceptable performance for a user. Next is to identify where the system is lagging or experiencing performance issues. Is it something that can be optimized ? Or something where some constraints can be relaxed? All of above require a) good command of the tech your are working with, b) domain understanding and c) effective communication with users. Also need to remember, there is no silver bullet.

This is a strange question, waiting for user feedback is not the optimal strategy to identify performance issues. Typically you should have metrics or you must add metrics in order to understand where your problem actually is. If, whatsoever you arrive at a point where users are pointing out performance issues then you must run two parallel tracks: (a) The first track should start investigating the specific flow, trying to identify any issues. (b) The second track should focus on improving (or adding) metrics and other diagnostic tools (logs, traces), starting on the problematic flow and extending across all flows. Finally: Examine the culture, the operating mode and add performance tests and monitoring in the workflow

To incorporate user feedback when addressing performance issues in software design, follow these steps: 1. Gather Feedback: Use tools like surveys, user testing sessions, and interviews to collect actionable insights, identifying pain points in the user experience. 2. Prioritize Issues: Address feedback based on severity and frequency, focusing on issues that most impact user experience, such as slow loading times. 3. Iterative Improvements: Implement changes gradually and gather additional feedback after each iteration to ensure alignment with user expectations. 4. Continuous Monitoring: Monitor performance post-implementation to ensure lasting improvements and maintain high user satisfaction.

To effectively incorporate user feedback into software design and resolve performance issues, first gather feedback via surveys, usability tests, and analytics to identify specific pain points. Prioritize the most critical performance issues affecting user experience. Collaborate with cross-functional teams to refine the design and optimize performance. Implement iterative improvements using Agile principles, releasing incremental updates. Validate changes through A/B testing and collect ongoing user feedback to ensure improvements align with user needs, balancing performance with usability.

When I face performance issues in software design, my first instinct is to panic. But then I remember: user feedback to the rescue! Here’s how I like to handle it: First, I prioritize the drama: If users are shouting about slow load times, I’m all ears (because if they’re complaining, it’s probably legit). Next, I get nosy: I’ll reach out and ask users directly, “How bad is it, really?” (Spoiler: it’s always bad, but their details help). I set some realistic goals: Based on their gripes, I create a simple plan—like “make the app stop freezing.” Then the fun part, fixing it: After we push some updates, I send it back to users. And I keep the convo going: let’s face it, software is never “done,” and there’s always another bug.

I'd say by combining user feedback with data-driven analysis, you can effectively prioritize and resolve performance issues that impact your users most. Also, it's important to communicate with the users how any implemented updates are helping to improve performance, so users know their feedback is valuable and being addressed.

What's mostly important is capturing the user voice itself. we have a desire to quantify things, especially around technical products, that can be done later. Make sure you ask open ended questions, get users explaining their pain in their words, ideally over a synchronous conversation as well as wide surveys, etc Then comes the magic of product triage and research/discovery. finding commonality, prioritizing, deciding on solutions. in this cadence is often as important as the prioritization work itself. it's better to do a lesser work often than deeper one rarely.