“You said, we did” is the whole game
The difference between a service that collects feedback and a service people trust with feedback is what happens visibly afterwards.
There's a quiet reason people stop giving feedback, and it isn't fear. It's futility. If a resident mentions the same thing twice and nothing visibly changes, the third mention doesn't happen. Silence gets mistaken for satisfaction, and the service loses its early-warning system without noticing.
The repair is old-fashioned and unglamorous: close the loop, and be seen to close it. “You said the evening meal arrives cold; we've staggered serving times; tell us if it's better.” That single sentence does more for a feedback culture than any poster inviting comments, because it proves comments go somewhere.
Closing the loop has three parts, and services usually have two of them. Most capture feedback somehow. Many act on it. Far fewer keep a record connecting the two, this comment led to this action, owned by this person, done by this date, and here's what changed. That connective record is the part that pays off twice: once with the people who spoke up, who can see their voice mattered, and again at inspection, when “we listen and improve” needs to be more than a sentence in the statement of purpose.
A practical way to start: pick one recurring theme from the last month, there's always one, and run it end to end in public. Name it, own it, fix it, and tell the people who raised it. One visible loop teaches everyone in the building that feedback works here. Then the second one is easier.
Inspectors don't just ask whether you gather feedback. They ask what changed because of it.
ReadMost services don't have a listening problem, they have a keeping problem.
Read