The community knowledge playbook

Why answers get lost

Most communities start in chat. Chat is great for the conversation happening right now and bad at everything after. Messages are sorted by time, so a clear answer from last month sits under hundreds of newer messages. On some tools it disappears from view: Slack's free plan shows 90 days of message history (Slack pricing, checked September 2026).

The cost is quiet. The same five questions get asked every week. Experts get tired of answering them and drift away. Newcomers learn that asking is faster than searching, which makes the problem worse. None of this shows up on a dashboard, but everyone in the community feels it.

The fix is not to ban chat. It is to give questions a separate home where each one has a title, a status and a marked answer, so the answer can be found later. The rest of this playbook shows how to set that up and keep it healthy.

Decide what belongs

Not everything needs to be kept. Banter, event logistics and "is anyone around?" messages can stay in chat. A knowledge base should hold questions whose answers will still be useful to someone else in a month.

A simple rule works well: if it has been asked twice, it belongs. The second time a question comes up, ask the person to post it as a question thread, answer it there, and mark the answer. From then on, you link to it.

Write down three or four topics your knowledge base covers, such as onboarding, billing, tools and program rules. Topics become tags, and tags make browsing possible for people who do not know what to search for.

Set up the structure

In Dium, a community is a Flow and each thread is a Wave. Waves have types. For a knowledge base you mostly need three: question Waves for things people ask, discussion Waves for open topics without a single answer, and announcement Waves for things you tell everyone.

Keep the setup small at first:

• One Flow for the community. If you run several related groups, such as one per cohort, keep them as separate Flows in the same Room so members and DMs carry across
• Three to five tags that match your topics
• One or two profile types for people whose answers carry weight, such as mentors or staff
• A pinned welcome Wave that explains where questions go

Resist the urge to build ten categories on day one. Structure should follow the questions people actually ask, not the ones you expect.

Teach members to ask well

A good question is half the answer, and it is also what makes the thread findable later. Share a short template in your welcome Wave and model it yourself:

Title: a full question, e.g. "Can late joiners get a partial refund?"

Context: what you are trying to do and why
What I tried: links, steps, or what did not work
What a good answer looks like: a yes or no, a number, a how-to

When someone posts a vague title such as "quick question", edit it or ask them to. Titles are what search reads first, and what the next person skims.

Answer and mark

The single most useful habit is marking the best answer. In Dium the person who asked, or a moderator, marks one reply as best. The Wave shows as Solved, and the answerer is notified.

Three rules keep marks meaningful:

• Mark the complete answer, not the first one. The best answer is the one a stranger could act on without reading the rest
• Mark within a day or two. Remind askers in your weekly round-up if they forget
• When the asker has gone quiet, a moderator marks it and adds one line saying why

Marks also feed each member's trust score, where a best answer counts three times as much as an ordinary reply. That is a gentle nudge toward answers that solve the problem.

Seed it before launch

An empty knowledge base teaches people not to search. Before you invite everyone, fill it with the questions you already know people ask.

• Collect the 20 most repeated questions from chat, email and support tickets
• Post each as a question Wave with a clear title
• Have staff or experienced members answer, then mark the best answer
• Invite five members who answer a lot and give them a mentor or expert profile type

Twenty solved questions is enough for a newcomer's first search to find something. That first success is what builds the search-first habit.

Run a weekly rhythm

Knowledge bases do not maintain themselves, but they need less work than people fear. A steady weekly rhythm is enough for most groups under a few hundred members.

Dium helps with the reminders: members can choose daily or weekly email digests in their own time zone, with quiet hours, so new questions reach the people who can answer them. Office hours Waves can repeat weekly, every two weeks or monthly, and Dium schedules the next session when one ends.

Keep it fresh

Answers go stale. Prices change, links break, policies get rewritten. A stale answer is worse than none, because it looks trustworthy.

• Once a quarter, skim the most viewed solved Waves and check each is still true
• When a policy changes, post an updated reply and move the best answer mark to it
• Let old, unanswered questions close. In Dium, question Waves in question mode archive after 14 days without activity, so the open list stays short
• Turn the most linked threads into proper help articles, and point the thread at the article

Measure what matters

You do not need a dashboard to know whether this is working. Four numbers, tracked by hand once a month in a spreadsheet, tell you most of what you need.

Watch the trend, not the level. A rising share of solved questions and a falling number of repeats means the knowledge base is working.

Your first 30 days

After that, keep the weekly rhythm and review the numbers monthly. If you want a head start on the first live session, the free AMA and office hours planner builds an agenda and checklist for you.