Some implementations are only as good as their documentation. One of the earliest things I implemented when I joined UC Davis was the push to have good release notes; good in terms of being both detailed and user-friendly, which means being able to explain what we are exactly releasing but without losing the customer in technical jargon.
Some examples of release notes that I created:
Shout out to Tobi Paton for being my go-to proof reader for these release notes.