Skip to content

Customer Feedback: Investigate the Problem Behind a Feature Request

Summary

Learn to investigate customer feedback through real examples, compare usage conditions, and test improvements without equating requests with requirements.

Published

Explore the Situation Behind Customer Feedback

When a customer requests a feature, investigate the situation that prompted it. Record the proposed solution separately from the underlying problem.

Volume and intensity alone can overrepresent particular customers. Compare requests with their usage conditions and frequency.

Ask about a Real Experience

For more notifications, ask what was missed, when, and what happened next. A real example gives context that a future preference alone cannot supply.

GOV.UK interview guidance recommends non-leading questions and exploration of actual experiences. (GOV.UK: In-depth interviews)

Compare the Conditions Behind Requests

Record the goal, workflow, frequency, and workaround. If some users need more notifications while others receive too many, examine settings and usage conditions.

Identical wording can conceal different causes. Check problem similarity before counting requests together.

Test the Improvement against Actual Use

Compare options such as additional alerts, a different display, or clearer setup instructions. After testing, examine missed information and unwanted alerts together.

Publish the changed feature and conditions. Do not publish customer statements or personal information without appropriate permission.

SpreadSite is a no-code website builder that lets you create, publish, and update a website from Google Sheets using ready-made templates.

To publish a website explaining improvements informed by customer feedback, give SpreadSite a try!

Build a website with SpreadSite →

Frequently asked questions

Q: Should I investigate a single request?

A: Yes when its impact warrants it. Examine severity and the conditions that reproduce the problem.

Q: Can a survey alone choose an improvement?

A: Supplement it with interviews or observation when the context is unclear.

Q: What should I record when declining a feature?

A: Keep the problem, options considered, rationale, and conditions for reconsideration.

Q: How should improvement be assessed?

A: Compare similar usage conditions before and after, checking the problem and possible new burdens.

Sources

Build a website with Google Sheets using SpreadSite