When I was asked to give a presentation titled “Putting Buzzwords to Work on the Web” at SXSW 2006, I was a little worried I’d have to give a presentation too glossy for my style. But given the chance to speak at SXSW, I considered it further, and discovered an opportunity to discuss something of interest to me — the language we use to talk about technology.
As I’ve said previously, the language used to describe technology generally focuses on and emphasizes the wrong things. I decided we’ve arrived at this point because, for the most part, it requires technical sophistication to create meaningful experiences on the web, and we’re using the language of the web’s creators– engineers and developers. My conclusion was that in the larger picture, this language is unfitting and unfamiliar to most of the people using it.
The word “tools†is particularly interesting– we use “tools†to make the computer do things– “blogging tools,” “word processing tools,” “photo editing tools.â€
But intuitively, blogging is really just journaling—however, we don’t intuitively think of a real-world pen and journal as a “journaling toolset.â€
To most of my relatives, RSS might as well be three random letters. But to those same relatives I can explain why content syndication is relevant on the web primarily because syndication is an word they already understand.
Microsoft’s Ray Ozzie did just this at ETech and wowed the crowd. He showed the value of syndication in a simple demo. If he had focused on the protocol or its potential in abstract terms, he would have had little effect. But by focusing on practical purpose, by demonstrating how syndication will be the underpinnings for solving practical problems, people got it.
But I’m optimistic that the language we use to talk about technology will change for the better– as I said before:
I’m convinced that over the next couple years we’ll see this language change because as “content management†evolves from a “tool†into something more meaningful and relevant to a larger audience, the web experiences we’ll have will be influenced by a new crowd, those without computer science and engineering degrees. And just as natural language evolves over time due to sociological and cultural influences, the language of the web will change as a new wave of contributors enter.
So how do we speed up the evolution of the language of technology into something more meaningful and relevant to a larger audience? One small but important step is to actually about purpose, not acronyms. Let’s realize that buzzwords in themselves are empty and meaningless. What is meaningful is purpose.

So you’re saying we need to create a PDL (Purpose Driven Language) around Web 2.0 to help eschew obfuscation.
I think you’re exactly right. The language of technology is an unneccesary barrier that needs to be broken down to help people understand what’s really going on with the web. One difficulty in changing the language is that there is a kind of secret club aspect amongst people who understand it. There seems to be a small satisifaction that some people get by discussing things in terms that others don’t understand. Hence the emergence of http://en.wikipedia.org/wiki/Leet
ph34r 14n th3 h4×0r
I’m on the fence about this. BuzzWords are empty and meaningless except for the very point the previous comment makes, the “secret club aspect.”
I think there is something deeper about human social interaction at work. BuzzWords have great meaning for the tech crowd. Knowing the buzzwords makes you part of the “in-crowd” in the geek culture. That acceptance breeds the confidence and productivity that makes all geeks seek out new buzzwords, invent new ones, and maybe some new technology along the way.
The fact that these terms are meaningless to the average potential consumer of the technology is the fault of marketing and product teams. Tech buzzwords help drive innovation, in a way, but they don’t help end-users and aren’t meant to. Marketing and product teams thoughout the tech industry are lazy, or misguided into thinking that people want to understand how a product works.
I think Bill is right in saying, it’s about what is does (the purpose), not how it does it.