For software engineering orgs, I try to push a practice of lightweight effective internal documentation.
Part of my argument sometimes -- to handle objections about job security from keeping info in one's head -- has been that people shouldn't worry about it hurtig job security, because the people who are conscientious about documenting will be recognized as too good of engineers to lose.
But when we're seeing a frenzy of layoffs across the industry (even by companies making huge profits), it's harder to say that job security isn't a concern.
(I'll still push on documentation, because it's important good practice for the team's success, and we're doomed if individuals start thinking they need to hoard the company's knowledge. But I'll have to be thinking of better ways that people's livelihood interests can be covered.)
Do you have any more information on "lightweight effective documentation"? I never seen it work in practice. If there is a method thay has worked for you I would be keen to hear.
Part of my argument sometimes -- to handle objections about job security from keeping info in one's head -- has been that people shouldn't worry about it hurtig job security, because the people who are conscientious about documenting will be recognized as too good of engineers to lose.
But when we're seeing a frenzy of layoffs across the industry (even by companies making huge profits), it's harder to say that job security isn't a concern.
(I'll still push on documentation, because it's important good practice for the team's success, and we're doomed if individuals start thinking they need to hoard the company's knowledge. But I'll have to be thinking of better ways that people's livelihood interests can be covered.)