Knowledge at Work
Thinking on how teams store, share, and synthesize what they know.
Knowledge Management in 2025: Why Static Wikis Are No Longer Enough
The wiki was invented to capture knowledge. But the way teams create and consume knowledge has changed.
What RAG Actually Means for Your Internal Documentation
Retrieval-Augmented Generation is a phrase you've probably heard. Here's what it actually looks like when applied to a real company's internal knowledge.
Building a Knowledge Graph from Scratch, Using the Docs You Already Have
Knowledge graphs sound like infrastructure projects. But for most teams the raw materials already exist in Confluence, Jira, and Slack.
What Confluence Search Misses (and Why It's Not Confluence's Fault)
Confluence search is designed to find documents. It's not designed to answer questions. That distinction explains most of the frustration.
The Real Cost of Knowledge Silos, and Why It Compounds as You Hire
Every hire adds knowledge to your organization. Without synthesis infrastructure, the percentage accessible decreases with headcount.
Why Source Attribution Matters More than Answer Quality in AI Knowledge Tools
A confident-sounding answer without a source is actually worse than no answer.
The Answer Was in the Ticket: Why Jira Is a Hidden Knowledge Base
The decision to use gRPC over REST is somewhere in a ticket comment from 2024. These aren't edge cases.
Semantic Search Isn't Just Better Keyword Search, It's a Different Model of Retrieval
Teams come to Corpussage expecting faster keyword lookup. They stay because semantic retrieval surfaces answers they didn't know to search for.
From First Day to First Merge: How Knowledge Access Changes Onboarding Time
The biggest variable in engineering onboarding time is how quickly a new hire can answer questions independently.
Search vs. Synthesis: What Your Knowledge Tool Should Actually Do
The knowledge management space is broadly organized around search. Corpussage is organized around synthesis.
Knowledge Half-Life: Why Documentation Goes Stale Faster Than You Think
Documentation that was accurate six months ago is already partially obsolete. Most teams have no mechanism for knowing which parts are stale.