Posted on behalf of a friend.
My friend recently had her boss quit. Her boss had been there for 13 years and in that time, had never taken vacation and always did the oncall work. He abruptly quit two weeks ago when they again denied him a raise and has thrown the entire organization into a panic trying to figure out what he even did (as he has a team of 10 developers, but they never touched half the stuff).
He took a Friday off a week ago and three key systems production systems broke that day and required the company to spend a ton of money on an expensive consultant to get them back up (he was not answering his phone and the systems are worth thousands per hour).
One of the consequences of the massive disruption is that the development team is getting lots more money to try and prevent further problems. Money for consultants, raises, and "team building lunches" (as they decided that a lack of social interaction among team members is why nobody knew what the boss did) is flooding in.
The boss is being replaced by someone who openly supports a bus factor of 1-2 for job security. Obviously he doesn't tell management this, but he opposes documenting systems that are currently being built. In addition, he parceled out 2-3 systems per dev to document and told them to keep the document on their local machine (where the boss has access, but nobody else) and not put it on the wiki. He views the mess of the boss departing as a way to keep the department high on the list of company priorities as well as "a canary to tell us if they want to can anyone as they will tell us to document."
My friend thinks that this guy is great for looking out for his employees and as long as the document gets passed to the next person who replaces them, the knowledge base stays fragile as far as management is concerned but for what the boss and 1 team member know.
Are there any potential downsides that you can think of?