The primary goal for documenting tribal knowledge while offboarding employees is sharing knowledge. The issue is that not everyone likes or knows how to document what they know. Three approaches to documenting tribal knowledge: 1. A pair-programming-style approach. Ask the exiting employee questions, and then you document the answers in the way that is most comfortable or helpful. The culling or collecting of this knowledge can always come through interviews and meetings. I recommend recording these meetings. Later on, you can work on post-offboarding documentation writing and review. 2. Brain dump. The exiting employee may want to be left alone to write and “brain dump.” 3. Swimm’s Platform. Use Swimm’s documentation platform to create code-coupled docs. You can assign a doc to a Swimm user via the Assign link, or assign a doc from a predefined set of reasons (needs review, needs updating, FYI, other) and include an optional note. 1. A pair-programming-style approach. Ask the exiting employee questions, and then you document the answers in the way that is most comfortable or helpful. The culling or collecting of this knowledge can always come through interviews and meetings. I recommend recording these meetings. Later on, you can work on post-offboarding documentation writing and review. 2. Brain dump. The exiting employee may want to be left alone to write and “brain dump.” 3. Swimm’s Platform. Use Swimm’s documentation platform to create code-coupled docs. You can assign a doc to a Swimm user via the Assign link, or assign a doc from a predefined set of reasons (needs review, needs updating, FYI, other) and include an optional note. Whichever approach you go with, make sure there is enough time to discuss and review everything with employees before they leave.