Every growing company eventually develops archaeologists.

These are the people who know which Slack thread contains the real answer, which doc is current, which dashboard is trusted, which decision was reversed, and which executive comment changed the plan.

They are valuable because the system is broken.

Slack archaeology, doc spelunking, and “ask Sarah, she knows” are symptoms of poor information architecture. The company has information, but not reliable retrieval. Context exists, but not in a form that compounds.

Internal communication does not work if people cannot find the authoritative version later.

A source of truth is an ownership claim

A source of truth is not just a place where information lives. It is a promise that this is the authoritative version and someone owns keeping it accurate.

Without ownership, “source of truth” becomes a label pasted onto a doc that slowly rots.

Every source of truth needs:

  • an owner;
  • a scope;
  • a status;
  • a last-updated date;
  • update triggers;
  • links to related artifacts;
  • archival rules;
  • a clear audience;
  • permission boundaries;
  • a way to report errors.

If nobody owns it, it is not a source of truth. It is a snapshot.

Search is not a strategy

Leaders often assume search will solve information sprawl.

It rarely does.

Search works when people know the right terms, documents are named consistently, old versions are archived, permissions are sane, and authoritative pages outrank obsolete ones. In real companies, the same concept may be called onboarding, implementation, customer launch, activation, time-to-value, or success plan. Search returns everything and nothing.

AI search may help. It will not fix unclear ownership, stale content, contradictory records, permission gaps, or missing decision logs. It may even make the problem harder by confidently summarizing bad information or exposing context to people who should not see it.

Retrieval quality begins with information architecture.

Design for the next reader

Most internal docs are written for the writer's immediate need, not the next reader's future retrieval.

The next reader may be a new hire, a manager in another function, a remote employee in another timezone, a leader preparing a customer conversation, or the same team three months later trying to remember why a choice was made.

Design for that reader:

  • use plain titles;
  • include a short summary at the top;
  • name the owner;
  • state whether the doc is draft, current, or superseded;
  • link to decisions, dashboards, and related policies;
  • explain what changed from the prior version;
  • remove or archive obsolete versions;
  • include keywords people actually use.

This is not bureaucratic polish. It is retrieval design.

Slack should point to truth, not contain it

Chat tools are excellent for surfacing questions. They should often point to sources of truth, not become them.

When someone asks, “What is the current policy?” the best answer is not a fresh paragraph in Slack. It is a link to the policy, plus a quick note if needed. If the policy is unclear, update the policy. If the answer is new, create or amend the source of truth.

Otherwise every answer creates another unofficial version.

The same applies to decisions. A Slack thread can discuss a decision. Once made, the decision log should hold it. Then the Slack thread can link to the record.

The source-of-truth map

Build a map for the company:

  • Strategy and priorities: owner, location, update cadence.
  • Company metrics and dashboards: owner, definitions, commentary rhythm.
  • Product roadmap and launch plans: owner, status, customer-facing guidance.
  • Policies and people practices: owner, effective date, exception path.
  • Decision logs: owner, scope, revisit rules.
  • Customer escalations and incident records: owner, lifecycle.
  • Operating cadence artifacts: owner, archive location.
  • Manager cascade materials: owner, expiration date.
  • Team operating docs: owner, review cadence.
  • Confidential or restricted information: owner, access rule, review date, and safe summary location.

The map matters because people should not need social knowledge to find institutional knowledge.

Information architecture is inclusion

Poor retrieval creates inequality.

Tenured employees know where things are. New employees do not. Office employees overhear context. Remote employees search. People close to executives ask directly. Others guess. High-status functions get answers faster. Lower-status teams inherit stale versions.

A good information architecture is not just tidy. It reduces proximity privilege and makes the company less dependent on informal networks.

The point

Internal communication is not complete when a message is sent. It is complete when the right person can find the right answer later, trust it, and know who owns it.

If people must perform Slack archaeology to understand decisions, the communication system is leaking memory.

Fix the architecture. Assign owners. Archive the old. Make truth retrievable.