Very practical article as it leaves readers with many actionable items. Thank you for taking the time to write it.

It left me with the curiosity to hear more about how your team engrains in the development process, especially within the context of the guiding principle no.6. That is, how you collaborate with stakeholders and how documentation updates are brought up and triggered during a development cycle/sprint. Probably an idea for another great article ;)

I find the "Discussions" section very eye-opening, but I'm also wondering whether you already know how to prevent discussions from disappearing when content is updated: If the common flow to create a discussion is to first highlight a piece of content, what would happen to the discussion if the paragraph where the highlighted content is is updated? Just thinking that some discussions may hold their value even after the content becomes outdated... Would love to hear your thoughts on that!

Once again, thanks for this very inspiring article!