Someone with access to customer feedback forwards real complaints about a rival department up the chain, so leadership sees that department through its customers' worst moments and has to act.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
Every complaint about housekeeping that reached the guest relations director at a hotel group's flagship property went to the regional vice president for two months, eleven in all, each with the guest's own words and the room number. She was convinced the department needed a new staffing model, and she had said so at the spring planning session without effect. When the vice president asked whether the complaints were typical, she sent the property's cleanliness scores the same day: up on the year and the best in the group, with turndown complaints concentrated on two floors staffed by agency workers. The vice president asked the director of housekeeping for a plan for those two floors. The agency contract was cut in half that quarter.
Why it works
Real complaints make the rival department look worse, because the executive pictures the guest in the email and not the thousands who were satisfied. They also make defending the department costly: its backers must seem to dismiss customers, explain the complaints away, or give ground, and whoever keeps backing it owns the next complaint. Forwarding real feedback is cheap and looks responsible. The move works best when the forwarder sees the complaint channel first, leadership lacks aggregate data of its own, and the culture treats the customer as the final judge.
The thinking behind it
Daniel Kahneman Availability, from Judgment under Uncertainty: Heuristics and Biases (1974), written with Amos Tversky: people judge how frequent or probable something is by how easily instances come to mind. A forwarded complaint, in the guest's own words, comes to mind instantly, while a satisfaction rate does not. That is why a handful of emails can outweigh thousands of quiet stays, and why the defense is to put the rate beside every story.
When it fits
Someone who sees customer feedback early, and is convinced a department's problems are real and costing the business, is the reader it fits. You need real complaints, a line to the executive who can act, and the aggregate numbers ready for when you are asked about them. It works on service problems customers can see, and poorly on internal ones they can't.
How to use it well
Forward complaints that show a pattern, with the customer's words intact, and say what you think the pattern means.
- Keep each one factual: date, location, what happened, what the customer said.
- Have the aggregate numbers ready, and send them the first time you are asked.
- Name the fix you want: a staffing change, a process, a leader.
- Copy the department's own leader where you can, so the complaints don't arrive behind their back.
Persistence matters. A steady record moves an executive that one email will not.
What it costs and where it backfires
Department leaders you press will treat you as an opponent, and their allies will go looking for complaints about your own team. If leadership learns to react to every anecdote, it stops weighing evidence, and you may be on the receiving end later. What keeps this fair is the denominator. Holding back aggregate numbers you have, trimming complaints to sound worse, or forwarding one unit's complaints while burying others' turns framing into deception, and your own emails become the evidence.
When it is used on you
Answer each complaint about your unit with the denominator: how many complaints, out of how many interactions, against last year and against peer units. Fix the real ones quickly and visibly. Ask, in a neutral tone, who controls the channel and whether other units' complaints travel upward the same way.