What is atomisation (Web 2.0)?
I like the term atomisation as a way of summarising a significant trend in Web 2.0. This post explains my take on the atomisation concept with examples.
For me, atomisation (Atomization) is a Web 2.0 concept where the content on a site is broken down into smaller fundamental units which can then be distributed via the web through links to other sites.
Atomisation traditionally means fine particles of powder or liquid, but I like the idea that the content on a website can be broken down into smaller components and then can be released onto the web where they can be aggregated together with other content to provide content and services valuable for other site owners and visitors.
Any type of content that makes up a site can potentially be "atomized", so news stories or features in different categories or information on new product releases are all examples of atomized content which can be syndicated to other sources.
This concept of syndicated content is certainly not new on the web or traditional concept, but the reason I like the atomisation concept is that site owners need to think more beyond their own sites and how they can "sweat their content assets" by making them available to other sites.
The creation of widgets and gadgets for use on third party sites and the distribution of content via syndicated RSS feeds are the best examples of atomization.
As my post on widgets explains, the benefits of widgets are similar to online display advertising, i.e.
- increase reach through third-party sites
- relatively low cost exposure making use of existing assets
- engage visitors with brand - particularly useful for products which are launched which require an increase in awareness.
- can assist with Search Engine Optimisation through links back to site.
- encourages links back to sites.
The small units of content contributed by participants within a social network can also be considered atomization.
What atomisation means for site owners
Site owners need to think through how they can:
One. Provide content RSS feeds in different categories through their CMS. The BBC has done this well for years with their feeds effectively providing tens of thousands of newsletters or their site at the level of detail or granularity to support the interest of their readers, e.g. separate feeds on:
- Sport
- Football
- Premier League football
- Individual team
Two. Separate out content which should be provided as a data feeds of new stories or statistics into widgets on other sites. Example - the recently launched UK retail statistics widget dasbhoard for iGoogle
Three. Develop web services which update widgets with data from their databases. A classic example is the justgiving widget where Money raised by a donor is regularly updated.
Four. Create badges which can be incorporated within blogs by their fans or advocates. The membership body, CIPD does this well through their link to us programme
Five. Whether widgets or feeds from other companies can be included within their content to provide value for their users
What do you think - do we need the atomisation concept - there is very little substantial about it on the web - just passing comments on blogs - hence the reason for this blog.
Do you have any more examples - please add what you think or examples below.
Please bookmark this article if you found it useful (just two clicks).
Please add your comments, experiences or link suggestions to inform me and other visitors to my site.
I've set it up to be quick, but you can't add true hyperlinks - just text.
Thanks, Dave Chaffey.
Atomisation
widgets
Thanks for the widget namecheck! We've been really pleased with the take up and reaction to our widget, and it's become one of the most popular referrers to our site. I couldn't agree more with you on the atomisation front - RSS is already a great tool and we're looking to use it even more in the future of our site.
Jonathan Waddingham
Client Support Manager, Justgiving.com
http://justgiving.typepad.com/charities/
Atomisation
Linus Gregoriadis, E-consultancy
Back to reclaim Atomisation...:)
Only to find that Dave has hijacked my buzzword on Google... ;)
Yes, Atomisation was my speaking theme for 2007. Not least because I had an expensive animation done so I had to show it a load of times to get the cost-per-presentation down to an acceptable level.
I haven't figured out a new theme for 2008 (social media, mobile, rich media - all too obvious) and I reckon "atomisation" still has legs.
I'm refining my atomisation toolkit a bit. There's atomisation of:
1. Identity - OpenID, Google Social, Facebook MoreFriends apps etc.
2. Content - microformats are most interesting (and, of course, there's RSS, XML etc.)
3. Functionality - most obviously APIs + widgets/gadgets/badges etc.
4. Preferences / Behaviour - e.g. APML (http://www.apml.org/), now that's interesting stuff...
Watch this space...
Ashley

Delivering customer value via the atomised web
My feeling is that the atomisation of the web is one of the most important issues that marketers need to get to grips with.
The latest Online Customer Engagement Survey (you can register for a free copy here http://tinyurl.com/28onxs) indicated that companies are really starting to recognise the importance of the customers distributed and atomised experience.
Almost 40% of companies indicated that they were going to be investing in developing web-based widgets, gadgets and badges. While 35% were going to develop similar for the desktop.
Our ability to deliver content and value to our customers when and where our customers are is central to the next generation web. The days when you could reliably and cheaply drive customer upon customer into your siloed website are gone.
It is possible to use widgets and gadgets etc. to reach out and ‘grab’ customers but the real benefit to be derived from them exists in being able to deliver content, and functionality, to the customer in a context that they are familiar and happy with. Of course this raises the questions of how do you achieve conversions and how do you measure within this distributed user experience? Something for another for another article I’d suggest.
Richard Sedley, Director cScape Customer Engagement Unit
WEBSITE: www.cscape.com
BLOG: www.loopstatic.com