How would you approach redesigning a core feature after negative user feedback?

Model answerNegative feedback is data, not a mandate. My first step is to understand what users are actually complaining about versus what they're asking for — these are different things. If users say 'this is too complicated,' I'd watch session recordings before redesigning anything. Then I'd form a hypothesis, prototype the simplest possible fix, and test it with 10 users. I'd measure whether the redesign improves task completion rate and NPS, not just whether users say they like it.