At Google my team wrote a post for the Google Cloud blog about our product. This article is painfully true, in particular "Non-engineering approvals suggest cha

At Google my team wrote a post for the Google Cloud blog about our product. This article is painfully true, in particular "Non-engineering approvals suggest changes authors find frustrating". My coworker wrote an initial draft and the rest of the team left some minor suggestions. Then we waited for weeks to get approvals from multiple people, mostly non-engineers, one of whom was at the company for whole of three weeks. Had to make several changes we didn't like but had no choice. After addressing all their (at best, non-consequential) feedback we had to wait another few weeks to hear back again. This time one person who initially required we change X to Y was apparently replaced with another review, who insisted we absolutely have to replace Y with X. In the end it got published, but was so heavily butchered it is a very bland and uninteresting post. As a silver lining, we ended up writing a technical paper about the product later and that was much better experience, reviews came from internal researchers and domain experts. (throwaway so I don't add too many bits of identifiable info to main pseudoanonymous account)