There are teams that do work, and there are teams that don't do work. It's no coincidence that most documents exclusively benefit the latter.

Ironically, the documents that would actually help people doing work are often missing and/or incomplete and there's never budget to write them properly - up-to-date descriptions of processes, product manuals, API references beyond what's automatically generated, troubleshooting guides for common problems, onboarding materials, and so on. But somehow we have dedicated people to write detailed five year plans that never get completed and such. I can't help but wonder if ease of writing rather than usefulness is the core determinant of what gets written.