3 ms·
Opposite opinion. You should never need more then a day to knowledge transfer. If that. I always try and cross train people enough that I can quit at any po
by treeman79 6y ago
Opposite opinion. You should never need more then a day to knowledge transfer. If that.
I always try and cross train people enough that I can quit at any point and it’s not an issue.
All processes are kept automatic where no one is crucial to keep it running.
Mostly it’s useful for vacations.
In the past I went on a cruise. And I wasn’t sure the company will be online without me to baby them through.
After that I got extremely serious about investing in the team and tools to never let that happen again.
- nitrogen 6y agoI agree with making things automatic. But sometimes you have to let team members specialize. It's less efficient for everyone to know everything. But, it is good if everything is known, at least in part, by at least two people.
- aaronblohowiak 6y agoWhen I was managing the goal for the team was to have at least two people know each thing, but avoid too much overlap between any two people. This is like some form of erasure encoding :)
- treeman79 6y agoA Company got down from 20 to 3 people. Completely different tech stack each. Many warnings that company was in major trouble if any of left. Other 2 had no way to support. Oh It was so painful when it happened.
- atwebb 6y agoThen you've mitigated the bus factor, this thread is about that being uncommon or not fully supported in other places. Part of the mitigation discussion here is a tech stack that is transferable.