December 21, 2005

Delicious Lesson and Social Network Ecosystems

Joshua Porter brings up a wonderful point he is calling the "Delicious Lesson". The Lesson is incredibly important, as it is one thing that many tools and implementations of the social web do not get. The person must get value for their interaction in the service or it will fade.

I see so much focus on the technology, the interaction components, the network effect, etc. But, the driver for these services that are successful is that they have a direct primary value for the person choosing to use them.

A Little Effort for Greater Personal Payback

Jeff Hawkins (the inventor of the Palm device and pen-based writing language (Graffiti) Palm used) talks about the most important point for people to adopt and learn Graffiti was it gave the person value. Jeff points out that learning Graffiti took a little bit of time, but people could see value of learning Graffiti as it made for a quicker input of information. There was personal value that did not take a lot of initial effort to learn, which returned a much greater value.

Social Network Ecosystems

In social networks and personal interaction with web applications and their associated communities there is a ecosystem. The social networks have value chains. I have been playing with this idea for a few months (mostly with in the intersection of the Personal InfoCloud and the Local InfoCloud. I have been using it on some personal projects and it is weaving its way into my consulting practice (but with focus on the full ecosystem and values).

The personal interaction with the system/application/service and value derived is a viable measure, particularly when there are two points of value for the person. The first personal value is derived from the service returning direct value to the person for their interaction. In it is making one&039;s own bookmarks/favorites more easily refindable, the ability to expand one's own bookmarks/favorites beyond the functional restrictions of the browser, and having access to the bookmarks/favorites from any browser anywhere one has web access. The second value is the network value, which can be a feeling of digital philanthropy (doing it out of goodness), personal attention (being an authority, coolness, building points for alphaness, etc.), a driver for monetary reward (recognition increases clicks to an site with ad revenues, builds attention for a business, etc.), etc.

Attention is Value

Attention for those providing development, like in the widget communities for Yahoo! Widgets and Apple Dashboard is very important. In the podcast of the Niall Kennedy and Om Malik interview with Kevin Burton regarding APIs this issue gets brought up (beginning at 15:19 into the podcast). The example discusses Konfabulator (the original product name for Yahoo! Widgets) and Apple Dashboard. Kevin Burton (I believe) states Apple Dashboard has larger exposure than Konfabulator does at the moment and Apple could offer the developers more attention to get more people writing widgets for them. Here the initial value for the developers is attention, as is pointed out in the podcast. The developers are passionate about what they do (personal value in a platform for their expression of their development prowess), but the secondary value received is attention. In a limited pool of developers (not only for widgets, but APIs, and other open development arenas) value to the developer is attention, which can lead to monetary value. This value to the developer is going to be a driver for which service they provide their services (a secondary driver is ease of development). The value to the network is more widgets equal more cool things for the service, but the primary reason the developers are there, is often the value to themselves.


Comments are closed.

This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License.