User Feedback and Requests
Level 3 Β· Finding the right problem
How to sort what users tell you and what they ask for into patterns. Why saying yes to every request leads to feature creep.
Course contentsLesson 8 of 13
Level 1 Β· The job
Level 2 Β· Where the product is going
Level 3 Β· Finding the right problem
Level 4 Β· Choosing what goes first
Level 5 Β· Shipping and measuring
After this lesson you can
- Sort feedback into themes and count them
- Find the problem behind a request
- Spot the signs of feature creep
11 mincovers 3 glossary entries
Worth reading first: Opportunity Solution Trees
What to do with what users ask for
User feedback is what users tell a team about a product, in their own words. It comes from support chats, reviews, surveys, sales calls and user talks. A product with 10,000 users can easily produce a few hundred comments a month. Read one at a time, they are noise. Sorted and counted, they show patterns.
The basic method is to tag and count. Give each comment one or two short tags, like export or slow search. At the end of the month, count each tag. Ninety comments about the export button tell you more than one angry email from a big client, however loud it was.
Feedback says what people feel. Product analytics shows what people do. The two often disagree. Users may say they want more settings while the numbers show almost nobody opens the settings page. A good team reads both and trusts the pattern where they agree.
A feature request is a user asking for something the product does not do yet. Most requests describe a fix, not a problem. Twenty people ask for a download to spreadsheet button. Ask each one why, and you may find they all want to send monthly totals to a boss. A shareable report might serve them better.
Log each request with who asked and why. Then treat requests as clues for discovery, not as orders. Users know their problem very well. They are often less right about the fix, because they only see their own corner of the product.
Saying yes to every request leads to feature creep. Each new feature seemed fine on its own. Together they make the product slower, harder to learn and harder to fix. A simple to-do app that adds chat, a calendar and notes can bury the button for adding a task.
The cure is a clear strategy and the nerve to take things out. Remove a feature that almost nobody uses, and the product gets better for the rest. Before you add something, ask what it will cost each user who never needed it.
Worked example
Lucy counts a month of chats
Lucy's team tags 400 support chats from one month. Ninety are about the export button being hard to find. Twelve ask for a new chart type.
Moving the button to the top bar takes one day. Next month, export chats fall from 90 to 15. The chart idea goes into the log for later.
The words for this lesson3
Check yourself
Twenty users ask for the same button. What should a product manager do first?
Finished this lesson?
Marking it complete also marks its 3 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.