In my daily RSS skimming session, two articles managed to stick:
Andrew Gent's Web 2.0 and the Lack of Process
and
Michael Marth's Data First ist gaining traction in the industry
. While Andrew criticizes that Web 2.0 technology comes without a process and without structure, opposed to traditional tools in the enterprise such as Content Management Systems (CMS):
- By that I mean that the technology itself makes no assumption about how or why the technology would be used. What is the usage model for Twitter? Who should blog? What should you use a wiki for? The answer -- if you bother to ask -- is usually "whatever you want!"
Interestingly Andrew opposes these "process-less technologies", also including blogs not only to CMS, but also to E-Mail, Instant Messaging, IRC and web pages:
- Email, for instance. Process is designed into the very core of most of these older technologies. You have an email client. You choose who to send email to. They can read it, reply to it, forward it, save it, and delete it. That's all. The technology embodies the processes previously defined for physical mail.
If this is an example for the process that the tool makes assumptions about, then there is definitely a process for Wikis:
- You read a wiki page
- You edit a wiki page
- Other people read your contribution
- Other people edit the wiki page
- Repeat
There is a process for blogs:
- You write a blog post
- Other people read your blog post
- Other people comment your blog post
Out of this process emerged new technologies that were intended to improve the process. In the blogging space examples are Trackback and
CoComment, which improve the process of commenting in a blog. Even twitter has a process, or an etiquette: "Follow your followers, to allow discussions" is one aspect of this etiquette.
And even tools like E-Mail, Instant Messaging and IRC needed some time to develop their own etiquette: How much time am I allowed to let pass before I answer an E-Mail? Should I send instant messages to people with an "away" presence state? It is not the tools that create the process, its the people. People decide how to use Twitter, how to use Blogs, how to use Wikis, how to use E-Mail, how to use Social Networks, how to use Instant Messaging.
People first, process later
If you try to implement technologies the other way round, without either implementing or improving existing processes (which classical enterprise software does), or allowing people to define and develop their own processes (which Enterprise 2.0 does, but the same applies to E-Mail, Instant Messaging, etc), you will fail, because your software is not able to meet the needs of your users.
A similar approach, in a different domain, is described by the keywords data first, structure later. In software development, we are obsessed with structure. Having ontologies, taxonomies, schemas, class hierarchies, typologies, classifications, structured data seems the way to build successful applications. But as in the enterprise, too much structure without relation to the reality (here people, there data) will render your classification useless. Therefore a new class of frameworks is emerging that does not enforce structured data, but allows structurable data. If you want to know what this means in terms of technology, have another look at Data first is gaining traction in the industry
.