Creating a knowledge-sharing culture
summary
Starts weekly/Friday lectures, a newcomer wiki and a zero hidden knowledge policy so knowledge leaves employees with documented pages and onboarding links; runs monthly one-day hackathon learning days, invites local user groups into the office, buys ebooks and pushes developers to speak. Ties bonuses and transparent finances to visibility and client diversity, which flips opponents into supporters; 20% of a major Java conference’s speakers come from the company after a year. Adds five‑minute team plus 45‑minute technical retrospectives; culture shift takes one to two years.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:14Failed knowledge-sharing attempt
- 4:37Friday workshops revival
- 7:24Cultural clash
- 8:05Transparency and bonuses
- 9:52Building new system
- 11:57Hackathons and user groups
- 13:40Learning culture strategies
- 16:52Conclusion
related talks
05mCultivating a Learning Culture: Unlocking the Power of Continuous Development
23mKnowledge sharing in the company
11mLightning Talk: Building a Community Inside your Company
46mYour developer’s intelligence isn’t artificial
15mGrowing at Work with Community-oriented Development
43mKeynote: Coding Culture
01h 00mEvolving Quality Through A Culture Of Learning
36mCultivating a Culture of Continuous Learning