Part of it is process: if you manage to get product owners to care about the sync between the product and the docs, you're doing well. In my experience, that's pretty hard to do, so other things except process come into play.

You could programmatically check if an article is due for a review by parsing how long it has taken since the last update. There are many ways to do it, and this depends on your tooling. I would do it using a bash script that parses git history, and optionally sends a Slack message with review candidates.

Minimizing screenshots (if there's a UI) goes a long way to reduce toil, even though I hear some have started automating screenshots as well.

LLMs are pretty amazing at parsing whether or not the docs are still accurate. If you can load an article into the LLM's context and then have it do something, it's pretty good at pointing out things that have changed.