Guide

Closing the customer feedback loop, for B2B product teams.

A customer feedback loop is closed when the people who raised a problem hear what you did about it. For a B2B product team that means five steps: hear it, count it, decide, ship, and tell everyone who raised it, including when the answer is no.

Updated

When it ships

You told us in October that changes caught you out before your Monday meeting. As of today, reports show what changed since you last looked.

What is a customer feedback loop?

It is the path from something a customer tells you back to the same customer. Most teams have the first half: calls get recorded, requests get logged. The loop stays open because the second half has no owner. The customer never hears back, and stops telling you things.

That last part is the real cost. In B2B, the customers who stop reporting problems are not happier. They have just stopped expecting an answer.

What are the steps?

  1. Hear it. Keep what the customer said word for word, with who said it and whether you asked. Voice of customer examples shows what to listen for.
  2. Count it. File it under the problem underneath and count companies, not mentions. How to analyse customer feedback covers this.
  3. Decide. Bring the top problems to the meeting that decides what gets built. If you pick one, write a one-page brief.
  4. Ship, or say no. Either is fine. Silence is not.
  5. Tell everyone who raised it. Every company filed under that problem, including the ones who asked for a different fix.

Step 5 depends on step 2. If you only kept a list of requests, you only know who asked for this exact feature. If you kept problems with the companies behind them, you know everyone who will care.

What does a closed loop look like?

A made-up example, start to finish:

4 SepOn a success call, Ostrom says: "I reported it in March and I don't know if anyone read it."
Sep to OctSeven more companies say something similar, six of them without being asked. The theme becomes "Nobody hears back after reporting something".
14 OctPlanning picks it. The brief: every report gets a status its reporter can see. Worth six weeks.
15 OctAll eight companies get message 2 below. Three take a short call. One of them changes the design.
25 NovIt ships. All eight get message 3, quoting what each of them said.
DecemberReports from those eight companies go up, not down. Two of them mention it on their renewal call.

What do you say at each step?

Three short messages, from a person, not a release note. Quote the customer's own words back to them: it shows someone actually listened.

1. When you hear it

Within a day of the call. Short, and only if you have not already said it on the call.

Thanks for telling us about [the problem, in their words]. I've added it to what we're tracking, along with how you work around it today. I'll let you know when we decide what to do about it.

2. When you decide to work on it

When the brief is written, before anything ships.

You told us in [month] that [the problem, in their words]. We're working on it now: [the change, in one sentence]. If you have five minutes before [date], I'd like to show you where we're going and hear if it would help.

3. When it ships

The day it is live. To everyone who raised the problem, not only those who asked for this fix.

You told us in [month] that [the problem, in their words]. As of today, [what changed, as they will notice it]. [One line on where to find it.] Thank you for raising it. It's one of the reasons we prioritised it.

How do you close the loop on a no?

Most teams skip this one, and it is the one customers remember. A clear no with a reason is better than a year of "it's on the roadmap".

You told us in [month] that [the problem, in their words]. We've looked at it properly, and we're not going to build [the request] for now, because [the honest reason]. What we'd suggest instead is [workaround or alternative, if there is one]. If it starts costing you more, please tell us. It stays on our list, and that would change the count.

Mean the last line. If more companies raise the same problem, the count changes, and so can the answer.

Who should do it?

Whoever owns the decision, so usually the product manager or founder, sends message 2 and the no. Message 3 can come from the account owner, but it should still quote the customer and name the problem, not the feature.

What matters more than who: decide it before the work starts. Write "who tells the customers" into the brief, next to how much time it is worth.

How do you know it is working?

  • Customers who heard back raise more problems afterwards, not fewer.
  • "Did anyone read this?" stops coming up on calls.
  • Customers start a call with "you fixed the thing I mentioned".
  • Your no messages get replies, not silence.

Can you keep track of who to tell?

The hard part of step 5 is knowing, months later, every company that raised a problem, and what each of them said.

Ordagrann reads the customer calls you record in Granola, groups every problem and request into themes, counts how many companies raised each one, and turns a theme into a one-page brief your team can build from. Each theme keeps every company and the exact words behind it, so when something ships, the list of who to tell is already there.

Get started

Works with Granola Business. Any other transcript can be pasted in.