The linked article spells out exactly what project it was about:

> Take AWS. It reached $10 billion in revenue in less than four years. But what's remarkable is that they didn't get there by forming a team, writing a lot of code, and then testing and iterating. In fact, it took more than 18 months before the engineers actually started to write code. Instead, they spent that time thinking deeply about the customers they were trying to serve and forming a clear vision for what AWS should be

Yeah, unless they mean some other Amazon than the one that believes in "2 > 0" in product portfolio management and that "communication between teams is terrible!" (a quote attributed to Jeff Bezos).

Granted I don't know the context of the given quote, but I definitely agree with at least one interpretation of it. If you need communication and synchronization between teams to achieve your goal, there's a lot more room for missing memos, misunderstanding etc. In that sense indeed, communication between teams is terrible in the sense that it adds extra drag to the whole process. Of course, there's ways to spin this quote in a number of other ways too, which is why I think the quote without any additional context doesn't really illustrate any one point.