Blog · Tag
knowledge-base.
10 posts in this archive.
The Saturday KB hygiene drill
Thirty-five minutes of knowledge-base maintenance that keeps Monday's drafts from citing stale content. A year in, here's the drill that actually stuck.
The January past-performance backfill ritual
Two hours in mid-January to refresh last year's past-performance references so they actually carry the weight they need to for this year's bids. The shortlist, the edits, the re-approvals.
SME collaboration, reconsidered
The 48% bottleneck hasn't moved in five years. Every playbook that attacks it via better communication has failed. The economic frame, three patterns that partially work, the one that fully works, what tooling must do.
Semantic deduplication of KB blocks at ingest
How we merge near-duplicate KB blocks at ingest time using embedding similarity, the threshold we settled on after testing four values, and the trade-off we accept by tuning toward over-merging.
SME collaboration, Part 4 of 4: a KB your SMEs will actually use
What makes an SME contribute to a knowledge base versus what makes them ignore the tool. Closing the four-part series — the structural choices that decide whether your KB compounds or rots.
Content library vs. knowledge base is not semantics
The vendors call it a content library. We call it a knowledge base. The two words name two different products. Why I think the distinction is the most important one in this category.
Shipped: KB block freshness alerts in review
Stale KB content now flags itself before a reviewer touches it. The freshness signal sits inline on every drafted answer that cites a block past its refresh date.
Shipped: content-block freshness scores
Every KB block now carries a freshness score that decays as the source ages, drifts from the company's current marketing language, or contradicts a more recent block. Stale citations get caught at draft time.
In preview: per-block source permissions
Per-block permissions in the KB — control which teams or roles can read, draft from, or edit each content block, with audit trails on every read. In preview while the marketed KB surface catches up.
Shipped: content-block versioning in the KB
Every content block in your knowledge base now keeps an immutable version history. Drafts that cited a block stay tied to the exact text they cited, even after the block is edited.
See the proposal workflow
Take the 5-minute tour, then start a trial workspace when you're ready to run a real pursuit against your own source material.