The organisation sends another survey.
Customers are asked to rate the interaction, explain what could be improved and confirm whether they would recommend the business.
The responses are collected. A dashboard is updated. Selected comments appear in a management presentation.
Then the same problems continue.
Customers still encounter the confusing process they reported months earlier. Employees still rely on the workaround they have repeatedly escalated. Complaints about the same failure are resolved one at a time without changing the cause.
Eventually, customers stop giving detailed feedback. Some select a score and move on. Others ignore the survey completely.
The organisation continues asking, but customers no longer believe that answering will make any difference.
This is feedback theatre: the visible performance of listening without the operating discipline required to learn and act.
The danger is not merely that the organisation wastes money collecting unused information. Repeatedly asking customers for input and appearing to disregard it can create a second failure on top of the first.
The original problem disappoints the customer.
The failure to respond to what they said weakens trust.
Collecting feedback is not the same as listening
Most organisations can demonstrate that they collect customer feedback.
They send surveys, monitor reviews, record complaints, conduct interviews and track customer scores.
These activities produce data. They do not automatically produce insight or improvement.
Listening requires the organisation to do something more demanding:
- Understand what the customer is communicating.
- Determine whether the issue is isolated or systemic.
- Assess its severity and commercial significance.
- Identify the underlying cause.
- Decide what action is appropriate.
- Assign responsibility.
- Check whether the action worked.
- Respond to the customer where possible and useful.
Without these steps, the feedback process ends at collection.
The organisation hears the customer but does not learn.
Feedback does not always signal loyalty
It is tempting to interpret every customer who provides feedback as someone trying to preserve the relationship.
Sometimes that is true.
A customer who takes time to explain a problem may still believe the organisation can recover. Their feedback creates an opportunity to understand the failure and potentially retain their trust.
But feedback can reflect many motivations.
A customer may respond because they are angry, courteous, incentivised or accustomed to completing surveys. They may want to protect other customers rather than continue the relationship themselves. A quick rating may require very little engagement.
Feedback is therefore not proof of loyalty or future intent.
What it does provide is evidence the organisation would not otherwise possess.
Even when the customer has already decided to leave, their account may reveal a preventable failure affecting others.
The value of feedback lies not in assuming what the respondent intends, but in understanding what the information can help the organisation see and improve.
The customer pays a cost to give feedback
Providing useful feedback requires effort.
The customer must remember what happened, explain it clearly and spend additional time on an interaction that may already have inconvenienced them.
When organisations repeatedly request feedback without using it well, they transfer part of the improvement burden to customers.
The implicit exchange is straightforward:
Give us your time and information, and we will use it to improve.
If the same customer later encounters the same problem, that exchange begins to feel dishonest.
The problem becomes more severe when surveys are frequent, poorly timed or irrelevant. A customer may be asked to rate a routine interaction before the final outcome has occurred. They may receive several requests from different departments about the same journey. They may explain an issue in a survey and then be asked to repeat it when they seek help.
At that point, feedback collection creates additional customer effort rather than reducing it.
Before asking another question, the organisation should know why it needs the answer and what it is prepared to do with it.
The signs of feedback theatre
Feedback theatre can exist even when the organisation has sophisticated software and professional reports.
I look for several warning signs.
1. Success is measured by collection volume
Management tracks how many surveys were sent, how many responses were received and whether the headline score improved.
Far less attention is given to:
- How many significant issues received an owner.
- How long customers waited for acknowledgment.
- How many recurring causes were corrected.
- Whether the same problem appeared again.
- Whether an intervention improved the customer outcome.
- What proportion of feedback remains unresolved.
- Which customer groups are absent from the data.
The feedback programme becomes successful when it produces more feedback—not when it produces better decisions.
2. Feedback is summarised before it is understood
Customer comments are placed into broad categories such as “service,” “communication,” “price” or “delay.”
These summaries may be useful for reporting, but they can remove the detail necessary for action.
“Poor communication” could mean:
- The customer received no update.
- Different employees gave contradictory information.
- Technical language made the decision difficult.
- A promised call never occurred.
- The message arrived through the wrong channel.
- The customer did not understand what happened next.
Each cause requires a different response.
Categorising feedback is not the same as diagnosing it.
3. Responsibility ends with the customer-experience team
The customer-experience or research team collects the feedback and presents it to the business. Operational teams listen, acknowledge the findings and return to their existing priorities.
No one has the authority, resources or incentive to change the process.
This creates a structural problem. The team responsible for hearing the customer may not control the systems producing the failure, while the teams that control those systems are not accountable for acting on the feedback.
The result is a well-documented problem without an operational owner.
4. Individual cases are closed while the cause remains
An employee apologises, processes a refund or resolves the immediate complaint.
The customer’s case is closed.
But nothing changes for the next customer.
Service recovery and systemic improvement are different responsibilities. Both matter.
The individual customer may need an immediate resolution. The organisation must also determine whether the failure is likely to recur, where else it may be happening and what would prevent it.
If cases are repeatedly closed without learning from them, the complaints process manages consequences while preserving causes.
5. Customers are asked questions the organisation is unwilling to confront
Some organisations ask broad questions about what should improve but have no appetite to challenge the policies, targets or leadership decisions responsible for the answer.
Feedback is welcomed as long as it points towards safe adjustments: employee courtesy, communication wording or minor process changes.
When customers identify a more difficult issue—pricing transparency, product suitability, chronic understaffing, unfair terms or conflicting incentives—the finding is explained away.
The organisation wants customer input, but only within the boundaries of decisions it has already made.
6. Positive feedback is celebrated while difficult evidence is disputed
Compliments are treated as authentic. Negative comments are dismissed as unusual, emotional or uninformed.
Some negative feedback will indeed be based on misunderstanding or unrealistic expectations. That does not make it useless.
Even when the organisation cannot agree with the customer’s conclusion, it can still learn how expectations were created, why the process was confusing or where communication failed.
A serious feedback system does not treat every customer comment as fact. It treats every material comment as evidence to be evaluated consistently.
Not every suggestion should be implemented
Listening does not require an organisation to do everything customers request.
Some suggestions conflict with regulation, safety, fairness, affordability or the organisation’s strategy. Different customers may request opposite things. A change that benefits one group may create difficulty for another.
Customers usually see the experience from their own perspective. Management must consider the wider system.
The obligation is not automatic compliance.
It is disciplined consideration.
The organisation should be able to explain:
- What it heard.
- How the issue was evaluated.
- What decision was made.
- Why action was or was not appropriate.
- What alternative support may be available.
- Whether the matter will continue to be monitored.
Closing the loop can include making a change. It can also include acknowledging the concern, explaining a constraint or clarifying an earlier misunderstanding.
Silence is what makes the process feel performative.
Frequency is important—but severity can matter more
Recurring feedback often points towards a structural issue.
If many customers report the same delay, confusing instruction or inconsistent response, the pattern deserves attention.
But frequency should not be the only criterion.
A single report involving safety, discrimination, data misuse, regulatory exposure, serious financial harm or ethical misconduct may require immediate investigation.
Other issues may affect only a small customer group because that group is underrepresented, vulnerable or using a less common journey.
A practical prioritisation approach should consider:
- Frequency.
- Severity.
- Customer harm.
- Financial exposure.
- Legal or regulatory risk.
- Strategic importance.
- Number and type of customers affected.
- Likelihood of recurrence.
- Effort and feasibility of correction.
Patterns matter, but rare and consequential events must not disappear inside the averages.
From collection to a working feedback system
A credible feedback system needs a defined path from customer input to organisational learning.
I would structure that path around three connected levels.
1. Respond to the individual customer
Where the customer can be identified and expects a response:
- Acknowledge the feedback.
- Clarify the issue where necessary.
- Resolve the immediate need where possible.
- Explain what will happen next.
- Confirm when the customer should expect an update.
This protects the individual relationship.
An automated “thank you” may acknowledge receipt, but it does not close the loop on a substantive concern.
2. Identify and correct recurring operational causes
Related comments, complaints and service failures should be examined together.
The organisation should determine:
- Where the issue occurs.
- Which customers are affected.
- What process, policy, system or behaviour produces it.
- Whether a temporary workaround exists.
- Who has authority to correct the cause.
- How improvement will be measured.
This prevents the organisation from resolving the same symptom repeatedly.
3. Use customer evidence in management decisions
Some feedback reveals broader questions about product design, resource allocation, policy, channel strategy or the promises the organisation makes.
These issues require leadership attention.
The role of feedback at this level is not to dictate strategy. It is to ensure that customer evidence is considered alongside financial, operational, regulatory and competitive information.
This connects listening to organisational decision-making rather than leaving it inside the customer-service function.
Ownership must be specific
“Operations will look into it” is not ownership.
For a material feedback issue, the organisation should identify:
- One accountable owner.
- The scope of the problem.
- The evidence available.
- The action or investigation required.
- The deadline.
- The expected customer and business effect.
- The method of evaluating the outcome.
- The person responsible for communicating progress.
Ownership should follow the cause, not merely the channel through which the feedback arrived.
A complaint about delayed delivery may be received by customer service, but the accountable owner may sit in operations, procurement, technology or another function.
The team that hears the customer should not automatically become responsible for fixing every system the customer describes.
Close the loop truthfully
Customers do not need a public announcement for every internal adjustment.
But where feedback has led to a meaningful change, communicating that change can demonstrate responsiveness and reinforce participation.
The communication should be accurate.
An organisation should not claim, “You asked, and we listened,” if the change had already been planned or if customer feedback played no meaningful role. Closing the loop should not become another form of theatre.
Appropriate communication might include:
- Updating the customer who raised the issue.
- Informing affected customers of a process change.
- Explaining why a requested change cannot be made.
- Publishing a summary of recurring themes and actions.
- Showing employees how customer evidence influenced a decision.
- Confirming that a pilot is being tested rather than promising a final solution.
Visible improvement builds trust when it is genuine, relevant and proportionate.
Measure whether feedback produces action
A feedback dashboard should report more than customer scores and response volumes.
Useful measures may include:
- Percentage of material issues assigned to an owner.
- Time taken to acknowledge feedback requiring a response.
- Time taken to resolve the individual customer’s need.
- Number of recurring issues linked to verified root causes.
- Percentage of agreed actions completed.
- Recurrence rate after corrective action.
- Number of customers updated on significant outcomes.
- Customer behaviour following recovery.
- Volume of feedback with no clear disposition.
- Repeat feedback concerning previously identified problems.
- Changes in operational and commercial outcomes after intervention.
These measures help answer the question most feedback programmes avoid:
What changed because we listened?
Sometimes the right answer is to ask less
More feedback is not always better.
If the organisation already knows that customers are frustrated by a particular process, another survey may add little value. The priority should be correction.
If customers are repeatedly asked for information that has not been analysed, collection should be reduced until the organisation can use what it already has.
If several departments contact the same customer, the feedback process should be coordinated.
If a survey is sent before the outcome occurs, its timing should be reconsidered.
A disciplined organisation does not measure its commitment to customers by the number of questions it asks.
It asks only when the answer can improve understanding or action.
Feedback should make the organisation more accountable
In my work on Customer Leakage Intelligence, I am interested not only in what customers say, but in what happens to that information after it enters the organisation.
Where is it recorded?
Who sees it?
How is it evaluated?
What decision follows?
Does the customer receive a response?
Does the underlying failure recur?
These questions reveal whether feedback is functioning as an improvement system or merely as a reporting activity.
Customers will not agree with every decision an organisation makes. They do not expect every suggestion to be implemented.
But when a business repeatedly invites customers to speak, it creates an expectation that their time and perspective will be treated seriously.
When the same preventable problem persists, the request for more feedback can begin to feel less like listening and more like performance.
The question leadership should ask is not:
How much customer feedback did we collect?
It is:
What did we understand, decide and improve because customers took the time to tell us?
If the organisation cannot answer that question, it may not have a feedback system.
It may only have an audience participating in feedback theatre.