In Web 2.0 Software, Adoption Trumps Functionality

The last several years have seen the greater adoption of social media and other Web 2.0 software components. These component software tools provide users with a more interactive experience, personalization, with the ability to create their own content, links, tags, navigation, etc. Additionally, you are seeing the growth of the “connected web”; web services, RSS, embeddable code, ubiquitous meta-tagging, widgets, consumable data, etc.

The proliferation of these software applications has migrated to every sector; consumer, enterprise, SMB, etc. What used to take NDA’s, sharing and modification of API’s, and endless meetings now can be accomplished with a snippet of code.

As the web transitions to more semantic driven applications and less user-interface driven, you would think that functionality would become increasingly important in applications.

In my experience, the trend is towards the opposite and that ADOPTION trumps functionality. The challenge is that we have too many options on the internet; too much data, content, search results, websites, applications, etc. The word I hear over and over is “overwhelming”.

So, if you have a very limited window of attention from your audience, why would you throw extraneous “stuff” at them hoping something would stick. Instead, take advantage of the Web 2.0 technologies and provide them with a tailored experience with just-enough functionality.

More importantly, focus on what is their motivation and interests. Not all potential buyers are the same. Don’t provide a generic website experience that meets 80% of 80% of the visitors and satisfies none. Instead, focus on identifying what a 100% of a smaller audience that you know will buy and add additonal functionality to support additional segments over time. Customers provide unsolicited referrals when you exceed their expectations and provide them a WOW! experience. This is the heart of word-of-mouth marketing. EXCEED CUSTOMER EXPECTATIONS!

If you cannot exceeed the whole group, then focus on a small enough group that talks to each other and build from there. You see countless blogs and articles about how to launch products on the interet. This is the reasoning behind the axioms. You need a critical mass of associated happy customers that will tell others about it.

It is about numbers. If you satisfy 1% of a large group, that doesn’t make much of a market impact. If you satisfy 80% of a small group, you own the market. Bottom line, adoption of your solution is more critical than providing everything, including the kitchen sink.

Of course, the secret is prioritizing the “right” functionality to satisfy the customer which takes someone asking them….


1 comment so far

  1. […] – in a previous post, I discussed why adoption trumps functionality in Web 2.0 applications Bottom line is that without users, web 2.0 collaboration cannot occur. You can look at the […]

Comments are closed.

%d bloggers like this: