Excited for your session, @DannyPancratzĀ ! I feel like more things need to be managed as products not projects, so Iām looking forward to how you applied those thoughts to community.
ā
@DannyPancratzĀ , your success story at Unqork has genuinely encouraged customersĀ to elevate their community, thus I am excited to hear about your journey at Pulse this year. I appreciate you sharing that with us...CHEERS!!!!!!
ā
I know youāll be the voice of so many Community-pros out thereĀ @DannyPancratzĀ
Your work at Unqork and inSpired, is a living course in Community Management. Rooting for yaĀ ā
+1 to @anirbanduttaĀ ās thought.
Rooting for this one!Ā šš½
Ā
After seeing how well youāve managed the Unqork Community and seeing how youāve topped the inSpired Community, Iām sure there are lots of going to be lots of valuable insights in this session š
This is going to be sooo insightful! š„ #superexcited @DannyPancratzĀ
Ā
Hi @DannyPancratz,Ā This session was really enlightening! Would like to know what role AI will play in your community in the future? What areas do you plan to use AI in moving forward?
Thanks, @Jagari Das.Ā
TBD on what role AI will play in our community; itās something weāre actively monitoring and ideating on, but not rushing into anything.Ā
Our initial and most common use case will be using the community to train and feed AI tools to find answers from our community knowledge base and help users more quickly get answers. That might be through something like the PX knowledge center bot or a solution we develop ourselves. Thatās a customer outcome I can see AI helping with.Ā
Currently, I am glad our community is strongly gated and limited to actual people, as Iāve seen other communities grappling with spam issues from bots and the accelerations in AI.Ā
Iām sure there will be AI-assisted improvements to community management and administration, but Iām already able to achieve a lot of that with RPA that doesnāt need AI.Ā
So, long term, Iām probably most interested in how AI can provide prescriptive recommendations on new content, resources, and events based on community activity.Ā
@DannyPancratzĀ Iām thinking similarly. Though, Iām optimistic that AI could not only detect information or trends, but synthesize them into summaries. Such as, āHereās some of the newest topics being talked about on community,ā or even per-user:Ā āBased on posts youāve interacted with, youāre probably most likely to be interested in X and Y.ā Maybe AI removes the need to build a dedicated recommendation system,Ā andĀ can describe the recommendations with context and summarization, instead of just providing links.
AI for Registered user onboarding is another area that comes to mind, Journey orchestrating users to different areasĀ based on their usage of the Community.
Or even the AI not recommendingĀ contentĀ butĀ people. āYou two should meet. You have so many interests in common."
AI to perform content gap analysis on existing content, so as to create more holistic content for the community.
@DannyPancratzĀ - Thanks for extending your expertise through this insightful session! Community is a great place for the Product Folks & also to the end users who use it. So, do you have any best tips aroundĀ How you'veĀ been able to move your customers from your product to the community, especially when maintaining the flow?
@Revant_AmingadĀ our community āproductā strategy is to be the āeverythingā resource for using our product, so a great second screen (or tab) experience.Ā
Our Community Hub mission is to āconnect our users to the people and resources they need to be successful.ā That gives a clear value prop and helps solve a lot ofĀ jobs to be done for the end users.
How we do that is a through a focus on an integrated āHubā UI, making the community a launchpad to everything they need and help them discover things they didnāt know they needed. Gainsight DHās federated search API is a key differentiator, as it allows us to make the community a true comprehensive search across all resources (even those that live on other platforms: CMS, LMS, our marketplace built on our own platform).Ā
So, in summary, our community strategy emphasizes a focus on the UX, as well as integrating any resource users might need as they use our product. Then, naturally, this extends to creating new community resources that make the community even stickier (and help our customers even more!).
There are also other tactics that help like embedding the community widget in our platform, onboarding email workflows, nudges from CS, etc.Ā
But, imo, it really comes down to the jobs to be done framework and product canvas I talk about in my session: If your community truly offers value, users will adopt it and keep coming back. Our focus on the UX is really just trying to help them understand (or prove) that the Community Hub can help them as they use our product, and thus should be their 1B tab to the 1A of our platform.Ā
(Bonus POV: I donāt know that gamification helps much with the initial adoption, but it can help them once theyāre engaged. They need to find value in the community / start actually using it before any gamification systems will resonate with them. Thus, I donāt have an onboarding gamification path. But we have a lot around contributions like posting, marking answers, etc.)