How does your team capture and eliminate tribal knowledge before it becomes a bottleneck?
by•
Every fast-growing engineering team runs into the "tribal knowledge" trap: knowledge lives entirely inside a few senior engineer's heads.
I’d love to hear how other teams are tackling this:
Processes: How do you encourage developers to document key technical decisions without making it feel like tedious admin work?
Tooling: What tools or workflows have actually stuck for keeping internal docs updated as code continuously evolves?
Culture: How do you make knowledge sharing a default habit rather than an afterthought?
Looking forward to hearing what’s working (or not working) for your team!
7 views
Replies
Zep and Graphiti are probably the most relevant tools I’ve seen for this. Codifying tribal knowledge is doable, but even with AI, keeping it accurate and current can quickly become a full-time job.
Processes: I would avoid forcing developers to document everything manually. Let the system capture decisions from PRs, issues, Slack conversations and meetings, then ask people to validate only the important or ambiguous parts. Capture is usually much easier when it happens as a by-product of the work.
Tooling: Zep and Graphiti are worth looking at, particularly for temporal knowledge and agent memory. I also tried to sign up for Dosu, but it still seems fairly gated. You currently need to speak with them before getting access.
Culture: The real goal should be to make knowledge sharing require almost no additional effort. People should not have to remember to update a wiki every time something changes. Retrieval should happen automatically in the tools they already use, while the system flags stale, conflicting or uncertain knowledge for review.