Closing the feedback loop means telling the people who gave you feedback what happened to it: that you read it, what you decided, and above all that it shipped. Most teams do the first half, collecting, and drop the second, so their customers learn that asking leads nowhere. Closing the loop isn't a newsletter to everyone. It's a message to the people who asked, sent when their request changes, without anyone on your team having to remember to send it.
Why it matters#
- Asking keeps working. People who hear back ask again, and they write better requests the second time.
- The people who asked are your first users. A feature announced to the people who wanted it gets used. Announced to everyone, it's one more email most of them skip.
- It shows everyone else. A board where requests visibly move to Completed tells a new visitor that writing one is worth their time. A board where nothing moves tells them the opposite.
The four moments to tell people#
A request has four moments worth a message, each one short, and each one to the people who asked for that request rather than to all your customers:
| Moment | Status | What they learn |
|---|---|---|
| You've read it | Under review | Someone looked, and it's being considered |
| You've decided | Planned, or Closed with reason | Whether to wait for it, and why if not |
| You've started | In progress | It's coming, and roughly how far along it is |
| It shipped | Completed, then an announcement | That it's there, and how to use it |
The no counts as much as the yes: a request closed with a reason closes the loop too. How to say no to a feature request has replies to copy.
The last moment matters most, and it's the one most often missed. The engineer merges the work, the issue closes, the release goes out, and the customer who asked for it four months ago finds out by chance, if at all.
Where the loop breaks#
The loop rarely breaks because nobody cares. It breaks at one of four joints:
- Nobody knows who asked. The request came through support, a sales call or a Slack thread, and was copied into a list without the person who said it. When it ships, there's no one to tell.
- The status lives in another tool. The work happens in GitHub or Linear. The board says Planned for weeks after the code shipped, because updating it was a separate step that someone had to remember.
- The announcement goes to everyone, or to nobody. A changelog page that nobody opens, or a newsletter that buries the one line someone was waiting for under ten they weren't.
- Duplicates split the people. Five copies of the same request, with their voters spread across them. You ship from one, and the other four groups hear nothing. Duplicate feature requests covers catching and merging them.
Each fix is a link that holds by itself: a person attached to every request, a status that follows the work, and an announcement that knows whom to tell.
Closing it without sending anything by hand#
In Swingback, each of those links is part of how a request works.
Who asked is who follows. Writing, voting for or commenting on a post follows it. Every request keeps the person who made it, whatever the channel: your app's users are signed in to the widget by a token your server signs, a message saved from Slack Beta keeps whoever wrote it as the author, and your servers can name a customer as the author of a post or a vote through the REST API, on the Pro plan.
Every status change tells them. When a post changes status, the people who follow it hear, in the portal and by email. A burst of news on one post makes one email, not five. If the post links issues on GitHub or in Linear, through the sync Beta, the issues move it: it becomes Completed once the last one is done, and nobody has to update the board. See Statuses, both ways.
The changelog tells them again, with the story. A changelog entry links the posts it delivers. The first time it's published, the customers who wrote, voted for or commented on those posts hear about it, along with everyone subscribed to the changelog. For a small fix that needs no email, Publish quietly puts the entry on the portal and tells nobody. See who hears about it.
In their own language. Each email is written in its reader's language, one of seven: the one they read your portal in, or, when it isn't known, your workspace's default.
Once a week, in one place. The weekly digest lists, among the week's news, the posts completed and the changelog entries published, for the customers who keep it on. See Notifications.
A checklist#
Whatever tool you use, the loop is closed when all of these are true:
- Every request has a person attached, or several, whatever channel it came through.
- Every status change reaches them without anyone writing an email.
- Shipping moves the request the day it ships, ideally because the issue closed.
- The announcement links the requests it delivers, and goes to their people first.
- A no gets said, with its reason, to everyone who asked.
- Duplicates are merged before you ship, so that everyone who asked hears, not only the people on the copy you worked from.
If your engineers live in GitHub or Linear, GitHub issues for feature requests and collecting feature requests for a Linear team show how the board and the issues stay in step, so the last moment closes by itself.
