Communicating early and often is a great and easy hack:
“In the end, write the docs you want to write. If no one reads them, or if readers find they are out of date, then consider not writing them next time. But don’t let anyone shame you into wasting time. The question is not, “Do you have documentation?” but rather, “Do you communicate clearly?”” (Kent Beck, The Documentation Tradeoff)
“Write documentation” is a tidy but unsubtle maxim. “Tell people what you did” and “help people use your software for the right thing” are better starts. Of late, “invest in written documentation for onboarding humans and agents” is an even better suggestion.
As long as you’re telling people that your thing exists, here’s when you should use it, and here’s how to use it, your documentation bases are covered.