ListenListening Post
Send a short regular digest of what members are saying to the people who build and decide.
Community teams hear things first: the confusing feature, the policy that annoys everyone, the idea nobody asked for that everyone wants. If that knowledge stays in the community team's heads, it changes nothing. A regular digest carries it to the people who can act.
How to use it
- Choose your audience: product, leadership, programme staff or whoever makes decisions members care about.
- Set a rhythm, such as fortnightly, and a fixed length, such as one page.
- Include the top three themes with counts, two or three representative posts with links and one emerging issue.
- Separate what members said from what you think it means.
- Ask readers what they will do with it, and track the answers for Tell Them What Changed.
Example
A hypothetical hospital trust's staff community sends a fortnightly digest to the operations board. One digest surfaces repeated complaints about a confusing shift-swap form, which is simplified the following month.
Watch out
- Only reporting complaints, or only praise. Readers stop trusting a digest that always sounds the same.
See also Tag The Signal, Tell Them What Changed, Prove The Value.