Customer research for Knowledge base software

Define the question before collecting names

For knowledge base software, investigate whether answers live in old chat threads and new staff repeat the same questions. Research is useful when it explains a workflow, its owner, and an unresolved constraint. A list of companies in a sector cannot establish that those companies have this problem.

Begin with new hires searching for reliable internal procedures and check how their work relates to an enablement or operations lead responsible for repeat questions. Map the current process around pinned messages and a loosely organized shared document. You are looking for the step where the workaround stops being adequate, rather than asking people to validate an abstract product idea.

Search for the language of the problem

Try the queries below in a search engine or the search feature of a relevant professional community. Read the original discussion and its date. Results are starting points for research; these query examples do not claim any particular search volume or the existence of a matching prospect.

Write an evidence note you can revisit

Illustrative source text: “Every new teammate asks how to issue a refund, and our pinned answer is already outdated. How do we keep procedures owned?” Save the actual source URL and date when researching a real example. Keep a short relevant excerpt and your interpretation in separate fields. Do not rewrite your interpretation as something the author said.

The working hypothesis is that several new hires are onboarding in the same month. The missing information includes whether the author is an enablement or operations lead responsible for repeat questions, whether the need is still open, and which implementation requirements remain unverified. Keep this constraint visible: search quality cannot compensate for missing owners or outdated source material.

• Observed: the original words, the visible date, the task described, and any explicit requirements.
• To verify: whether the current process is pinned messages and a loosely organized shared document.
• Disqualify when the need belongs to teams expecting automatic expertise from a product that only organizes their existing knowledge.
• Next step: one context-appropriate question, or no contact when there is no suitable route.

Use a short discovery interview

Ask about a recent event before showing your product. Let the person explain the sequence in their own words; do not treat agreement with a leading question as validation.

• Which repeated question interrupts an experienced colleague most often?
• Who owns the answer and knows when it becomes stale?
• What would need to be true for you to publish five frequently requested procedures with owners and review dates?
• How would you verify that a new teammate completes one procedure using the article without asking its author?

Turn notes into a research decision

Compare independently sourced accounts of the same task. Keep an example that contradicts your hypothesis, such as this ambiguous scenario: A team requests a wiki without naming anything people need to find. It may justify more reading, but it is insufficient to label someone a buyer.

At the end of a bounded research session, decide whether to narrow the audience, ask a specific follow-up, change the pilot, or stop. Keep unknowns visible and store only the information needed for that decision. Research quality is measured by a better decision, not by how many names are collected.