-
#TipTuesday: Use Category Descriptions Like Tiny Tour Guides
Happy #TipTuesday Everyone, Category descriptions are easy to overlook. They sit quietly under a category name, usually only a sentence or two long, and because of that they can feel like “set it and forget it” text. But those little descriptions can do a lot of heavy lifting. Think of them as tiny tour guides for your…
-
#TipTuesday - Category, Tag and User Following
Never Miss What Matters: Personalize Your Community Experience with Following One of the greatest strengths of a thriving customer community is the wealth of knowledge being shared every day. New discussions, product updates, feature ideas, best practices, customer success stories, and expert advice are constantly being…
-
#tiptuesday Using AI to Generate Better Test Variants, Faster
In an earlier Tip Tuesday post, I gave tips for getting started with testing in your community. You can read the full post here. One of the hardest parts of A/B testing isn't running the test... often it's coming up with variants to test in the first place. Writing multiple versions of a banner headline or your CTAs can…
-
#TipTuesday: Mark an Accepted Answer when your question is solved
Q&A is one of the most commonly used features in many communities. Members rely on it to ask questions, get help, and learn from others who may have run into the same situation. Because Q&A is so active, it is worth the occasional reminder: when a question has been answered, marking an Accepted Answer helps turn that…
-
#TipTuesday: Make Member Conversations a Regular Habit
I was well into my career as a community builder before I realized the value of intentionally setting aside time to talk directly with members — by phone, Zoom, or even in person when possible. It’s easy to get caught up in moderation queues, analytics, and content calendars. But some of the best community insights come…
-
#TipTuesday - Brand-driven Ideation programs: the not so scary alternative
Ideation programs can be intimidating, and many community teams shy away from implementing them. Sometimes, it's because they feel they won't get buy-in from the Product team, or they think the initial support will eventually fade away. Especially in large communities, teams may also fear receiving a high volume of ideas…