Skip to main content

When creating a survey, I do this in order to get data, but also very important regarding transparency is to share the result with the community.

Use Case: We are asking for the most popular topics in order to create content on this feedback.

For us some surevey’s are only open for a specific time frame, after I would like to share the results publicly in some cases, would like to pin the final outcome and be able to close the survey so that no more members can participate. 

How do you manage these situations with the current “survey” feature?

Best,
Lena

Oh, I think I accidentially postet it as question/discussion. I wanted to post it as an idea.
 @Julian could you please move it over? Thank you. :) 

 


I don’t have a great solution for you, but can share something we recently started trying. 

I take the topic requests we get from our webinar surveys and share them as ideas on the community for others to upvote. It helps close the loop a bit and also expands the feedback from 1 person’s suggestion to X upvotes from the community (helping with prioritization).

I guess I buried the lede a bit there… we have our Community (and other resources like our Documentation and Training) as “Product Categories” for our Ideas feature. I’m trying to scale community ideas (whether features, programs, webinar topics, article requests, etc) the same way ideation helps with other types of product feedback. (My soap box topic is that managing online communities requires a digital product management approach.) It’s also helpful for encouraging adoption of the ideation feature: have an idea or request? Create an idea, whether for one of our products or resources like the community! 

Truthfully, adoption of ideas for community requests is low. However, I create the ideas from those survey responses as a way to *show* the community the types of behavior I’d like to see. It also makes it easy for them to upvote topics/ideas they agree with, which gives me more data for prioritizing what comes next. It also is an element of the feedback loop element you’re looking for. 

TL;DR Maybe consider sharing ideas from your surveys as ideas on your community? It’s a way to be transparent and also collect more insight. You can also use the ideation features like status labels, pinned replies, etc for communicating updates and managing expectations.


Hi @Lena H.! Thank you for your idea. The survey functionality or polling (how we usually call it) is an extension of the text editor used by our platform. Hence, the expansion of this tooling to cover sharing results and time-bound surveying might be fairly limited by the existing package of the editor. I do see the value in your proposal, especially around creating more user engagement and being more transparent when build content strategies, so I’m opening up this idea for voting and collecting additional insights. 

Just as another possible workaround, have you considered using Typeform surveys? I’m not entirely sure their surveys meet the use case you presented, but they can be embedded in a topic and I’m personally a fan of their UX. Also great suggestion from @DannyPancratz, thanks a lot for sharing! 


NewOpen