Product Strategy9 min read
From user feedback to product strategy: knowing which problems to solve
Most product teams are not short of feedback. They are drowning in it. The skill is turning a flood of requests, complaints and ideas into a short list of problems worth solving.
By Strategy Practice, Brand, strategy & AI
Feedback arrives from everywhere: support tickets, sales calls, app reviews, customer success notes, surveys, social media, the CEO's friend. Each piece is real. Together they form a pile that no team can act on in full, and that is easy to misread.
The common failure is to treat the pile as a vote. The most requested feature gets built. But volume tells you who is most vocal and which customers have the shortest path to your team. It does not tell you what matters most to the business.
Group by problem, not by request
Ten customers asking for ten different features may all be describing one problem. One customer asking loudly for one feature may be describing a problem nobody else has. The first step of synthesis is translating requests into the problems underneath them.
- Collect feedback from every source into one place, with the customer and context attached.
- For each item, write the problem it implies in one sentence.
- Group items by problem, not by the solution requested.
- Note who has each problem: segment, size, value, stage.
Prioritise on impact and fit
| Question | Why it matters |
|---|---|
| How many customers have this problem? | Reach |
| How valuable are they? | Revenue at stake |
| What does the problem cost them? | Severity and willingness to switch |
| Does solving it fit our strategy? | Not every good idea is our idea |
| What does it cost us to solve? | Effort and opportunity cost |
Strategic fit is the question most often skipped. A problem can be real, widespread and valuable to solve, and still be the wrong thing for this company to solve right now. Saying so is part of having a strategy.
Close the loop
Customers who give feedback and hear nothing stop giving it. Tell people what you heard, what you decided, and why, including when the answer is no. A clear no with a reason builds more trust than a vague 'it's on the roadmap' that never arrives.
Feedback tells you where it hurts. Strategy decides which pain you are in business to fix.
Strategy Practice
Brand, strategy & AI
The strategy practice covers positioning, product strategy, UX diagnosis and AI opportunity work. It writes about the commercial reasoning behind design decisions, and the organisational conditions that make good products possible.
