The Assembled Web: Notes Toward a Manifesto

In the spirit of (and heavily inspired by) the original Cluetrain Manifesto and the recent 10th anniversary edition, I offer the following definition and 10 principles of what we at Optaros have been calling the Assembled Web.

The Assembled Web is not experienced as a set of discrete web applications and sites, neatly separated from each other and organized into categories: it’s an indiscriminate field of content, functionality, and people interacting in multiple contexts and in unpredictable ways: like life.

New web applications are assembled from other projects/applications/frameworks/services, sometimes on the server, sometimes in the browser, sometimes in the cloud. People’s accounts, identities, and networks come with them across sites, applications, and contexts.

How should enterprises not only come to grips with this bewildering confusion but thrive in it?

By embracing the assembled web and participating fully in it.

Assembled Web First Principles:

1. You should always be thinking multi-site, multi-interface, multi-project. If you think you will (always) only have one interface to any given set of content of functionality, you’re mistaken, and you will paint yourself into a corner.
   
   
2. Success on the web is no longer (if it ever really was) about driving traffic to your site, or keeping eyeballs there once they arrive. It’s about engaging audiences everywhere they already are. It’s about improving the size, quality, and velocity of your “digital footprint.” Ubiquity is the target, not exclusivity. The danger is not that people will say bad things about you but that you will be ignored.
   
   
3. Your brand is not what you say it is, but what your prospects, customers, partners, and employees say it is. In short, your brand is what the Internet says it is. You influence this not through marketing but through creating appropriate experiences and getting users exposed to those positive experiences. (Micro-interactions are ultimately assembled into and become brands).
   
   
4. Design is critical, and design is not about pretty shiny objects. It’s about usable interfaces, in the sense of traditional HCI (Human Computer Interface) design, visual design, and technical design. Creating usable experiences for users and usable projects for developers are both essential, and to ignore either is to invite failure.
   
   
5. The internet itself, like the *nix operating systems on which it (almost entirely) runs, is a set of small pieces loosely joined. Every project you do must be composed of smaller discrete components communicating with each other. The corollary is that every project you do must also be composeable or consumable by other projects – including projects you know nothing about. This is true across multiple projects (within your organization and outside it) as well as over time within a given project.
   
   
6. The difference between “behind the firewall” and “out in the cloud” is trending toward zero. Same for the difference between employees and contractors, customers and prospects, competitors and partners. If you’re still thinking in terms of intranet, internet, and extranet, remember that the difference between them is (from a technology point of view) entirely arbitrary. What differentiates them is business processes and decisions.
   
   
7. There is no defensible reason to invent a proprietary standard wherever an open standard exists. In fact, even where no open standard exists, great efforts should be extended to create one, rather than implement a proprietary version.
   
   
8. Working in isolation from the rest of the internet is inherently limiting and dangerous. This is true whether you’re a one-developer shop or a 5000 developer IT department in a Fortune 100 company. Collaborative engineering with appropriate participants (which almost always means open source licensing arrangements) is required. Why continue to work alone now that the Internet exists?
   
   
9. Consumer Technology is beating Enterprise IT, and soundly. If your “in-house” IT can’t compete with a consumer-grade provider available “on the web” you need to catch up and compete or concede the function.
   
   
10. Small incremental releases are essential. It isn’t just a question of not putting too many eggs in one basket – it’s also about lowering the cost of failure and therefore raising the level of innovation. Don’t accept quarterly releases of functionality, or even monthly. Web applications should change hourly or at least daily. The web is live, not pre-recorded.

OMMA Global Day One: The Year the Media Died

Highlight of OMMA Global day one for me was Terence Kawaja of GCA Savvian, whose presentation included a verse by verse playing and discussion of his own satirical song “Mad Avenue Blues” (sung to the tune of “American Pie,” with the refrain changed to “The Year the Media Died”).

Like the original, it’s long (9:21 in this case) and as Kawaja said in presenting it, lends itself to the elegiac mode – he wouldn’t quite say media is dead but it’s hard to write a catchy lyric about the era in which large mainstream media companies faced downward revenue pressure:

Interesting video for the luncheon keynote at a conference on online media, marketing, and advertising – but it hits on much of the industry’s current malaise.

The good news, such as it is, is that John Battelle challenged Kawaja to write an upbeat song on the state of the media – send your suggestions to @tkawaja.

See Also: Wall Street Journal coverage of the song

New WordPress plugin: Twitter Tools – StatusNet

When Alex King’s Twitter Tools plugin was in its 1.x days, I published some directions on how to change the API endpoints to point to Identi.ca.

Now that Twitter Tools is at 2.x, Alex has provided an API for enabling additional posting.

So I wrote a plugin for his plugin: Twitter Tools – StatusNet.

It leverages the API he provided to post your tweets (on new blog post creation or via the sidebar form) to a StatusNet instance (default is Identi.ca but it can be easily changed to another). (In case you missed the announcement, the software formerly known as Laconica, which powers Identi.ca but also other sites, is now known as StatusNet).

Given that many StatusNet instances also already cross-post to Twitter, my plugin enables you to suppress the actual posting to Twitter that Twitter Tools does. (You can have notices posted to both Twitter and your StatusNet instance, or just your StatusNet instance without Twitter).

What it doesn’t do is provide all the functionality Twitter Tools provides – digests of your notices, a sidebar widget containing latest notices. If you cross-post to twitter you can use all that functionality from Twitter Tools natively.

If you’d like to replace Twitter throughout Twitter Tools with your favorite StatusNet instance, you can hack away at Alex’s plugin directly – the same basic concepts I outlined before would still apply.

Being Interesting is Not Enough: Be Useful

How to Be Useful (Photo by Robert Banh, cc-by license)

I used to be fond of saying that the best advice for content-centric businesses on the web was a simple commandment:

Above all, be interesting – everything else will follow from that

Being interesting is still necessary, of course – if you’re trying to create a content-centric business and your content isn’t interesting, you’re in big trouble.

But is being interesting sufficient? In an attention economy, where interesting content is ubiquitous, and what’s truly rare is the users’ attention? In an era where every company is a media company?

In the era of the Assembled Web, where consumers expect to find content, community, and commerce pervasively and persistently throughout their online experience, is it enough to just be interesting?

Read more…

Social Media Engagement, Ice Cream, and Murder

Earlier this summer, the Altimeter Group and WetPaint collaborated to produce the ENGAGEMENTdb site and related ENGAGEMENTdb Report ( a free download).

It’s truly a must-read if you’re interested in how large brands are engaging their customers through social media. In the Introduction, Ben Elowitz (of WetPaint) and Charlene Li (of Altimeter) claim:

While much has been written questioning the value of social media, this landmark study has found that the most valuable brands in the world are experiencing a direct correlation between top financial performance and deep social media engagement. The relationship is apparent and significant: socially engaged companies are in fact more financially successful.

So now we know it pays to be social, but it is important to note that by “social,” we’re talking about deep engagement, not merely having a presence.

But there’s an interesting rhetorical slip there – in the space between “a direct correlation between top financial performance and deep social media engagement” and “it pays to be social” we’ve crossed the gap between correlation and causation.

Read more…