When one person is the only one who knows how to complete a task or maintain a critical service, work can stall when that person is busy or leaves. Knowledge transfer means helping someone else gain the information and skills needed to take on the work. It takes time up front, but it can reduce bottlenecks, support growth, and make a team less dependent on any one person. section 5.1.1 section 5.1.2 section 8.4.3
Choose an approach that fits what needs to be passed on:
- For delegated work, hold a knowledge-transfer session, demonstrate the task, and let the new owner shadow you. Match the task to their experience and continue offering supervision. section 5.1.1 section 5.3.2
- For a departing specialist, arrange lunch-and-learn sessions or technical talks and document critical information before they leave. section 8.4.3
- For a leadership change, have outgoing and incoming leaders plan the handover, define responsibilities and timelines, and organize conversations about critical information. Document what must remain available afterward. section 13.3.1
- For ongoing engineering work, use code reviews, code walk-throughs, pair programming, and mentorship to share practices and learn from one another. section 12.2.1
The time trade-off
Suppose ten similar tasks would take you ten days to complete alone. Spending three days transferring knowledge and one day demonstrating the work while a teammate shadows you takes four days up front. If the teammate can then take on the tasks, you free six days of your own time. The benefit depends on choosing suitable work and giving the person enough support to succeed. section 5.1.1 section 5.3.2
Figure 5.1 Days of work with and without delegation
Compare the days spent doing ten tasks alone with the initial time spent teaching and delegating them. section 5.1.1
Sharing knowledge does not mean sharing every detail with everyone. Communicate information relevant to the team’s work while protecting sensitive information. Check whether knowledge is spreading: team-development and collaboration measures can include whether sharing prevents a single point of failure. Where external partners hold expertise, assign someone to work closely with them so that expertise also develops within the team. section 3.2.3 section 9.2.6 section 9.2.2
