It’s a great approach to create an anti-fragile team.
From the experience, I know how hard it’s in practice. There is a strict deadline, management interferes and asks to assign the star player to the project to be on time. Company priorities overweight the importance of knowledge distribution.
But that’s life. Even if these rules can be implemented 70% of time, it’s already a win.
One more additional technique I employ to flesh out info is to religiously do teams recordibg of various reviews, architectural , reverse knowledge transition of recently on boarded team mates, prototype walk throughs etc.
These videos can easily be digitized and stored for future easy reference by anyone.
Ps. This task can be easily accomplishable using ai tools.
We are considering implementing a RAG-based search system that will index these across the org and make this information publicly available. We have a couple of candidates, but we haven’t tried it yet.
It’s a great approach to create an anti-fragile team.
From the experience, I know how hard it’s in practice. There is a strict deadline, management interferes and asks to assign the star player to the project to be on time. Company priorities overweight the importance of knowledge distribution.
But that’s life. Even if these rules can be implemented 70% of time, it’s already a win.
Yes, the reality is that we cannot stop doing what we are doing. But small steps compound quickly. It is just important to keep going.
One more additional technique I employ to flesh out info is to religiously do teams recordibg of various reviews, architectural , reverse knowledge transition of recently on boarded team mates, prototype walk throughs etc.
These videos can easily be digitized and stored for future easy reference by anyone.
Ps. This task can be easily accomplishable using ai tools.
We are considering implementing a RAG-based search system that will index these across the org and make this information publicly available. We have a couple of candidates, but we haven’t tried it yet.