What this article solves: This article explores where tribal knowledge resides within engineering teams, based on recent surveys and data. It highlights common patterns, tradeoffs, and the implications for documentation practices.
Who this is for: This is for engineering teams and leaders looking to understand the landscape of knowledge sharing and documentation within their teams.
Tribal knowledge often exists in informal settings that can hinder efficient collaboration and onboarding. Recent surveys indicate that a significant portion of this knowledge is trapped in conversations, personal notes, and outdated wikis. Understanding where this knowledge resides is essential for engineering teams aiming to create reliable documentation practices and reduce the risk of knowledge loss.
The Landscape of Tribal Knowledge
Surveys of engineering teams reveal that tribal knowledge primarily resides in three key areas: informal conversations, legacy documentation, and personal notes.
Informal Conversations: A staggering 55% of engineers report that they rely on verbal communication to share critical information—Slack threads, standups, and calls summarized in tools like Fathom but never linked to a ticket. Fast, human, and usually unsearchable six months later.
Legacy Documentation: Around 30% of teams point to outdated Notion, Confluence, or Google Drive folders as a major repository of tribal knowledge. The content felt official when written; it rarely survives the next reorg or rename.
Personal Notes: Approximately 25% of engineers maintain their own notes or documentation. While this allows for personalized organization, it creates silos of information that are not shared across the team, leading to knowledge gaps during onboarding or project transitions.
The code-adjacent gap: Decisions that did get written down often live only in GitHub review comments or a Linear/Jira ticket—never promoted to a doc a new hire would find.
Key Patterns and Tradeoffs
Tradeoff Between Accessibility and Accuracy
One notable trend is the tradeoff between accessibility and accuracy of information. Teams often prioritize quick communication methods, such as Slack, which leads to the sharing of knowledge that may not be fully vetted or documented. This immediacy can create a false sense of security—engineers may believe they have access to all the information they need, but critical details may be lost over time.
The Impact of Team Size
Survey results indicate that larger teams often struggle more with tribal knowledge retention. In teams of over 20 members, 70% of engineers report that knowledge is more likely to be siloed, with informal communication dominating over formal documentation efforts. Smaller teams, on the other hand, tend to have better knowledge sharing practices, as they rely more on cohesive communication channels.
The Role of Culture in Knowledge Sharing
The culture within engineering teams also plays a vital role in how tribal knowledge is disseminated. Teams that prioritize open communication and collaboration tend to have more structured documentation practices. In contrast, teams with a more hierarchical culture may experience greater barriers to knowledge sharing, resulting in a reliance on informal methods that can lead to inconsistent documentation.
Bridging the Gaps: Solutions for Better Documentation
To combat the challenges of tribal knowledge, engineering teams can adopt several strategies:
Meet knowledge where it already lives: Pull from GitHub (what shipped), Slack (what was debated), and your tracker (Linear or Jira) without asking engineers to rewrite it in a wiki.
Do not fight your official wiki—wire it: Teams on Confluence or Notion still need a publish surface for PMs and compliance. The win is linking wiki pages to PRs so the wiki stops drifting into fiction.
Capture calls before they evaporate: When roadmap or architecture decisions happen on Zoom, Fathom summaries should sit next to the ticket and PR—not in someone's private notes.
Encourage a knowledge-sharing culture: Lunch-and-learns help, but culture without tooling still ends in Slack scrollback. Tooling without culture still ends in empty PR templates. You need both.
Conclusion
Understanding where tribal knowledge lives within engineering teams is crucial for effective knowledge management and documentation practices. By addressing the patterns and challenges identified in surveys, teams can create more robust systems for documenting and sharing critical information, ultimately leading to improved productivity and reduced onboarding time.
For teams looking to streamline their documentation processes, consider exploring how ScopeDocs can help automate and integrate documentation directly with your workflow.