The "disconnect" rule is an excellent policy for several reasons. In addition to the ones outlined in the post - there is the concept of seeing your own work with "Fresh Eyes". I truly wish I could do this once very six months at least.
I was shocked last year when I came back from a couple of weeks abroad to discover that the very first Architectural decision we had made on a project seemed blatantly off. Turns out it was - no one had considered questioning an implicit assumption - no one (especially me whose job it was) had even caught the assumption.
Saved us at least 3 iterations when we fixed it.
Another good reason is that it ensures the company can function without an individual for a week or two. This will encourage key people to document their work and share information so the company doesn't suffer when they drop off the grid.
I was shocked last year when I came back from a couple of weeks abroad to discover that the very first Architectural decision we had made on a project seemed blatantly off. Turns out it was - no one had considered questioning an implicit assumption - no one (especially me whose job it was) had even caught the assumption. Saved us at least 3 iterations when we fixed it.