A long short game?

In between times spent snoozing in the sun, I kept an eye on the St Jude Classic. I quite like the look of Colombian Camilo Villegas, think he’s a fine young golfer who’s going to make a real name for himself, a guy who likes taking risks with his game, and blessed with great natural talent.

With today’s technology, there’s a lot you can “see” when following a game on the web, and pga.com do this very well. Which means I come across stuff like this:

A putt of 519 ft 10 inches. Now that’s what I call a looooong short game. Villegas is good, but not that good. I wish him well.

Musing about tweets as recommendations

If you read my last post, Thinking further about syndication,  then you would be aware that I’m devoting a lot of cycles to alerts, status messages, mini news items and tweets. I thought it was time I expanded a little on one small segment, tweets as recommendations.

When is a tweet a recommendation? Not when someone says “I’ve just blogged this” or “I’ve just posted this” or even “I’ve just launched this”. Not when someone says “And here’s me on <pick some media>”. That’s advertising, no getting away from it. No pigment, oil, wax or emollient can hide the porcine nature of such tweets.

I’m not saying that’s wrong. There’s nothing wrong with any of us advertising something we’ve done, so long as we don’t try and pretend it is something else. Such tweets (and for that matter, such alerts and status messages in general) are not recommendations.

So what makes a tweet a recommendation?

I think it’s the following:

  • The tweet must be unbiased, it must be about an entity that is in no way connected financially with the tweeter
  • The tweet must be clear in signalling something sufficiently positive about the entity
  • The tweet must be actionable, it must link to somewhere that the tweetee can do something about the recommendation
  • Most importantly, a tweet becomes a recommendation when the tweetee decides it is one

I think that’s a key point. When you tweet about something, you don’t decide that it’s a recommendation, it is the person who follows you who makes that decision. It is the “follower” who imbues the “tweeter” with the “recommender” tag about a particular class of social object.

Hugh Macleod has been hammering on around this space with his insights, initially on personal microbrands and then on social objects. Doc Searls has been working in a similar space with the work he’s been leading on VRM. Chris Locke was all over this in the lead-up to Cluetrain, in Cluetrain, and ever since.

The authenticity of recommendation is not conferred by the recommender, but by the recipient.

There’s a lot more we can do with tweets as recommendations. Staying with the Cluetrain theme, straying over to the Weinberger side of the argument, it is the very miscellaneity of the tweets that makes such things valuable. But when everything is miscellaneous, it’s time for the taggers to ride in.

So will we see a time when a tweet gets tagged by someone other than the tweeter? Is that how a tweet becomes a recommendation, when a second party adds something like #recommend #books to someone’s tweet? Maybe we’re almost there already.

We can also make the tweets carry more context. As I’ve said before, I just love the last.fm to foxytunes to twittertunes to twitter sequence; you’re listening to something, the title and artist/s get scrobbled off and packed to go somewhere, expanded into a full mashed-up result covering the song lyrics, artist web site, google returns, last.fm entry, iTunes link, wikipedia entry, the whole shooting match. Then it gets compressed again, snurled or tinyurled into submission, repackaged for suitability in a 140 character text medium.

We can have ratings associated with such tweets; we can use collaborative filtering techniques as well.

There’s a lot that can be done. I’ve used the music analogy, but this covers many classes of “social object”. Books, films, restaurants, airlines, hotels, anything.

And sure, people will try and game this. But you know what, it’s not that easy. What if we take such tweets and move them into a tweetypedia? A wiki place where customer-driven recommendations go? Tagged with value like Flickr, editable with care like Wikipedia. Then, if we take the Clay Shirky maxim of keeping repair costs as low as, if not lower than, damage costs, the tweetypedia can become a valuable common good.

Just musing.

Thinking further about syndication

When I started this blog, this is how I began the page on About This Blog:

I believe that it is only a matter of time before enterprise software consists of only four types of application: publishing, search, fulfilment and conversation. I believe that weaknesses and corruptions in our own thinking about digital rights and intellectual property rights will have the effect of slowing down or sometimes even blocking this from happening.

Those were my “Four Pillars”. If you want read what I said about syndication early on, you can find the post here.

Since then, I’ve continued with my almost morbid fascination with observing people at work, trying to understand what work actually means in the post-industrial sense. More and more, that fascination has focused on syndication.

So what is syndication? Put simply, I think of it as the “subscribe” half of a “publish/subscribe” model. People publish things. People subscribe to things. And most importantly, the people who subscribe choose what they want to subscribe to. They choose.

Recently, when I wrote about status messages and alerts, a number of you made some very useful comments, and what they’ve done is help me crystallise some of my own thinking. [So thank you everyone who reads this blog, thank you particularly for those of you who volunteer your time in making comments so that I may learn, that others may learn.]

And this is where I’ve got to:

There’s a continuing explosion in the number of ways we create information and in the number of ways we consume information. There’re a lot of people continuing to complain about information overload, and as a result there’s some resistance to the new forms of creating and consuming information. People want filters.

Historical filters, given the constraints of the communications technologies used, were about aggregations and summaries; the aggregator or summariser played a key role in the communications process.

But there was a problem. Aggregators and summarisers, well-meaning or not, introduced their own bias, and the authenticity of the original communications was undermined.

Today we’re in a different world, with different communications paradigms, models and tools. We’re not that far away from ubiquitous, digital, persistent, archivable, searchable, communication; the costs of transmission, reproduction, storage and retrieval have all dropped alarmingly; the devices at the edge continue to improve at a similar rate.

So now we can each do the filtering.

Which made me think, how? What should the tools look like? And that took me down a whole new path. I decided to go into what makes any of us subscribe to anything at all. And the best model I could find was the Four Drivers model, developed by Nitin Nohria and Paul Lawrence (something I appear to have referred to at least seven times in this blog!).

Nohria and Lawrence suggest that there are four primary drivers to anything we do: the drive to acquire, the drive to bond, the drive to learn and the drive to defend. Further, they suggest that these drivers act in parallel and not in sequence or hierarchy; they also suggest that the power or intensity of the drivers varies continuously. I like that model. A lot.

So where does that take me? My motivation to subscribe to things published is based on my drive to learn, bond, acquire or defend. So far so good. What happens if I use that model to classify the things I subscribe to?

“Drive-to-defend” subscriptions: These are alerts I subscribe to because they tell me about something dangerous, something that threatens me or my loved ones or people/things I am responsible for. Fire alarms. Calls for help and SOSes. Urgent texts from my children. Major systems outages. That sort of thing.

“Drive-to-bond” subscriptions: These are alerts I subscribe to because they tell me something about people that I want to get to know better, people I want to get closer to. Many tweets fall into this category, as people share what they are doing. I get an idea of their interests, their beliefs, their values, and I can identify the things we have in common as well as the things that we don’t share. Relationships are often defined not by the common things but by the things unshared. And they’re enriched by both. It’s not just tweets, but many elements of the facebook mini feed fall into this category, as people join and leave groups, become friends with others, promote and join causes.

“Drive-to-learn” subscriptions: These are alerts I subscribe to because they open up new avenues for me to explore, new ways of thinking, new things to think about. Again, many of the elements of the facebook mini feed fall into this category, as people share posts, follow links, become fans, join groups.

“Drive-to-acquire” subscriptions: This is the one I’m spending most time on right now, trying to understand more about how recommendations work. What happens when someone says they’re reading something, they’re listening to something, they’re eating something, they’re watching something. They’re doing something. What happens when that’s all they say. What happens when they share more than just the event, when they share their views on this thing they’re doing. They like the book, they hate the restaurant, they’re intrigued by the film. That sort of thing.

So that’s where I’m at. The point I’m making is that this information cannot be aggregated. When Sean recommends a book to me I am interested because it is Sean who is doing the recommending; I subscribe to Paul’s tweets because it is Paul. I subscribe to Jeremy’s blog because it is Jeremy.

Not because I want to get averaged-out filtered sanitised summarised made-into-bite-sized-chunks of pap.

I’ve had pap for years. Now I want the real thing.

And I can have it. Today.

That’s what syndication is about, the power of being able to subscribe to the things I want to subscribe to. Very granularly. Out of choice and not force. With no one else filtering or summarising anything at all.

Views? Comments. More to come after I hear from you.

Nude Big Ideas and Unintended Uses

Just take a look at this video:

To quote Jim Houston:

Based on the lyric (and alternate title) “Big Ideas: Don’t get any” I grouped together a collection of old redundant hardware, and placed them in a situation where they’re trying their best to do something that they’re not exactly designed to do, and not quite getting there.

It doesn’t sound great, as it’s not supposed to.

Sinclair ZX Spectrum – Guitars (rhythm & lead)
Epson LX-81 Dot Matrix Printer – Drums
HP Scanjet 3c – Bass Guitar
Hard Drive array – Act as a collection of bad speakers – Vocals & FX

Now that’s a line-up I haven’t seen too often….

And if you don’t believe him, there’s photographic proof, if there is such a thing as proof AP (after Photoshop). I believe.

Thank you Jim Houston. Thank you Radiohead for thinking up the competition. And thank you Jemima Kiss for alerting me via Twitter.

Wondering about status messages amongst other things

I’m sure there are better ways to decompose social networks, but in my simple mind, there are only a small number of fundamental components:

  • directories and address books (you need to find the person or group you’re looking for)
  • profiles and CVs and suchlike (there has to be some way of describing the person or group)
  • communications infrastructure (you need ways to talk and listen and exchange messages)
  • scheduling infrastructure (you need ways to agree times and places to meet)
  • event notifiers (you need ways to spread news and gossip)

All these then get wrapped into a larger infrastructure, which covers four other things:

  1. an ability to identify oneself
  2. an ability to personalise the experience
  3. an ability to have Four Pillars support (search, syndication, fulfilment; we already have conversation)
  4. an ability for developers to add applications

In a way that’s what Office and Exchange and Outlook was about. In a way that’s what Bloomberg was about. And in a way that’s what Facebook and even Twitter are about.

This is an emergent and evolving space, but only in a narrow respect: communities have been around a very very long time; communications processes have also been around for a very long time. What has changed is the following:

  • communications tools are becoming ubiquitous, especially with the web and mobile devices
  • communications themselves now persisted digitally (allowing efficient archival, retrieval, search and syndication)
  • the tools and the modes of communication have become more affordable

As a result, there’s a lot of learning to be had. Some people are concentrating on the interactions within the communities, the social graph as it were. Some are concentrating on movements: take a look at this article, published in the latest issue of Nature, and building on a theme established by a number of essays written by Barabasi and Gonzalez et al over the last couple of years); some continue to focus on the ownership, privacy and portability of the information. Yes, there’s a lot of learning to be had.

From an enterprise context, the learning takes on one further dimension. Enterprises have always been about walls and perimeters; now, as the walls become more and more porous, as the enterprises extend beyond their traditional boundaries to their customers and supply chains, communities become alliances, they become ecosystems, they become groupings of what Venkat calls “network-based competition”.

Yes, there’s a lot of learning to be hard.

Me, I’m utterly fascinated by one small piece of this overall puzzle. Alerts, event notifications, status messages, whatever you want to call them. Maybe it’s the old journalist in me. That’s why I loved the mini feed in Facebook. That’s why I loved Twitter.

And now, as I see more and more tools that help scrape information to do with events, I find myself going off at a tangent. Realising that we’re going to get overloaded by such messages (remember what happened when people started connecting Twitter to their Facebook status messages?); realising that current tools are already being stretched; and realising that the historical response (aggregation and summarising) is inappropriate.

I think we’re going to see an explosion of activity in the status message related tool space, with two different sets of tools. One to do with personal “manual” input, one to do with automated input. In both cases, I think we’re going to see this explosion connect with a similar set of explosions in the visualisation space, so that we see more colour, more heatmaps, more timelines, more fractal representations, more radar diagrams, more tag-cloud-like diagrams …… but all to do with status messages.

Status messages with a difference. Not aggregated, not summarised, but built around a capillary-action publish-subscribe model. Truly personalised.

That’s provisional enough. Now I wait for the comments so that I can learn more about this.