Google Wave was a real-time communication and collaboration platform that attempted to merge email, messaging, and shared documents into a single workspace. It signalled that the established boundaries between communication tools were about to collapse, long before most organisations had finished understanding what that collapse might mean for how teams actually work together.

The preparation was not about adopting Wave itself but recognising that the underlying pressure — demand for real-time, context-rich collaboration — was not going away. Organisations that evaluated the platform missed the more important question: what does it mean when communication, documents, and decisions happen simultaneously rather than sequentially, and who needs to make choices about that now?

Wave required everyone in your network to be on the same platform simultaneously, creating an adoption paradox: it was most useful when everyone used it, but nearly impossible to reach that threshold. This is a recurring challenge with network-dependent tools. The value arrives only after a critical mass commits, and most organisations cannot coordinate that kind of collective commitment without external pressure.

Wave was part of a longer pattern in which major platforms periodically attempt to consolidate fragmented communication. What made it interesting as a signal was that it came from Google. That it still failed illuminates how deeply embedded existing communication habits are, even when a better alternative is demonstrably available. The coordination problem turns out to be harder than the technology problem.

Wave’s failure accelerated a different model. Rather than one unified platform, the next decade brought specialised tools each solving a narrow problem well. The implication was that organisational communication would fragment before it converged, and that integration would become the ongoing strategic challenge, not platform choice. That dynamic is still playing out across every sector today.