Start With One Team’s Source Material, Not the Whole Company

Most company knowledge projects start too big.

Support answers are inconsistent. Onboarding handoffs depend on memory. Macros are stale. Internal docs no longer match the way people work. The diagnosis may be right, but “clean up everything” is not a workable first project. It has no clear owner, no useful finish line, and too much material for anyone to review properly.

Start with the tickets, notes, procedures, transcripts, macros, and team discussions behind one part of the operation. Before you collect files, run three tests.

Test 1: Does the source set belong to one team?

A useful starting boundary is work one team can recognize and one owner can explain. It might cover support exceptions, a sales-to-onboarding handoff, renewal-risk reviews, or lead routing. It should not cover every document the company has.

Choose real evidence from that work:

• resolved tickets and customer conversations
• current procedures, old drafts, and saved replies
• CRM notes that legitimately affect decisions
• Slack or Teams exports where exceptions or ownership were discussed
• call transcripts and handoff notes
• examples where the standard answer failed

Include sources the team still sees even when you suspect they are stale. Conflicts between a procedure, a macro, and recent cases are useful findings, not mess to hide before the work begins.

Avoid a full helpdesk dump or an unlabeled drive export. More files do not automatically produce a better result. The team should be able to look at the source list and say, “Yes, this represents the work,” or point out what is missing.

Test 2: Is one accountable reviewer named?

Everyone may want better documentation, but one person must decide what becomes reusable guidance. Choose the process owner before the review starts.

That person needs enough authority to answer:

• Is this procedure still current?
• Is this rule safe to reuse?
• Does this customer-facing language make a promise we should not make?
• Is this exception policy or a one-time judgment call?
• Which source wins when the material disagrees?
• What decision is still missing?

Human review is the trust layer. Drafts should stay drafts until that reviewer approves, edits, rejects, or marks them as needing work. A clean summary without an accountable decision-maker only makes uncertain guidance easier to spread.

Test 3: Will the reviewed result be used soon?

Name the destination before you start. The result might replace a stale procedure, improve a handoff checklist, give support a safer saved reply, document an escalation rule, or expose a policy decision that blocks all of those uses.

If nobody expects to use the result soon, the boundary is probably still too vague. A near-term use gives the reviewer a practical standard: is this accurate and complete enough for the work we need to do now?

Consider a mid-market sales-to-onboarding handoff. New customers keep repeating setup details after the deal closes. Instead of collecting every onboarding document, gather the CRM notes from recent accounts, kickoff transcripts, handoff checklist, customer emails where context was repeated, and escalation notes from delayed launches.

That source set could produce an updated handoff procedure, a rule for when missing account-owner data blocks the handoff, a checklist for open commitments and implementation blockers, a conflict where CRM fields disagree with kickoff notes, and an open question about who may accept an incomplete handoff. One onboarding owner reviews each item before the team uses it.

This is where Company Brain fits. It turns one team’s source material into a draft operational knowledge pack: procedures and rules linked to their supporting sources, saved-reply drafts, gaps, conflicts, outdated-content flags, and open questions. A human owner reviews the items and decides what is approved for reuse. The goal is not to organize the whole company or let anyone ask anything. It is to finish one useful, reviewable piece of operational work.

Ordinary confidential operational material is allowed for this source set, and users should not have to manually sanitize normal business documents. Restricted material remains out of scope: secrets and credentials, payment data, regulated health, legal, or financial information, private employee records, highly confidential strategy, special-compliance material, and anything the organization cannot share under its own obligations.

Pick one team, one accountable reviewer, and one use for the reviewed result. Then gather the files that team actually relies on.

If the source set and reviewer are ready, open the upload workspace. If the team boundary, intended use, or source set is unclear, get scoping help.