This is how I imagine their meetings to discuss this goes:
“Users leave our documentation pages in under 15 seconds! Our documentation is so clear and efficient! For some reason their hardware analytics show that the device falls 20 meters and shuts down afterwards, but that is surely an unrelated event!”
And if they spend a lot of time poring over our documentation, well, that just means our user engagement is through the roof!
So the solution is having the engineers building the service write the documentation right? Wrong. They also don't know what assumptions a real customer makes and how they would use it. Quite likely they too don't understand real external production use.
Writing technical documentation is hard.
So true. Good documentation can make or break a platform. I think a big part of the success of C++ is that Stroustrup is an excellent writer. A lot of the posts I have seen from Linus were also very well written. In the 90s Apple had documentation that seemed written by people who actually knew how to develop software. Nowadays it feels less so.
A bit of humbleness would have gone a long way to them securing a large enterprise contract.