Community Insights in Practice: How Continuous Feedback Enables Better Product and Communication Decisions

Community Insights in Practice: How Continuous Feedback Enables Better Product and Communication Decisions

Ongoing feedback

Does this sound familiar? A feature goes live after months of internal consultation, and four weeks later it turns out that hardly anyone is using it. That’s because it solves a problem that nobody actually had in practice. If you work in product management, marketing or research, you’ve probably come across this situation at some point. Although you have data, you still lack a genuine understanding of what actually drives your target audience. And this is rarely because nobody is asking. Rather, it’s down to how the questions are asked.

The starting point usually lies within the line department

A closed brand or customer community does not differ from a traditional survey or panel in that it provides continuous monitoring. Tracking studies and repeat surveys do that too. The difference lies in where a topic begins and where it ends up.

In practice, this rarely looks like a neat methodological model; it’s more like a cycle. A specialist department raises a topic because it needs to prepare for a decision, or the community team itself recognises that there is a need for information on a particular topic. From there, the topic moves on to the community, returns having been analysed, and, in the best-case scenario, feeds into precisely the decision for which it was originally intended.

What makes this approach valuable over time is the long-term relationship with the participants. Unlike with a rotating panel, in a closed community you repeatedly speak to the same members on different topics, often within a matter of days. Feedback therefore never stands alone, but is always in the context of what the same group has said previously. If you revisit a topic after a few months, you can see whether anything has shifted or whether an earlier reaction was merely a temporary blip.

What happens within the community itself

As soon as a topic is raised within the community, it is moderated and usually addressed on two levels simultaneously. It is discussed in a forum and, in parallel, surveyed quantitatively, rather than both being carried out sequentially in separate steps. This simultaneity of discussion and survey is the real advantage, not the choice between different formats. This is because it provides a figure and, at the very same moment, an explanation of why that figure looks the way it does.

The result is a snapshot of the community, rather than of the entire market. An approval rating initially says something only about this group at this particular point in time. What is usually more interesting than the rating itself is what is said in the comments. Why does someone agree? Why does another person hesitate? The language used by participants can also be systematically analysed and tracked across multiple surveys. It is precisely this structured analysis that requires the most care and is most easily overlooked when results need to be summarised quickly.

The path back to the line department is the most difficult part

The truly critical step is feeding the results back to the line department. And it is precisely here that, in practice, a surprising number of initiatives fail. Results end up in an internal report that nobody actually reads in the end. And the specialist department that originally raised the issue is completely unaware of it.

Here’s an example from our own experience at crowd-creation of how things can be done differently: when a specialist department raises an issue, it first goes to the relevant community manager. They prepare it for the community, usually as a combination of a discussion and a directly integrated survey. Technically, these are in the same space, so members don’t have to switch platforms.

Once the activity is underway, the Community Manager moderates it on an ongoing basis. This means they can see opinions developing in real time, rather than only afterwards in an evaluation table. After a few days, the results are analysed. Not as a set of anonymous figures, but alongside the accompanying comments, because it is precisely these that make all the difference. This analysis is then sent back to the specialist department as a brief, clearly presented summary. The community manager remains the same point of contact throughout, on both sides of the cycle.

Why it’s worth the effort

If this cycle runs reliably, it fundamentally changes the way decisions are made. Instead of an internal guess as to what the target audience might want, there is actual feedback from the community. Product decisions can be validated before launch, rather than having to be corrected afterwards. Communication strategies can be tested before the budget for a wide-reaching campaign is approved.

However, it is also true that the effort involved is real. A closed community requires ongoing moderation. The combination of discussion and quantitative surveys needs to be thought through anew for each topic. And the analyses must be presented in such a way that they actually reach the relevant specialist department, rather than getting lost in a report. But it is precisely this effort that makes the difference between a platform that fizzles out after a few months and an active community that helps shape decisions over the years. It does not merely collect feedback, but keeps the channel between the target group and the specialist department open time and time again.