Overview
Collecting feedback without responding to it is worse than not asking. This guide covers what to share with your team, how to frame it, and what to do when the results are uncomfortable.
Why closing the loop matters
Response rates are not a participation metric. They're a trust metric.
When people stop answering the weekly check-in, it's usually not because they're too busy. It's because they answered before and nothing happened. They said something was wrong. The following week was identical. The week after that, they stopped saying anything.
Closing the loop breaks that pattern. It signals that the channel works: that what's sent through it reaches someone who reads it, takes it seriously, and does something about it. That signal is more important than any single piece of feedback you'll receive. Without it, Relay becomes another form people fill in because they were asked to.
What to share
You don't need to share the scores. You need to share that you read them.
The most effective close-the-loop moments are specific and concrete: 'A few people mentioned the brief turnaround time on the last project felt stressful. I'm going to build more buffer into the planning for the next one.' That's it. No percentages, no references to Relay, no 'the team collectively expressed.' Just a thing you heard and what you're going to do about it.
Sharing scores directly can work in high-trust environments where the team already understands what Relay is and why they're using it. In those contexts, bringing the trend into a retrospective or planning conversation can sharpen the discussion. But sharing scores as a default creates pressure. People start to feel responsible for the number rather than honest about their experience.
What not to share: speculation about who said what, anything that could narrow the group down to one or two people, or direct quotes from comments when the team is small. Anonymity is an architectural commitment, but it requires your active protection too. A team that trusts the anonymity will give you honest signal. A team that suspects otherwise goes quiet.
How to share it
The format matters less than the consistency. A sentence in the weekly team standup is fine. A short note in your team channel is fine. What doesn't work is a quarterly 'results review meeting' where you walk through a presentation of scores. That turns feedback into a performance. The rhythm should be low-key and regular.
The best framing is first person and direct: 'I've been reading the check-ins. One thing I want to address is...' Not 'the data shows' or 'the results indicate.' You read something. You're responding to it. That's the relationship Relay is built to support.
Timing matters. Close the loop within a week of receiving results, ideally in the same week. A response three weeks later, after two silent weeks, is harder for the team to connect to what they said. You're not looking for a comprehensive response to every theme. You're looking for one concrete acknowledgement, consistently.
What to do when the results are hard
Sometimes the results will show something you didn't expect, or something you did expect and had hoped wasn't true. A sustained drop after a restructure. Low scores that have sat in the same place for months. Results that point to your leadership directly.
The instinct is to explain. To give context before acknowledging the signal. Don't. Start with the acknowledgement. 'The scores have been lower than I'd like for the last month. I hear that. I don't have a complete answer yet, but I'm taking it seriously and I want to understand what's driving it.' That's enough for now.
A team that can tell you things are hard is a team that still trusts the channel. That's valuable. The risk isn't a low score. The risk is a low score you don't respond to, and then a team that stops telling you anything at all.
Closing the loop is not a feature. It's the practice that makes everything else work. Set aside ten minutes on the first Monday of each month to think about what you've heard and what you haven't yet responded to. That's the whole process.