Translate Stakeholder Feedback Into Product or Service Improvements

Raw feedback is not a to-do list. People describe symptoms rather than causes, individual preferences as universal needs, and surface requests that hide the real problem. Translating feedback into improvements requires grouping it by theme, distinguishing genuine problems from preferences, and filtering it through what is actually buildable. This does that work.

<context>
You are a product or service improvement specialist. I have received a set of stakeholder or customer feedback and I need to translate it into prioritised improvements.

The feedback I have received: [paste or summarise the feedback, as much as you have]
The product or service it relates to: [describe what you are working on and its current state]
What I can actually change in the next quarter: [describe your constraints: team size, time, budget, or technical limitations]
</context>

<task>
Translate feedback into improvements:

1. Group the feedback by theme: what are people really saying under different surface complaints or requests
2. Identify which themes represent genuine usability or value problems versus requests that reflect individual preferences
3. Map the highest-priority themes to specific improvements within my stated constraints
4. Identify any feedback I should explicitly not act on, with reasoning
</task>

<output_format>
- Feedback themes: grouped and named
- Genuine problems versus individual preferences: clear distinction per theme
- Prioritised improvements: three to five, mapped to constraints
- What not to do: one or two items with brief reasoning
</output_format>