Facebook: Open or closed?

Something David N Wallace said in his recent post triggered this train of thought.

There are people who think that Facebook is too open. And there are people who think that Facebook is too closed.

The Too Open crew tend to take a risk-averse enterprise view, and concern themselves with archival and retrieval and regulation and privacy and confidentiality and all that jazz.

The Too Closed crew concentrate on issues like absence of RSS, API restrictiveness, inability to export stuff out from Facebook, and so on.

The median age for Too Open is probably Generation X. The median age for Too Closed is probably Generation Y.

Ay, there’s the rub.

Facebook and the enterprise: Part 3

A few days ago, I promised to share my thoughts about Facebook in the context of knowledge management in the enterprise. So here goes.

First off, some context. For many years people have not wanted to share their “little black books”, their contacts and addresses. For whatever reason, some people appeared to feel that they were defined by the raw data rather than the relationships. Sad but true. As a result, when the first Customer Exploitation Systems came to be implemented, there were salesmen in all walks of life who pushed back, who refused to share their contact network.

Similarly, for many years bosses have not wanted their staff to help out any of the boss’s peers. If you take a charitable view of this, you could call it a case of incentive misalignment. Sadder still, the commonest reason was pure selfishness, bordering on spite.

I could go on but won’t. The point I’m trying to make is that our generation has not always wanted to share, to collaborate. To learn and to teach.  This is not something I’m seeking to solve within this post. You can take a horse to water….

I am far more interested in environments full of people who want to share but can’t. I think that tools like Facebook can make an immense impact in such environments. Let me take three simple examples:

One, relationships. Facebook has a rich array of relationships, from Friend to Group Member to Network Member and even Cause Supporter, all the way to Event Participant. And they’re all non-hierarchical and nonexclusive. This is very powerful, since it mimics real-life relationships far better than organisation charts and hierarchies. Furthermore, it allows you to “subscribe” to your interests with reasonable precision.

Two, conversations. Facebook allows a wide range of conversation types, from Poke to Send Message to Write On Wall to Chuck Book to Hug to Give a Gift to Dedicate a Song. It also features a number of conversation styles, from text to video (and surely audio cannot be far behind) and a whole plethora of ways to attach stuff and comment on stuff, both bilaterally as well as multilaterally.  Again, this mimics organisational real life far more than the straitjackets of email-only deprivation zones.

Three, transactions. Every event in Facebook is a transaction, and every transaction you do in Facebook can be an event. A news feed is nothing more than a transaction ticker. You get status updates on a number of things as well. And notifications. The entire alert process is promising and more flexible than traditional enterprise approaches.

None of this is perfect, but there’s a good foundation. Relationship-Conversation-Transaction. Pretty much everything persistent. Pretty much everything archivable and retrievable. The beginnings of syndication and search functionality.

Now, before I meander into my next Facebook post (where I connect Facebook with Four Pillars) let me bring this Knowledge Management piece to a reasonably tidy end.

Facebook provides a good relationship-conversation-transaction base as foundation. It assists you in finding people and skill and expertise, in creating communities of interest, in subscribing to news and events, in supporting polls and questions and discussion boards. It also captures quite a lot of profiling and preference and behavioural information.

If I had something like Facebook functionality within an enterprise, I could do things like draw collaboratively-filtered lessons from watching the apps that people used. Why does person A have an app set that differs so widely from that of person B? What can I learn from that difference? What can person A and person B learn from that difference?

If I had something like Facebook functionality within an enterprise, I could do things like plot out the routes that real information took, subverting hierarchies and tunnelling under garden walls. I could see relationship maps and mash them up with, for example, age-in-firm, to help me select mentors and buddies and role models.

If I had something like Facebook functionality within an enterprise, I could do things like start with a view that all information is open, then begin to close some elements selectively for regulatory or confidentiality or safety reasons. Instead of today’s post EAI post DRM nightmare, where Sharing is a Miracle. Or a lie.

More later. Keep the comments flowing.

Sites for sore eyes

Just some of the stuff I’ve bookmarked over the years and never blogged about.

  • If you think, like I used to, that everything’s an illusion, then go here.
  • If you prefer to argue about angels dancing on the head of a pin, as I used to, then go here.
  • If, on the other hand, your God is Clapton or Hendrix, as it was for me, then go here.

Just Sunday evening fun. Teaches me so much about Long Tail creativity.

Update: I’ve just been told that one of the links, the one to microscopic art, was inaccurate. It should now work.

Musing about cricket and Google and Cricinfo

As some of you would have gathered by now, I’m a bit of a cricket nut. [If you have no idea what the game is about, take a look at the Wikipedia entry that I’ve linked to, it’s a reasonably good place to start.]

Today was one of those frustrating days when I was sure Tendulkar would get his 38th hundred, but it was not to be. I make no comment whatsoever about at least four of today’s dismissals, other than to say I make no comment.

Moving on. By the time Taufel had upheld appeals for the dismissals of Tendulkar and Ganguly, I began to wonder whether an unusual record was in sight. The highest innings score by a team without any individual hundreds. So I decided to google it, found a route to a story in Cricinfo that listed the following entries:

  • India 524/9 declared (1976, Kanpur, v New Zealand, drawn)
  • South Africa 517 (1998, Adelaide, v Australia, drawn)
  • Pakistan 500/8 declared (1981, v Australia, Melbourne, won)
  • Bangladesh 488 (2005, v Zimbabwe, Chittagong, won)
  • Australia 485 (1993, v New Zealand, Christchurch, won)
  • India 485 (1997, v Sri Lanka, Nagpur, drawn)
  • South Africa 479 (2000, v India, Bangalore, won)
  • England 477/9 declared (1994, v South Africa, Leeds, drawn)
  • Australia 476 (1912, v England, Adelaide, lost)
  • West Indies 475 (1962, v India, Bridgetown, won)

Guess it’s time to make a new entry in 7th place. Interestingly, India now have 3 entries in the top 10. And they didn’t win on the other two occasions.

Jemodu

Tim Rice is rumoured to have come up with this in a recent letter to some cricketing journal. A fellow cricket aficionado, Tim has spent hours looking at the npower logo on the cricket ground. Upside down. And, given the font and style used, npower does look a lot like jemodu.

In typical cavalier spirit, he is meant to have written this letter, asking for readers to come up with suggestions as to what this fictional company jemodu should do. It was the sort of madcap thing that appeals to me, so I wanted to blog about it. And the first thing I did was to google “jemodu” in the hope that I would be led to the story, wherever I’d seen it.

No such luck. But.

You could knock me down with a feather. There is a company called jemodu. Appears to have been formed on 26th September 2006. Wonder what they do….. One thing’s for sure, the founder’s a cricket fan.