How do you do knowledge transfer in tech teams?

training up myself over the past few months, it's a mix of reading KB articles, support cases, internal wiki confluence docs, tons of asking for help, asking questions to all sorts of fellow and senior techies, listening and learning and note-taking and further research from customer calls, a good amount of self-learning-by-doing (installing/modifying software, etc.), etc. -- much of it as not-so-technical stuff -- just, how does this business work? how do we do things? what products/processes are changing day to day?

i've been working on a KB-with-built-in-knowledge-certification feature that would, in theory, help address this (it's in perpetual pre-MVP).

use cases might be new Sales / Support Engineers, or Account / Success Managers, who need to learn 300 or so pieces of information -- enough to at least get dangerous quickly -- but they need a way to prove -- to themselves at least -- that they know the material in the KB.

the information doesn't necessarily get stale 'fast', but it def does get stale.

diff folks can give you diff answers.

Most knowledge transfers I’ve been a part of, have been “theatre”. Even when the effort is done in good faith it’s impossible to transfer more than the high level knowledge.

Unless there’s a consistent effort to document the system throughout the lifecycle of the project, you’re not going to be able to do it in the last 2 weeks.

By keeping an up to date knowledge base.

Works great for transferring knowledge to yourself 2 years down the line as well! Foolproof KB articles have saved my arse countless times.