4 ms·
Losing institutional knowledge is a b*tch. It costs more to get new people up to speed in terms of time and productivity lost, than to just retain people who al
by unity1001 4y ago
Losing institutional knowledge is a b*tch. It costs more to get new people up to speed in terms of time and productivity lost, than to just retain people who already have the institutional knowledge.
- bonestamp2 4y agoYes. We used to work in silos. Dave was responsible for x, Cathy for y. When Cathy left, we were screwed because nobody knew much about y. So now that I'm the project manager, after Steve builds the new feature then I alternate assigning the bug fixes between two other people who did not build it. That way, at least two other people become familiar with that part of the application while Steve is still around to answer questions and provide guidance.