Closed-Loop Feedback: What It Is and How to Close the Loop
Shayan, Founder12 min read

Closed-loop feedback means everyone who gives you customer feedback hears back about what was decided or done with it. The loop closes when the person who spoke up knows the outcome, whether you shipped what they asked for, put it on the roadmap, or passed on the idea.
The phrase comes from control engineering and reached customer feedback through Bain & Company, which splits the work into an inner loop for individual follow-up and an outer loop for fixing the underlying product, process, or policy. In software, hearing back after sending feedback is rare enough that customers are surprised when it happens. On Hacker News in September 2011, briandear wrote about replying personally to emails from users of a psychology app, usually within an hour, and getting what briandear called "a baffled response expressing appreciation":
Wow! Thanks so much for getting back to me about [my suggestions.] I never expected a response at all, let alone such a nice email. I appreciate it that you'll be incorporating [some my feature requests] into [the app] so quickly.
Getting that kind of reaction takes a clear, repeatable way to handle bug reports and feature requests from intake to reply.
What is closed-loop feedback?
In control engineering, a closed-loop system measures its own output and adjusts until it reaches its target, while an open-loop system acts without checking the result. Cruise control on a car is an everyday example. It checks your current speed and adjusts until the car matches the speed you set. Engineers use the phrase for control systems, while this guide covers customer feedback.
The customer-feedback version was described in "Closing the Customer Feedback Loop" by Rob Markey, Fred Reichheld, and Andreas Dullweber in Harvard Business Review in December 2009. All three were consultants at Bain & Company, and Reichheld created the Net Promoter Score, which asks customers how likely they are to recommend a company. Their summary argues that feedback does the most good when it goes straight back to the people who just helped the customer, with the authority to act on what comes up.
The article opens with a branch manager at Charles Schwab reading client responses every morning:
Cheryl Pasquale, a branch manager at Charles Schwab, starts her workday with this morning ritual: As soon as she arrives at her desk, she fires up her laptop, logs on to Schwab's intranet, and pulls up the latest customer feedback report for her office. Generated by a brief survey the investment firm e-mails out daily, the report shows the most recent responses from her team's clients.
On Bain's own page for its Schwab video, the firm notes that Schwab employees "close the loop through follow-up calls". The HBR summary also points to the household fixture maker Grohe, which tracked how the number of sales calls affected its Net Promoter Score in one market:
Grohe saw that scores spiked at three visits and then fell off. In response, it cut back on unproductive customer contact and freed up 25% more sales capacity.
Closed loop vs. open loop
An open loop collects feedback and never tells the person who submitted it what happened. You might read every submission, discuss it in planning, and even ship half of it, but from the customer's chair nothing ever came back.
You can see both sides of this on Remember The Milk's forums. In 2017, after a customer asked for checklists inside tasks in the Help forum and bumped the thread for an answer, staff member andrewski stated the team's policy:
We don't necessarily respond to feature requests, though we read all feedback! :)
In the next reply, andrewski pointed the customer to the Ideas Forum as the place to submit requests:
If you wanted to post this in the Ideas Forum, that's probably the best place to post any requests. Others would be able to vote on your ideas, and we can update them with any announcements or changes (e.g. when a new feature launches or if we answer a request more resolutely).
Saying plainly that you read everything and may not reply is an honest policy. Five years later, in July 2022, a customer named kenneho posted in that Ideas Forum asking the team to respond to requests and update their statuses:
When 15 year old feature request still has gotten no replies from the RTM team, it doesn't seem like the RTM team actually appreciate the input from its customers.
Loops also stay open when feedback has no real home at all. In April 2026, a user named Moeed, who had been active in the Shopify community for over five years, pointed out that the forum had more than 25 boards and none for feature requests:
People end up dropping their feature requests in Shopify Discussion where they sit alongside general questions and random threads. Most of them just disappear. Nobody sees them. Nobody tracks them.
Later in the same post, he wrote: "Even if a request doesn't get implemented right away, just knowing it's being seen in a proper place would make a huge difference."
The inner loop and the outer loop
Bain's Net Promoter System breaks closed-loop feedback into two loops linked by a short recurring meeting.
First is the inner loop, which handles the relationship with the person who gave feedback:
The inner loop offers a reliable way to enhance relationships with customers while promoting individual learning. It lets employees and teams hear both positive and constructive customer feedback directly and immediately, in the customer's own words. It enables them to follow up with any customers whose feedback merits, and it supports actions they can take to improve the customer or employee experience.
Second is the outer loop, which tackles structural problems no single frontline rep can fix alone:
The outer loop's explicit purpose is to prioritize and support the kind of customer-friendly changes that employees and teams can't make on their own.
Connecting the two are huddles, short interactive team meetings at all levels of the organization, usually 15 to 30 minutes and often held daily or weekly, where teams can elevate broader issues to other parts of the company that can resolve them.
For a software team running a product feedback loop, those three pieces map straight onto day-to-day product work. The inner loop is replying to the specific customer who reported a bug or asked for a feature. The outer loop is changing the product and letting everyone who wanted that change know it shipped. The huddle is your weekly triage session where product, support, and engineering read new requests together and make calls.
Bain's outer-loop page describes a group responsible for "running an effective process that gathers ideas, deduplicates and triages those ideas, and routes" them to the right team. At a software company, that is what a feedback board does.
You need both loops, because running one without the other leaves an obvious hole. In March 2025, MaddieJ of Airtable announced that product ideas would move out of the community forum and into a form:
As you all likely noticed with our last community experience, we weren't able to process or respond to your feedback at scale, as it just lived in the community platform.
In the same post, MaddieJ noted that Airtable can't guarantee ideas will be implemented, reviews all feedback, and would share trends back to the community in regular updates called "Product Playback". Two days later, in the second reply on the thread, customer gaston asked:
will there be any way for users to track the status of submitted ideas (like "under review" or "planned for future release")?
Airtable had outlined an outer loop in bulk, sharing high-level trends with the whole community, and within two days a user was asking for the inner loop, a way to see where their own idea stood.
How to close the feedback loop, step by step
A customer feedback loop for a software product comes down to five steps that keep every request tied to the people who asked for it.
-
Collect feedback in one place. How you collect customer feedback matters less than where it ends up. If requests stay scattered across support email, live chat, and general forum threads, you end up with the Shopify problem Moeed described, where ideas vanish before anyone can track them or follow up later. Funnel every request onto one list with the customer's email or account attached.
-
Acknowledge it, with a time you can keep. Telling customers when someone will look at their submission sets a clear expectation from day one. Miro states its review window plainly in its community wish list rules:
The Miro Community team will process your new idea in 1-5 business days and determine if it is open for new votes
Pick a window your team can actually keep every week, write it where customers submit ideas, and stick to it.
-
Decide, and say the decision. Moving a request to a new status records a decision, and a short comment explains why so voters aren't left staring at a bare label change. Set aside a weekly triage huddle to prioritize feature requests, update their statuses, and reply to feature requests with a sentence explaining each call.
-
Act, and report what actually shipped. Big requests rarely land in a single release, and waiting until every last piece is finished makes it look like you abandoned the thread. On ClickUp's public board, a request for "Offline functionality on mobile" had 4,431 votes. In August 2026, Joey of ClickUp posted an update naming the one piece that had shipped and left the request open for the rest:
Hey everyone, quick update on this one.
A couple weeks ago, we shipped Offline Task Creation in our mobile app. Now, when you create tasks and you don't have great cell reception, we will queue it to be created when you are back online.
This was a top ask from many of you so I hope you enjoy!
Try it out & let me know what else you'd like to have functional offline on mobile! 📱
Reporting a partial ship honestly as partial tells customers what works today and gives your team direct input on what to tackle next.
-
Tell everyone who asked, however late. Teams often skip updating old requests because they feel awkward about how long the work took. Post the update anyway. On Ahrefs' public board, Anna Wolf requested "Word count on SERP overview" on July 20, 2017, and 111 people voted on it. More than five years later, on March 10, 2023, Andrey Kirillov of Ahrefs marked it complete with one line:
Word count has been added to the SERP overview widget in Keywords Explorer and Site Explorer.
One concrete sentence naming what shipped and where to find it is enough, and you can pair bigger releases with a public changelog post.
Closing the feedback loop when the answer is no
Teams often put off updating requests they plan to decline because saying no to a customer feels awkward. Telling a customer you won't build something still gives them a clear answer so they can plan around it, rather than checking back months later to find an untouched thread.
Bain sets a similar boundary when describing what the inner loop is actually for:
The objective of the Net Promoter System's inner loop isn't to satisfy every customer at all costs; it is to earn profitable promoters by enhancing customer relationships while allowing your teams to learn and improve.
When kenneho asked Remember The Milk to respond to feature requests and update their statuses, the ask was simply for "some sort of feedback" on customer contributions.
When a request falls outside your roadmap, update its status, state the reason plainly, and share a workaround if one exists. If you want copyable wording for a decline, a not-yet, or a shipped update, you'll find real examples and templates in how to respond to feature requests.
How to tell whether your closed-loop feedback system is working
To see where your loop is leaking, open your backlog once a month and count four things:
- Requests older than 30 days with no status and no reply from the team. These are the requests sitting untouched on your board while customers assume nobody read them.
- Time from a request being posted to the first response. Watching this number tells you whether your triage huddle is actually keeping up with incoming volume.
- Requests marked shipped where the people who asked were not told. If fixes keep going out in releases without anyone updating the original thread or notifying voters, the outer loop is breaking right at the finish line.
- Status changes made without a comment. A spike here means your team is flipping labels to keep the board tidy while leaving customers without the reason behind the decision.
If any of those four numbers is climbing, you know exactly which step in your loop needs fixing.
Keep everyone who asked in the loop.
Collect requests on one board, track decisions with clear statuses, and email every voter when a status changes. Free to start.
Closing the loop in UserJot
We built UserJot for feature request tracking around a public feedback board where customers post, vote, and comment. As someone types an idea, the board shows similar requests so they can vote instead of creating a duplicate. If you enable Conversations, which is in beta and free on every plan while it is, Juno searches your public board inside support chat and adds the customer's vote or files a new request once they confirm.
Requests move through six statuses: Pending, Reviewing, Planned, In Progress, Completed, and Closed, with Planned and In Progress appearing on your public roadmap automatically. Any status change, including marking a shipped request Completed, emails everyone who posted, voted, or commented, and you can link the request under your changelog post when you announce the release. Leave the reason in a comment on the request so people who click through from the status email see it there; on its own, a teammate's comment emails only the person who posted the request. The board, statuses, status emails, and roadmap are all on the Free plan, with paid plans at a flat $29 and $59 a month.
Frequently asked questions
What is closed-loop feedback?
Closed-loop feedback means every customer who shares a request, bug report, or piece of feedback hears back about what was decided or done with it. The term comes from control engineering and entered customer feedback through Bain & Company's Net Promoter System, described in a 2009 Harvard Business Review article. The loop closes when the person who spoke up knows the outcome.
What is the difference between open-loop and closed-loop feedback?
An open loop collects feedback and never reports back to the person who sent it, even if the team reads it internally. A closed loop connects collection to a visible decision or follow-up. On Shopify's community forum, a user noted that feature requests dropped into general discussion threads mostly disappeared without anyone tracking them, leaving those loops open.
What are the inner loop and the outer loop?
Bain's Net Promoter System divides closed-loop feedback into two parts connected by short, regular team huddles. The inner loop is following up directly with the individual customer who gave feedback. The outer loop is making broader changes to the product, process, or policy and keeping customers and employees informed about progress whenever it is relevant or required.
What are the steps of a customer feedback loop?
A customer feedback loop for a software team runs in five steps: collect every request in one place, acknowledge it within a window you can keep, decide and explain the decision, act and report what actually shipped, and tell everyone who asked when it goes live. Skipping that last step leaves the loop open even when you build the feature.
What is an example of closing the feedback loop?
On Ahrefs' public board, a user named Anna Wolf requested "Word count on SERP overview" in July 2017, and 111 people voted on it. In March 2023, Andrey Kirillov of Ahrefs marked the request complete with a single line naming where the new word count lived in Keywords Explorer and Site Explorer.
What is a closed-loop feedback system?
A closed-loop feedback system connects one place to collect customer feedback, clear statuses to record what the team decided, and notifications that tell people when a status changes. For a software team, that can be a feedback board, a roadmap, and a changelog paired with direct replies to customers.
Do you have to close the loop on every piece of feedback?
Every customer who submits a request should be able to see a decision, even when you decide not to build what they asked for. Closing the loop means sharing the outcome, and a clear no with a short reason closes it just as cleanly as shipping a feature.


