Customer feedback can show what people found difficult, useful or unexpected. It becomes less actionable when the request asks only whether they liked the business. Start with a decision the team can influence, then ask about the experience that should inform it. Make responding optional and proportionate to the interaction.
Business.gov.au identifies feedback as one way to understand and improve customer relationships. The approach below is a practical feedback cycle for a small service business. It does not turn voluntary responses into a representative survey or replace appropriate research for a consequential decision.
Choose a question connected to an action
Suppose a workshop organiser wants to improve joining instructions. The question is whether participants could find the location and prepare for the session. Ask about those tasks directly. A broad “How satisfied were you?” score may be useful context, but it does not tell the organiser which instruction needs changing.
Use wording that allows a negative answer without embarrassment: “Was there anything in the joining instructions that was unclear?” Follow with “What would have helped?” Avoid implying that the experience was excellent before the person responds. Do not bundle several topics into a single rating.
Keep the request short and timely
Send the request when the relevant experience is still reasonably fresh, through a channel customers expect. Explain its purpose and avoid requiring unnecessary personal details. If the request includes contact information for a follow-up, make it clear how that information will be used under your existing privacy procedures.
For the workshop example, three questions could ask whether the location was easy to find, whether preparation instructions were clear and which detail was missing. That is enough for the immediate decision. A long questionnaire about the entire business may reduce completion and produce data nobody has time to examine.
Read comments before counting themes
Group comments by the problem they describe, while preserving contradictory experiences. “Parking instructions were unclear” and “I could not find the entrance” may be related but are not identical. Keep a sample of the wording in the protected research notes so the team can check that its summary remains faithful.
Distinguish a suggested solution from the underlying need. One participant may ask for a map, while another wants a photograph of the entrance. Both may need confidence that they have reached the right building. The team can test which information helps rather than simply adding every requested feature.
Examine who responded
If twelve people respond from a workshop of forty, report those counts. Do not describe the findings as what “all customers” think. People with particularly positive or negative experiences may be more likely to respond. Some participants may not see the request or may find the channel difficult to use.
Compare the feedback with other evidence: questions asked before the event, late arrivals and observations from the venue team. These sources can help interpret the responses, but they also have limitations. A late arrival does not automatically mean the instructions caused the delay.
- Link the request to a decision the team can make.
- Ask about specific tasks and allow critical responses.
- Keep participation optional and the request brief.
- Separate customer needs from proposed solutions.
- Report response counts and recruitment limitations.
- Compare comments with other relevant evidence.
Close the learning cycle
Choose a manageable change, such as adding an entrance photograph and clearer public-transport directions. Test it with the next event's instructions. Observe whether related questions decrease and ask a focused follow-up. Avoid claiming the change worked based only on a higher overall satisfaction score.
When appropriate, tell customers what the team learned and changed without publishing identifiable comments. Feedback builds practical value when people can see that their experience informs the service. Keep the cycle small enough to sustain: one decision, a useful request, careful interpretation and a change that can be checked.
Sources and further reading
This original guide was prepared with AI assistance. Examples are illustrative. The edition date is an assigned date in this 2026 catalogue. See our editorial policy and report a correction.