If it is usable for communication with e.g. website visitors also depends somehow on your type of visitors. Just providing information is also possible with a simple website, but two-way communication gets much easier with Wave. Getting non-tech oriented people to switch to Wave might be difficult – it took me years to explain my parents how to use email . On the other hand, it seems that Wave is provides a great user interface – so this may not be that much of a problem after all.

In the short term it will more extend (than replace) the current technologies (just like the Internet didn’t replace the telephone (yet)). If people like it they will switch and use it, but as with every technology it is hard to tell in advance.

bless./love.

For the internal communication I mainly see it as a replacement for email and mailinglists and maybe even wikis. So all this “old stuff” that you previously used to communicate could be replaced by Google Wave. Nice thing is that you can use a Wave for multiple things – e.g. first the Wave starts out as a simple message to others, and then these others can modify the original message in a Wiki style.

For the external communication (e.g. to website users, etc.) I see Google Wave as some kind of replacement/enhancement for Twitter and even your website. So people can e.g. subscribe to a Wave that you use to regularly post your ministry’s schedule. But as Wave allows for two-way communication these people can also provide feedback.

Most of the techniques used by Google Wave have already been available in the past. But the cool thing is the integration of different techniques. You do not need 10 different services anymore, but you have one service that provides all – and that can even be extended by third party developers to provide additional functionality.