Keep the voice and the interpretation separate
A customer says, "I had to ask three times for an update." That is a reported experience. "We need a new app" is an interpretation. "We should sell a premium reporting package" is a proposed commercial response. Do not merge the three into one fact.
Record the context, the customer's words or a faithful summary, the stage of the journey and the evidence available. Preserve uncertainty where the account has not been checked. The aim is to understand and improve, not to build a case against an employee.
Distinguish issue, preference and unmet need
An issue concerns something that failed or created avoidable effort. A preference concerns how someone would like the service delivered. An unmet need may indicate a problem the current offer does not address. A request can contain more than one of these.
Government market-research guidance includes customer feedback as a source for improving products and services. It does not mean every suggestion should become a feature. Consider frequency, consequence, fit and delivery cost.
Worked example (illustrative): the reporting request
Several customers ask for a weekly status report. The business considers building a portal. A closer review shows that customers mainly want to know whether a milestone will be missed. They do not need a dashboard with every task.
The team tests a clear milestone update from a named owner, with an exception message when timing changes. It measures avoidable chasing and whether customers can make their next decision. The test may reveal that a portal is useful later, but it first establishes the information need.
The lesson is not that software is unnecessary. It is that the problem should define the tool rather than the tool defining the problem.
Unlock the rest of this lesson
You're halfway through. Enter your email to read the full lesson, use the exercises and quizzes, and unlock the rest of The Business of Growth library.
Already signed up through The Business of Growth? Use the existing signup to return and unlock this browser. No payment required.
Prioritise with two views
Look at frequency and consequence separately. A common minor inconvenience and a rare serious failure deserve different handling. A Pareto-style review can show concentration, but should not hide severity.
Also examine controllability. Some requests concern a service you should not provide. A clear boundary or referral may be better than an expensive new capability that distracts from the core offer.
Close the loop
Tell the customer what you understood, what will be investigated and what you can reasonably commit to. Where appropriate, explain the change and ask whether it addresses the original problem. Do not promise implementation before assessing feasibility.
Internally, name the owner and the acceptance condition. "Improve communication" is vague. "Send a checked milestone update before the agreed review point" is observable. Review whether the change occurs, not only whether a policy was written.
Test an adjacent offer responsibly
When feedback reveals a genuinely new need, check whether the customer would use and pay for a suitable solution. Compare fit, cost, capacity and alternatives. Use a small pilot with clear scope rather than adding the idea permanently because one important account requested it.
Feedback should improve the business's understanding of value. It should not turn the roadmap into a queue of every suggestion ever received.
Your next action
Collect ten feedback items from a defined period. Separate the reported experience, interpretation and proposed action. Group recurring themes, note severity and select one test. Write how you will close the loop and what evidence would justify a broader change.
Your notes stay on this page unless you choose device saving, download them or submit them to Greg below.
Keep names, private customer details and confidential information out of your notes. Device saving is optional. Only the separate Send my lesson work button below sends anything to Greg. There is no account or cross-device sync.
Two questions before you move on
These checks support learning. They do not assess business health, award a qualification or send a result to Greg.
Ask Greg
Ask a question about this lesson or a challenge in your own business. I read submissions and may reply or cover common questions in future lessons. I cannot promise an individual reply to every question.
Lesson: Turn customer feedback into better service and relevant next offers. Please do not include confidential client, financial, health or staff information.
Work out where your business is getting stuck
The free Growth Diagnostic asks ten questions across acquisition, conversion, relationships, delivery and commercial control. It gives you an area to investigate and three things you can do next.
One complete sample lesson in each stream is fully open. Read halfway into every other lesson, then enter your email to unlock the remaining content, exercises and quizzes across the library. Ongoing marketing emails are optional.