Ruby Video
Talks
Speakers
Events
Topics
Leaderboard
Sign in
Talks
Speakers
Events
Topics
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
RubyConf 2018 - The Dangers of Tribal Knowledge by Annie Sexton Are you constantly tapped on the shoulder for answers? Tired of being the Google for your team? Or perhaps you’re the new kid, having to ask a dozen different people to find answers to all your questions? These are the consequences of tribal knowledge. In this talk we’ll discuss how to have a team that self-serves, finds answers on their own, without forcing them to wade through a colossal employee handbook.
Date
Summary
Markdown supported
In her talk titled "The Dangers of Tribal Knowledge" at RubyConf 2018, Annie Sexton addresses the issues that arise when critical information is only held in the minds of a few individuals in a team, a phenomenon referred to as tribal knowledge. This presents significant barriers to efficiency and self-sufficiency within organizations. Key points discussed include: - **Definition of Tribal Knowledge**: This is information that exists only within the minds of team members and is not documented elsewhere, creating potential bottlenecks and risks if individuals leave. - **Impact on Team Dynamics**: Annie describes scenarios where both senior and junior developers suffer from the burden of tribal knowledge—senior members face interruptions while the new ones struggle to find essential answers, leading to frustration on both sides. - **Consequences of Poor Documentation**: Essential information can be scattered across various platforms like Google Docs, Trello, and emails, making it difficult for team members to find necessary resources. - **Creating a Self-Sufficient Team**: To address the challenges of tribal knowledge, Annie proposes the establishment of a structured onboarding process made up of two main components: - **A Crash Course**: This serves as an introductory guide to help new employees understand the basics quickly, enabling them to seek answers independently afterward. - **A Knowledge Base**: An organized repository where comprehensive documentation is stored, ensuring it’s easy to find, update, and search for information. - **Example from Heroku**: Annie shares her experience at Heroku, highlighting how the support team introduced a crash course and a knowledge base for onboarding new support engineers. This included essential readings and procedures to facilitate better understanding. - **Keeping Documentation Up-to-Date**: The importance of regularly reviewing and updating the documentation is emphasized, including setting expiration dates for articles to ensure all information remains relevant. - **Empowering New Team Members**: Annie concludes by stressing that new employees should feel confident to voice their understanding (or lack thereof) to continually improve the documentation process. Overall, the talk serves as a call to action for teams to document knowledge comprehensively, thereby preventing bottlenecks and enhancing self-service capabilities among members, which ultimately leads to a more efficient and productive work environment.
Suggest modifications
Cancel