Feedback loop

The practice of returning to customers who reported a problem or requested a feature to tell them what was decided and why, closing the circuit between feedback and action.

A feedback loop, in product terms, is the closed circuit that connects customer input to product change to customer notification. The full loop has four steps: collect (a customer shares a signal), synthesize (the team aggregates it into a theme), decide (the team prioritizes and ships, or explicitly defers), and close (the customer hears back about what happened).

Most companies do the first three steps competently and skip the fourth. The customer who took the time to write a thoughtful bug report never hears back; six months later they've forgotten, or worse, churned. Closing the loop — even with "we heard you, we're not building this and here's why" — is the difference between feedback that compounds and feedback that decays.

Closing the loop at scale is the hard part. Manually emailing every requester doesn't scale past a few hundred customers. The pattern that does scale: tag signals to the theme they belong to, and when the theme ships (or doesn't), trigger a bulk notification to everyone whose signal was tagged. This is where most product intelligence tools earn their keep.