Must read: Thoughts on the Emerging Collaboration Economy


Image by yuan2003 via Flickr

Found at (through Graham Hill)

The Emerging Collaboration Economy

Hub Culture founder Stan Stalnaker shares his thoughts in a Q&A with Rachel Botsman on sharing, the power of the commons, and peer-to-peer transaction.

Rachel Botsman is co-authoring a book with Roo Rogers entitled What’s Mine is Yours: The Rise of Collaborative Consumption (being published by Harper Collins in 2010).

The book is about how people are collaborating together through organized sharing, bartering, trading, renting, swapping and collectives to get the same pleasures of ownership with reduced personal cost and burden — and lower environmental impact.

RB: We look at how look how social networks and web technologies are giving new relevance to pre-industrial behaviors such as bartering, swapping, trading, social lending etc. that require marketplace structures. Essentially how we are going back to ‘human to human transactions’ between producer and consumer, seller and buyer, borrower and lender, neighbor to neighbor etc.  What are your thoughts on this? What are your favorite examples of this in action?

To be continued at

Reblog this post [with Zemanta]

Reading “Why Google Wave Sucks, And Why You Will Use It Anyway”

Found at

This guest post was written by Martin Seibert, a German Internet media consultant.

Google Wave is a hot topic at the moment. The ambitious group collaboration and micro-messaging platform started rolling out in beta via an initial batch of 100,000 invitations two months ago. Many people still want invitations. Among those who’ve tried it, some criticize it, some praise it. For now it has a lot of usability problems that are described below. Yes, you should look at Google Wave. But there is no need to desperately long for an invitation yet.

Nevertheless, this post outlines how you’ll probably use Google Wave in the future and also gives you advice on how to implement it in your company or your team of coworkers. It also reveals some big usability problems in the current version. Those issues aside, I would like to show you the advantages of the “wave” once again and describe some cool use cases that might make you love it at some point in the future.

Introduction to Google Wave

To be continued at

Reblog this post [with Zemanta]

What is Google Wave

What is google wave and is it better than email? We attempt to answer this questions with the hopes of getting an invitation because we were not lucky enough. Created by

Source: Mashable

Reblog this post [with Zemanta]

Enterprise 2.0 in 2010: Twitter / SharePoint / Google Wave / Facebook Tailwinds Fuel Growth « IronGiving

Found at

ep2023 Thx to Geek and Poke for the image above.

The term “Enterprise 2.0” was coined back in April 2006 when Andrew MacAfee wrote this Sloan Management Review Article.  Since, then MacAfee has become almost synonymous with the term Enterprise 2.0 and is even coming out with a new book on the topic to be published in late November 2009.  His blog is one of the most respected on the topic of Enterprise 2.0 and he tweets regularly.  I took Andrew’s very first graduate school class he taught in a class called Technology, Operations and Research back at HBS Spring of 2000 and I always thought he had a knack for sensing early technology trends.

One of my favorite posts of his includes his response to a ZDNet post that states  Enterprise 2.0 is a crock.   I like it as it paints six specific use cases around real world examples of well known companies using various facets of enterprise 2.0 to solve customer pain points.

Another favorite of mine is this post where he describes ten criteria for a successful enterprise 2.0 initiative.  This strikes me as a practical and useful framework for how and why some companies are succeeding with enterprise 2.0 solutions.

I mention all of this as I intend to cover some trends on this category in my blog here because I’m a real believer in the disruptive potential enterprise 2.0…..


Reblog this post [with Zemanta]

Checking out Microgeist’s the Future of 4G, Twitter and Google Wave

Or will all these divergent communication channels converge to 1 conversational wave?

Found at

9 September 2009

Like any new technological development, 4G is a lot closer than you think. Tests are already underway and some battle lines are being drawn with regards to how the market for these services will emerge. This development is on track to coincide with the equally rapid development of real time systems like Twitter and Google Wave. What is likely to emerge are services that create instantaneous streams to deliver and share not just text and hyperlinks, but video, audio, whiteboarding and files. This will be:
a) Faster
b) From a static or mobile device
c) With more reliable synchronization via the cloud
d) Easily archivable and searchable

Even more exciting is the continued evolution in hardware and always on devices. Taking the iPhone as an example, it’s gyroscope has redefined gaming and sent the experience into a much more physical dimension. The Wii is another case, even being used as part of physical therapy regimens.

The near future will bring devices that rapidly stream real time data that can be manipulated physically via mobile devices around the world. This data will be searchable and archivable via the cloud. Data will also be semantically organized and re-configurable into other views that reveal insights for business owners and managers.

With all of the possiblilities that this brings, planning for the roll out of these technologies requires a broad knowledge of what will become available, but it also requires significant focus because, taking Twitter as an example, the most compelling applications often use a subset of what is available. Technologically, Twitter is not particularly complex, but it has met a human need.

4G will provide the playing field for the next Twitter or Facebook, provided that a developers and entrepeneurs are able to ask the right questions and stay focused on meeting human needs, rather than geeking out.

This video presentation from iPass breaks down the current technologies and state of development in 4G. More importantly, is poses the questions that need to be asked by anyone who will be taking part in that space. It is important to remember that 4G, beyond being a mobile technology, will be a convergence of technologies. Desktop, remote, mobile, and new interfaces will continue to make it impossible to focus on one single type of device for anyone anyone hoping to compete in the next several years.

Read more

Reblog this post [with Zemanta]

Hyped or hoped: the enterprise implications of Google Wave (original post from Dion Hinchcliffe)

Lars Rasmussen introduces Google Wave
Image by dailylifeofmojo via Flickr

After reading about Google Wave I applied to become a tester of the application later this year.

Between dreams and actions there are challenges, was my motto on the application form.

If indeed collaboration and communication will change in the forthcoming years, one needs a generally accepted tool.

May be this becomes Google Wave. Nice to reflect how the Google Wave is acting on the departure of document oriented communciation and is heading for real time communication.I

Source: Posted by Dion Hinchcliffe @ 3:21 pm 2009/5/31

Google has launched many communication services since its inception yet none of these have had such obvious business utility or attempted to reinvent the collaborative process from the ground-up.

Google announced their forthcoming service known as Wave this week to widespread coverage in both the press and blogosphere.

Created by many of the same team members that developed the highly successful Google Maps, the preview of the service itself on Thursday was quite compelling, resulting in a rare standing ovation at a tech conference according to ZDNet’s own Sam Diaz.

Its egalitarian and federation-friendly design is intended to create an entire open ecosystem for communication and collaboration that Google is not-so-modestly touting as the reinvention of digital interaction circa 2009.

This is clearly a tall order, but the Internet leader provides plenty of substance to back up this vision despite growing evidence that individual companies may be losing the capacity to drive the agenda for the world when it comes to establishing successful new Internet standards and technologies.

While the ultimate destiny of Wave itself is far from clear, it’s both intriguing and open enough that it will likely emerge on the radar of businesses large and small when it becomes widely available later in the year.

Google Wave

Wave’s relevance to the enterprise might seem premature with so many of the early and current Web 2.0 applications (blogs, wikis, social networks, Twitter-style social messaging, mashups, etc.) still — often arduously — making their way into the workplace years after their inception.

Though we seem to finally be hitting a tipping point with 2.0 tools at work, Wave itself seems credible enough to get on our watchlists, at least to understand the implications.

The real question is whether there are really such significant gaps in the current state of Web-based communication that we need something new like Wave. With Google’s tendency to emphasize the consumer world first and the enterprise later, it’s also valid to ask if Wave will really have much impact on businesses.

Interestingly, you might be surprised at some of the answers, so let’s take a look.

Wave: A communication and collaboration mashup

Google Wave itself consists of a dynamic mix of conversation models and highly interactive document creation via the browser. Using simple, open Web technologies (Google makes much of the fact that most of Google Wave is a open set of formats and architectures that is jointly developed with the Web community) Wave combines many of the key features of e-mail, instant messaging, media sharing, and social networking into a seamless experience and data set that are eponymously known as waves. All of this is opened up to developers via the Google Wave API.

The demonstration at the introduction of Google Wave (link below) showed how users can interact in real-time, collaboratively creating structured conversations that contain rich media, instant notifications, simultaneous user editing of the conversation, and live integration with server-side resources such as spell-checking and language translation.

Most interestingly, while waves are relatively self-contained and use their own types of servers and data formats, they are easy to embed elsewhere or to build extensions for, enabling virtually infinite options for distribution over the Web or within the firewall, as well as rapid integration with existing applications and data. In fact, a wave is almost a form of social glue between people and the information they care about. And as we’ll see, this has implications for the enterprise world, not only with SOA but also with social communication in general as well as Enterprise 2.0 specifically.

See Waves in action: Watch the introduction keynote at Google I/O on Thursday.

What Google has done with the Wave protocol is essentially create a new kind of social media format that is distinctively different from blogs, wikis, activity streams, RSS, or most familiar online communication models except possibly IM. Both blogs and wikis were created in the era of page-oriented Web applications and haven’t changed much since.

In contrast, Google Wave is designed for real-time participation and editing of shared conversations and documents and is more akin to the simultaneous multiuser experience of Google Docs than with traditional blogs and wiki editing.

Though Google is sometimes criticized for missing the social aspect of the Web, that is patently not the case with waves, which are fundamentally social in nature. Participants can be added in real-time, new conversations forked off (via private replies), social media sharing is assumed to be the norm, and connection with a user’s contextual server-side data is also a core feature including location, search, and more.

The result is stored in a persistent document known as a wave, access to which can be embedded anywhere that HTML can be embedded, whether that’s a Web page or an enterprise portal. Users can then discover and interact with the wave, joining the conversation, adding more information, etc.

Google has also leveraged its investments in Google Gadgets and OpenSocial, two key technologies for spreading online services beyond the original boundaries of the sites they came from.

All in all, Google Wave is a smart and well-constructed bundle of collaborative capabilities with many of the modern sensibilities we’ve come to expect in the Web 2.0 era including an acutely social nature, rapid interaction, and community-based technology.

As the original announcement post explained, to fully understand Google Wave, one should appreciate the separation of concerns between the product Google is offering and the protocols and technologies behind it, which are open to the Web community:

Google Wave has three layers: the product, the platform, and the protocol:

  • The Google Wave product (available as a developer preview) is the web application people will use to access and edit waves. It’s an HTML 5 app, built on Google Web Toolkit. It includes a rich text editor and other functions like desktop drag-and-drop (which, for example, lets you drag a set of photos right into a wave).
  • Google Wave can also be considered a platform with a rich set of open APIs that allow developers to embed waves in other web services, and to build new extensions that work inside waves.
  • The Google Wave protocol is the underlying format for storing and the means of sharing waves, and includes the “live” concurrency control, which allows edits to be reflected instantly across users and services. The protocol is designed for open federation, such that anyone’s Wave services can interoperate with each other and with the Google Wave service. To encourage adoption of the protocol, we intend to open source the code behind Google Wave.

The key here is that Google is expecting many more front-ends for creating and editing waves, depending on the individual requirements of various entities. Google Wave is their own front-end application for doing so and using HTML 5 in their wave client shows they are planning more for the future than present.

An enterprise perspective of Google Wave

But Google’s point is well taken: The hodge podge of 1990s era (and often older, in the case of e-mail) Internet communication methods were created in another time.

Blogs, wikis, IM, and so on are all useful modes of communication but there are better ways and new requirements in today’s high social, interactive, and highly integrated times.

That’s not to say that many companies haven’t tried to do this already, but virtually none of them have the ability to drive the modern development community or use their existing online market share to foster adoption in the end-user marketplace like Google does. In the end, barring a major misstep from Google, chances are good that organizations will have to deal with business data in the Wave Protocol format in the future.

Using Google Wave in the Enterprise

Let’s take a closer look at what enterprises need to know about Google Wave:

  • Google Wave largely complements and doesn’t replace existing communication and collaborative applications. Google Wave creates a healthy synthesis of existing application types by providing integration across existing channels. The early demos in fact showed how Twitter and existing social networks can play very well with Google Wave, enhancing the experience and allow broader participation. Google Wave won’t replace existing apps like e-mail, IM, blogs, or wikis, and will actually make the latter two stronger through embedding. Groupware and other simultaneously collaborative apps, however, are more at risk of displacement.
  • Enterprise 2.0 is well supported by Google Wave. The general capabilities of FLATNESSES, my mnemonic for all the things that a capable Enterprise 2.0 platform should do, is well embodied in Google Wave. While blogs and wikis are the fundamental Enterprise 2.0 platforms, the basic capabilities of social interaction, emergence, and freeformedness are all there, though a wave presupposes a bit more structure and situated use than the more tabula rasa blog or wiki.
  • New protocols, servers, data formats, and client applications are required to use wave. Unfortunately, Google Wave brings a lot of baggage with it, though it’s mostly straightforward. You will require new software, though not on the client since that all runs in a zero-footprint browser client. This means more integration code, management, and monitoring. The best news is that everything is well-documented, open, and any organization can participate in directing the wave community, so lock-in, while always possible, seems largely avoidable and Google takes great pains to draw us to that conclusion. Google is also pushing hard for alternative implementations of the client and server components, including on-premise implementations, with the former on display at their announcement.
  • Waves are a natural integration point for many enterprise services including ECM, SOA, mashups, and more. By defining a strong protocol for continuous server-side processing of live conversations, Google has enabled an entire world where our IT systems are connected to the work we do every day. Literally while participants are busy typing and collaborating, a wave can be receiving support from back-end systems such as HRM, CRM, ERP, and so on to provide data, context, and other just-in-time support. Many businesses could benefit enormously from seamless business data integration such as customers, orders, and so on, never mind the deeper possibilities of contextual business processes leveraged directly in the collaborative activities of workers. I’ve written many times about the convergence of our IT systems and Web 2.0, and this seams one of the more natural environments for it that I’ve seen in a while.
  • Embedding and extensions will enable widespread distribution and consumption of waves. Google brings ease-of-development for creating server-side extension as well as simple models for user-distribution of waves. While the first will enable easy integration with local data sources and will create a large aftermarket for useful extensions such as the aforementioned language translation capabilities, the second will virtually ensure that enterprises will have interaction with waves one way or another. Since the premise of the product is also one of the dominant activities in the business world (enabling teamwork) and combined with the increasing consumerization of the workplace, it’s highly likely that organizations will encounter waves in their work with external entities, especially with partners and clients. At the very least, organizations will need to understand how waves will make their organizations even more porous on the Internet, and have policies about participating in them, just like SaaS services, social networks, and other external applications. Security will also be an issue with waves though things like integration of Web 2.0 tools and ECM will actually be easier than ever before since a corporate archive robot could ensure every wave conversation is backed up in the formal ECM system.

Google has launched many communication services since its inception including Gmail, Gtalk, Blogger to name just three, yet none of these have had such obvious business utility or attempted to reinvent the collaborative process from the ground-up.

While it’s always possible that Google Wave will never broadly take off (see Mary Jo Foley’s analysis of Wave here), I’m betting that it’s likely to be one of the most interesting offerings to businesses that the company has created yet. With the open positioning, early outreach to the world, and the clarity of purpose and design, Google Wave has a good shot at helping take Enterprise 2.0 to the next level in many organizations.

It’s much too soon to really decide anything about Google Wave yet, but are you putting it on your watch list?

Dion HinchcliffeA veteran of software development, Dion Hinchcliffe has been working for two decades with leading-edge methods to accelerate project schedules and raise the bar for software quality. See his full profile and disclosure of his industry affiliations.

Reblog this post [with Zemanta]