When a software team depends heavily on a few people with critical knowledge, how do you reduce that risk without slowing their most important work? What one knowledge-sharing practice has made your software team more resilient in a real situation?