Documentation is typically seen as the savior - the hero that can morph the cloudy skies of confusion into clear blue skies of value. But documentation should be seen as the enemy it truly is - the villain that allows you to build a product that can do 'all the things', while nobody can figure out how to do any of them.
It doesn't have to be that way. But to change, you need to focus on building a user experience that your users can... you know... use ... and in a self-explanatory manner that doesn't require them to read a novel every time they want to 'just do this one simple thing'.
Collection
[
|
...
]