Closing the feedback loop is the process of collecting customer feedback, acting on it, and then telling the customer what you did. Most teams nail the first two steps and drop the third entirely.
That third step is what makes it a loop. Without it, customers have no idea if their input mattered. They start to feel like they're shouting into a void, and they stop giving you feedback, which means you lose the signal you actually needed.
Why teams skip it
It's usually a process problem, not laziness. Feedback comes in through multiple channels, gets triaged, lands in a backlog, and ships six months later as part of a larger release. By then, nobody has gone back to find the original request, tag it, and notify the customer who submitted it.
What good looks like
The best teams build loop-closing into their release workflow, not as an afterthought. They track which feedback items influenced a decision, and when that feature ships, they notify the customers who asked for it.
It doesn't need to be a long message. "Hey, you asked about X six months ago, we just shipped it" is enough to make someone feel heard.
Publish your release updates with FeatureOS Release Notes and let customers follow along on your Feedback Board. When you connect the two, the loop closes itself.