People have some legitimate concerns about Google Wave, myself included. Google posted a wave asking what people like about Wave, and what they don’t like.
It appears they’re taking the gripes pretty seriously.
My personal gripes:
- It’s not a truly federated system
- What good is collaboration software if you have no one with whom to collaborate?
- Any app, native or web, running it uses tons of resources and is a little slow.
Here’s what Google says regarding poll regards:
With these responses and other data, we’re organizing our team around the core issues that are important to making waving better. We’re working hard to scale our systems so you can invite your friends and colleagues to wave with you. We’re also thinking about how to integrate with existing communication and collaboration tools. And since we all know that fast is better than slow, a large portion of the team is working to make Google Wave faster.
Let us know how we’re going with these things and if you are waving feel free to take the survey again and again — we’re interested in seeing how people use Google Wave differently over time. We’ll start writing about what people are actually doing with waves, so let us know about interesting things you’ve tried.
Happy waving!
Posted by Aaron Cheang, User Experience Researcher, Google Wave
Got a gripe with Wave? Let’s hear it in the comments…
link: Punch a Duck: Wave pool… I mean poll…
{ 2 comments }
I think the 2nd point here is the biggest issue. If there is nobody on the platform it is never really going to be that useful. I am a massive techie myself and we use all these tools to promote our clients but there is enough going on without having to learn a new technology. Am sure Google Wave will be massive one day but what is the point in us all investing time in something that will be big, wait for it to have the communtyy and users and then I’ll be there
I think this is very interesting.
In my particular situation, every member of my core dev team is on Wave, and we are gradually getting more people from other teams onboard. So, for us, the time is already here. If not for our already investing time in experimenting with Wave, we probably wouldn’t be trying to get our partners on the platform.
We currently use Wave, primarily, for recording meeting agendas. During the meeting, people take one agenda item of discussion and put it in a new “blip.” Others comment on it, and then we all record action items in the Wave.
This not only serves as a recording of meeting minutes, but as a source of accountability. If you say you’re going to do something, it’s written in the wave, in plain sight, and you’d better either a) do it, or b) explain why you chose not to do it.
Comments on this entry are closed.