This is one of those instances of pure non-sense that I hope will drive rich discussion.
The whole notion of forcing users to change their behavior by placing obstacles in their way is futile in my experience. It's a grave misunderstanding of who users are and how to design for them.
Forcing users to do what you want them to is how you get desire paths [1]
I worked at a company that tried something similar.
The result was that individual teams set up their own off-the-record private Slack workspaces or Discords so they could regain some control over their conversation history. Obviously not great from a company information security perspective, but many managers looked the other way because they just wanted to get their work done without worrying about conversation history arbitrarily disappearing.
The idea that you can force people to produce better documentation by making their lives more difficult never really works out.
Also as the sibling comment is saying, you won't change the culture of an organization only by an UX change or a software change, that can help, but that won't be enough
This would push people away from a wiki.
Unfortunately once you update the wiki, it also grows stale after that moment, so in someways intractable :)
The fact that I have never been able to get buy-in for this proposal would argue that our docs may actually be good enough.
That's not the use case the blog post is addressing. It shouldn't be considered a mark against anyone if when applying their advice in a way that they never advocated then it turns out not to hold up so well.
What else do you see causing the problem aside from culture? Are there tools that do this well?
You are restating the problem, the question is how
The idea is a very bad idea. Imagine if wikipedia would do that, what will happen. Fortunately they don't and they found other way to fix the problem.
The issue here is: part of the documentation is not up to date anymore
The underlying issue is : the culture of the company probably doesn't encourage written documentation and probably prefer 1-1 communication. As a result documentation is out of date
The right solution is: Dont share documentation in 1-1, always write it on the wiki, and give the ability to people to notify that some part of the page is out of date so that the owner of the document can fix it
This is not a side issue, especially in the "new" world in which a lot of organizations need to work remotely