In practice
In March a customer asks for CSV export of invoices. In June you ship it. You write to that customer: "In March you asked to export invoices to CSV. It's live under Billing, Export." That message closes the loop.
This isn't the same as release notes. Release notes announce to everyone. A closed loop speaks to the person who asked.
Bain splits it in two. The inner loop is following up with one customer. The outer loop is fixing the cause so the next customer doesn't hit it.
How to do it
- Keep who asked for what, in their words.
- When work ships, find everyone linked to it.
- Write each person a short note: what they asked, what changed, where to find it.
- Have a person check it's true, then send.
- If you decide not to build it, say so and why. That closes the loop too.
Common mistakes
- Sending a generic changelog email and calling it closed.
- Promising a fix in the follow-up that nobody has decided to build.
- Telling a customer something shipped when it only merged. A wrong notice is worse than none.
What changes in AI-first products
Agents ship fast, and the people who asked rarely hear about it. Drafting the note is cheap now; knowing who asked and checking it's true still matters. When a job ships, Annsa's Share Back drafts a note to each person who asked, quoting their feedback. A person reviews and sends it; auto-send is off by default.
See how Annsa does it: Share Back →