Just like we do code reviews, even internal documentation should be reviewed. Possibly not to the point of requiring review prior to publishing but certainly soliciting feedback and improving the docs to meet an adopted Page Style Guide.
Feedback allows us to accelerate our rate of growth or improvement. Unsolicited feedback, often unwelcome elsewhere, is like gold for anyone writing content.
Strategies for ensuring documentation review happens:
- curators take initiative to monitor all published documentation
- authors request reviews
- leverage CODEOWNERS within GitHub or other source control systems via Pull Requests
- include documentation review as part of your Definition of Done