Great design in software turns negative feedback into a positive development process. One such strategy involves creating a feedback loop where the user can actually see their suggestions acknowledged and acted upon, creating a sense of community and collaboration. Another way is to do A/B testing with new features based on user feedback, to see which changes actually improve the user experience. Also, it's good to provide a transparent roadmap on future features and improvements so that it can manage users' expectations and continuously show them the development process.

I would say this is a great point to turn a product into a great product. since the net promoter score could not be more leaner with less outliers. group the feedback into category, quantify the impact and time it take to remediate. form there it should be quite clear which task to pick and go through. the key is closely look at the net promoter score and changes on it to make sure you're on the right trajectory.

I like to incorporate negative feedback with what I call CORE guiding principles. C is for Care. Take care of users. As a designer you should know what the users actually need similarly to how a physician knows the body (system) remedies by hearing (or even not hearing) the complaint. O is for ownership. Take ownership of the complaint and communicate remediation actions. Even if you can't yet mitigate the issue raise subject matter experts who can guide prioritized resolution. R is for Rationale. Understand why feedback is negative from a business or equivalent use-case perspective. E is for essentials: prioritize mitigation then root cause analysis. Prevent with alerts that point to standard operating procedures (SOPs) and establish KPIs.