Why Finding Documents Is Not the Same as Finding Answers

A software engineer observed that despite having access to all relevant documents, understanding why a legacy service bypassed API gateway checks required piecing together an ADR, a Slack thread, a commit message, and a Jira ticket. No single document held the full explanation; the answer only emerged from the relationships between them. This experience led to a distinction between search, which retrieves individual artifacts, and discovery, which reconstructs explanations from multiple sources. Most retrieval systems assume the answer lives in one document, but organizational knowledge is often fragmented across tools and teams. The author argues that what organizations most frequently lose is not the documents themselves, but the connections between them.