Guide
Turn forum conversations into a question log without mistaking a visible discussion for a representative sample of your audience.
A discussion can reveal the language people use, the obstacles they describe and the explanations they find confusing. It cannot, by itself, tell you how common those experiences are. Treat it as a place to find reporting questions, then look for evidence beyond the thread.
Choose a community because the people there encounter your beat's decisions. A software implementation group may reveal different questions from a founder forum, even when both discuss the same product. Write down who participates, who is absent and what the community's rules allow before collecting material.
Read the whole conversation before saving an excerpt. A later reply may correct the premise. Several posts may repeat one original account. Apparent agreement can also reflect moderation, membership or who feels comfortable responding.
Use this log for each promising lead:
| Field | Example of what belongs there |
|---|---|
| Question in the participant's terms | What are they trying to decide? |
| Context | Role, constraints and date, where voluntarily shared |
| Evidence offered | Document, firsthand account, assertion or hearsay |
| Conflicting accounts | Who reports a different experience? |
| Missing voices | Who encounters the decision but is not represented? |
| Next reporting step | A record to inspect or a person to interview |
Keep personal details out of your working copy unless they are necessary. An accessible conversation is not automatic permission to expose a participant to a much larger audience. For sensitive or closed spaces, seek informed permission before quoting or identifying someone.
Suppose, hypothetically, several agency owners disagree about how long a client's procurement process takes. Do not publish “agency procurement now takes three months” from those accounts. Ask what they count as the start, whether the work is regulated, and whether they mean approval or payment.
Those distinctions may produce a stronger practical story: a comparison of the steps people collapse into “procurement.” Interview participants who describe different paths, examine available procurement guidance, and label the scope of the examples you can verify.
The community supplied the question. The interviews and records must support the answer.
When community rules permit, share the finished explanation with enough context that readers can assess its relevance. Correct misunderstandings without treating the group as a distribution channel you are entitled to use. Keep a note of unresolved questions for the next article.
Combine this process with a reader-question log and the human-source interview worksheet. Track whether the reporting resolves a real decision, not merely whether a thread attracted many replies.