Another place this pops up is documentation for processes in a business -- this could be a process for onboarding or compliance rituals or (hopefully not) deployment. Perhaps a business group has a process that is taught to new individuals who join the group through shadowing or song or dance, it is part of the folklore and rich and vibrant spoken cultural tradition of the group, but has never been written down. Then someone attempts to document it, and the result is confusing.

What if the process documentation isn't confusing and stupid because the author is bad at explaining things - what if the process documentation is stupid because the process is stupid and needs to be changed.

Another approach to this kind of thing is to reverse the sequence of "do it", "document it" steps and draft a rough version of the documentation up-front as part of an initial design, while it is cheaper to change the process or system, before work is done to implement it and roll it out.