Earlier quoted context omitted.
A way to tackle this further is to use an analytics tool like CodeScene. You link it with your repo and it shows you what people have knowledge across which parts of code[0]. Then you can identify parts that share too few contributors and encourage people to work on them together. You might also find parts where the knowledge is already lost, since everyone who worked on it already left the company. In that case some…
That kind of looks useful, would be nice if it handled Perforce and could be installed on private servers. Don't think the company would want to release all the code publicly.
My client is a bank with private GitHub servers, so I assume their codescene is self hosted as well.
edit: Yep, there is an on-premise option: https://codescene.com/pricing/