Teblog

Will sustainability turn BT Global Services' fortunes?

The IT or, to give it it's full name, the ICT industry has led a pretty charmed life. After being a participant for over forty three years, it amazes me that it still manages to buck trends; from ever more power at ever lower prices to the potential ability to steer the planet and its occupants from environmental disaster.

At least, that's the hope and the intention of the green IT industry. Manufacturers are gleefully chomping out and selling more and more ICT equipment, while claiming that the environmental savings accruing from its use will mightily offset the environmental harm caused by its manufacture, operation and the disposal of whatever it's replacing.

Of course, IT isn't the only game in town. Cleantech industries are working hard on coming up with new things (with their embedded environmental harm) to reduce our overall environmental impact. It's paradoxical and uncomfortable, but it seems we have to do some more harm in order to do even more good.

One company that has an interesting environmental programme is BT Global Services. It also wants to be seen as "the IT provider of choice". It plans to do this by raising the level at which it consults with businesses by using sustainability as a lens. It has the IT in the form of data centres, software and services. And it has the C, because its core business is communications.

Global Services has posted some ghastly results recently and is in the middle of a restructuring. Perhaps it sees 'sustainability' as an opportunity to improve matters for itself and for the environment.

Anyway, if pretty charts are anything to go by, its Sustainability Practice has a comprehensive approach to helping its customers build sustainable organisations. Like many large companies (IBM, Cisco, CA and HP are just four examples), it has drawn heavily on its own experience to formulate its guidance for customers. For example, an early step in the process is a carbon assessment. This focuses on people, power and procurement.

People commute and travel on business and they use laptops, personal printers and mobile devices, for example. Power is used in office devices and data centre equipment, as well as heating, lighting and cooling. Procurement includes third party services, hosted equipment, print services, transport and so on. These three elements are analysed according to the three 'Scopes' of the Greenhouse Gas Protocol. (Scope I is the direct burning of fossil fuels. Scope II is electricity and the carbon created in using it. Scope III is indirect activity such as staff commuting.)

When you look at it this way, it seems obvious, but that's the deceptive thing about a simple framework.

Of course BT has a range of service offerings to match sustainability needs. And, as you might expect, substituting travel with communications looms large. And 'Homeshoring' is offered as a solution for UK contact centres. (With dog-cancelling microphones, perhaps?) The data centre hosting story is the usual one of greater carbon efficiency than a DIY approach.

The individual elements of the BT story aren't particularly original, but its telephony and networking pedigree hint at good service and security levels. It has many years of implementing sustainability initiatives with resulting business benefits. The savings it boasts sound huge, but these have to be considered in the context of BT's size (£21.4bn turnover last year). It saves £37m per year in travel costs and it saved £238m in one year through conferencing. It also reports a 20 percent productivity improvement from flexible working arrangements.

BT has spent years trying to muscle in on IT's turf. Now the industry really is ICT, perhaps this is the best chance it has. And, with the inevitable build up to December's Climate Change Conference in Copenhagen, now seems to be a very good time for BTGS to set out its sustainability stall.

Screen and voice recording/publishing for free

Any company that makes life easy for its customers gets my vote. And one company that tries hard to achieve this is Citrix Online. It is driven by a desire to simplify the previously complex. It also likes to undercut the prices of its major competitors.

Right now it has a free service in beta, called GoView which lets anyone create a screencast (voice and screen recording). Since the most popular screencast programs are desktop products, its traditional pricing model - a monthly fee - must have presented a bit of a challenge. So its solution was to go for an ad'-supported model. At the moment all the advertisements are for the company's other services and they don't in any way interfere with your own screencast creations.

True, it lacks the sophistication of Techsmith's Camtasia or Blueberry Software's FlashBack products, for example, but this is largely its point. It's good enough for the majority of existing and potential screencasters. A few clicks and your movie ends up online and you have a URL to share. If you prefer the extra control a desktop application gives you, you might want to check out Techsmith's Jing - a mini-Camtasia and screen capture program or FlashBack Express. Both are free, although the licence terms for Express appear to contradict this.

Returning to the GoView service, once the desktop element is downloaded, a couple of clicks start a three second countdown. Anything you then do on the screen or speak into the microphone gets streamed to the Citrix Online server. When finished, you can edit out the bad bits of the end result, add captions if you want, then share the URL with others. As Aleksandr in comparethemeerkat.com would say, "Seemplz."

GoView is currently in beta and some simple improvements could be made, such as being able to select an area of the screen for recording, rather than the whole screen. But the whole point of a public beta is that the developers get tons of feedback like this quickly and more or less for free. I, and many others, have probably spent hours buggering about with the software and the service. This gives the company a fairly massive free testing resource. The other point of a beta approach is that the service provider is more or less forgiven for flaws. It's how Twitter got so successful. Its 'fail whale' almost became a friend in the early days of the service. I had issues with sound and screen size on Vista at first, but it worked a charm on XP. Once underway, GoView seemed pretty robust.

I think the key to the Citrix approach, and that of many other disrupters, is that it realises that part the world needs sophisticated software and services, but a much larger chunk actually craves a simpler life and lower costs. Professional screencasters will still want 'proper' products which let them massage and publish the outputs in various ways. But regular end users who just want to just grab what they're doing on the screen, twiddle with it a bit, then send it off will be perfectly happy with a simple service which automatically stores the recording online and gives the user a URL which they can share via email, blogs, tweets or whatever. Jing, by the way, comes awfully close in this respect.

GoView is just one of Citrix Online's recent crop of disruptive services. It is taking a pop at the lucrative online education market with a new GoToTraining service. Its fairly new HiDefConferencing offers voice conferencing which can mix up to 500 PSTN and IP participants together. As with its GoToMeeting and other GoTo products, the terms for both services are based on unlimited usage per licence. This is the computing equivalent of one of those 'all you can eat' buffet lunches so beloved of certain ethnic restaurants.

While I don't care much for concentrating on single companies, it has to be said that Citrix Online is a bit of a one-off. It's a successful business which relies on simplicity and an absence of financial surprises for its customers. The first appeals to end users and the second to everyone.

Not a bad recipe at all.

Dan Bricklin (inventor of PC spreadsheet) on technology

A couple of weeks ago, Wiley asked if I'd like a review copy of Dan Bricklin's 'Bricklin on Technology' book. Normally, I'd say "not on your Nelly" because I know what a chore book reviewing can be. However, I was at the West Coast Computer Faire in March 1980 when Bricklin collected his first award for VisiCalc - the pioneering spreadsheet for the PC. I was also a fairly avid user of his 'Demo' program a few years later. Even though I don't think we met, (unless it was in Zaragoza a couple of years ago), I felt connected, not least because I also developed and published PC software for many years, but without his degree of visibility or success.
When the book arrived, I winced because it's more or less 500 pages long. Unless you're a commuter or you don't get much sleep, how do you find time to read that much?
Anyway, the book was enjoyable at a couple of levels and a disappointment at another. Enjoyable because it peeled off and examined the layers of thinking that went into various products and issues. Bricklin leaves no stone unturned in his pursuit of insight. The transcript of an 85-minute interview with wiki inventor Ward Cunningham is a classic in this respect. (It was 37 pages.) I'd rather Bricklin had identified and pulled out the key elements but then, I suspect, this would have been an editorial step too far for him. He would have had to impose his own interpretations on the conversation, rather than laying it out in full in front of his audience.
You will get insight if you read this book. Insight into what brought us to where we are and a few glimmers into how we might get to where we're going.
The other enjoyable bit for me, which you won't all share, is that I've met (albeit fleetingly) many of the people mentioned in the book, worked with many of the products and written about many of the issues. Bricklin and I even started programming at the same time - early 1966, and we've both tried to take the user perspective in our work. The book triggered many long-dormant memories and reawakened many old feelings, especially in the late 70's/early 80's as we all groped our way through the chaos of the emerging microcomputer/PC business. This is not really a reason for buying the book because Bricklin's chosen subjects seem, in the main, to be serendipitous. A comprehensive history book it is not, although it is a useful addition to the history of the IT world of the late 20th century.
The book is a compilation of old blog posts, essays and transcripts of recordings, loosely arranged around topics which Bricklin finds important, all topped and tailed with narrative from the perspective of 2007/8. As he says in the conclusion, "On any topic you can explore deeply and find nuance", which more or less sets the tone for the book. He does dig deep, he records faithfully and, at times you want him to make his point more quickly. But maybe that's not what he's trying to do. Perhaps he's trying to help the reader understand the nuances, so that they can move forward with their own thinking. I don't know.
Most of his topics have some resonance today, although much of the writing has been overtaken by events or absorbed into the mainstream. The chapters will give you a clue: What Will People Pay For?; The Recording Industry and Copying; Leveraging the Crowd; Cooperation; Blogging and Podcasting; What Tools We Should Be Developing?; Tablet and Gestural Computing; The long term; Historical Information about the PC; Interview with the Inventor of the Wiki; and VisiCalc. It's a ramble round the industry and round the inside of Bricklin's head. His invention of VisiCalc gave him a passport to go where he likes when he likes and meet who he likes. And that's what he's done and, in this book, shared it with us.
My approach, if you're thinking of buying it, would be to say "I'm getting a good 300-page book, I'll just need to pick which 300 of the 500 pages are of most relevance to me." It's a bit like his approach to software - give the user the tools and let them choose how best to use them.

Amazon is selling it in the UK for £10.99

Cloud: evolution not revolution

Fed up with 'cloud' yet? You ain't seen nuthin'. It's not going to go away. But, with a bit of luck, it's going to start falling into place.

When Microsoft announced its 'Software Plus Services', many people, including me, scoffed. We assumed that this was just a way of preserving its profitable fat client software business while nicking whatever advantage it could from cloud-delivered services.

Microsoft has sunk its Office hooks deep into the corporate marketplace. But that won't surprise you. For better or for worse, people actually like using the same applications as their colleagues inside and outside the organisation and, in enterprises, the most popular ones are from Microsoft.

It doesn't matter how hard competitors try, the compatibility just isn't there. And, with products like Word, useful capabilities like Track Changes are just not portable. The wiki brigade will point out the nonsense of Track Changes and argue that a single workspace with multiple authors and a proper version history makes so much more sense. And in a pure academic sense, they're right. But, in the main, wiki products are lightweight and alien compared with the richness and ubiquity of Word.

What many organisations really need is concurrent editing of single instances of Microsoft documents. Some companies are working on such things, but that's tomorrow. They will have to climb the curve of evangelist, early adopter and early majority before they get anywhere near mainstream acceptance. By which time, who knows?, maybe Microsoft will have extended Word into a Microsoft-hosted wiki-like environment.

But Word is only an example of what's going on. Plenty of other applications deliver tremendous capability at the desktop and their online cousins less. A long time ago an industry pioneer called Adam Osborne used to claim that, "adequacy is sufficient, everything else is irrelevant." He probably said it in order to foist a portable computer with a five-inch screen on an unsuspecting world. But, for many, especially in the lower reaches of the market, his observation is true. There, OpenOffice, Google Docs and other products/services will continue to steal desktop business from Microsoft.

But, despite claims to the contrary, we're not about to experience a cloud revolution. The world isn't going to suddenly put all its eggs in the cloud basket. We're going to see a wide range of engagements with cloud. We've seen the start with SalesForce.com - a massively popular niche application which can be tapped into from anywhere. The same goes for email, online storage and credit card payment services. These are all cloud-based and require little thought to implement. They sit well with existing business processes.

Other cloud services act as an extension of the IT department, providing physical expansion (and contraction) without wrecking budgets and causing chaos in the data centre. As we move forward and we think of entrusting more of our IT to the cloud, we will need to tread carefully, lest we create hard-to-manage interdependencies between service providers. Nothing new in priniciple, but this is our own business we're entrusting to outsiders. SLAs and responsibilities need to be nailed down carefully.

It seems pretty obvious now that cloud services will sit alongside existing applications and services and be called upon when they provide genuine incremental value. But this wasn't so obvious a little while ago when the evangelists were screaming 'cloud is the future' and Microsoft, in what looked like a rearguard action to save its traditional business, was arguing that 'software plus services' is the future.

It sticks in my craw to say it, but I think Microsoft got it dead right.

Rumours of KM's death exaggerated

Say 'knowledge management' to most people in our business and watch the curl of their lips. It seems to be a 'given' that KM is dead. The usual reason given is that knowledge sits between our ears, so how the heck can it be managed? Even those who are prepared to stretch the definition a little bit into 'information' are still inclined to question the value of the stored information. I mean, what information is readily given up and what's its half-life anyway?
A few months ago, I stumbled across a US/Indian IT services company called MindTree. It has a Chief Knowledge Officer called Raj Datta. Expecting the worst, I spoke to him and was somewhat astonished to learn that he has taken a lifecycle approach to knowledge management. He recognises that it does live between people's ears. But he also recognises that it can be shared through social tools. The result is an organisation which spends a lot of time, energy and money on the most important bit of knowledge management, its creation in the first place.
Staff are introduced to many thinking and idea generation tools - from De Bono's Six Thinking Hats to mind-mapping. Through workshops and discussion groups, they can learn about many thinking concepts, developing their minds and their ability to innovate. Without creation, knowledge/information capture is merely ossifying the past.
Staff, called 'Minds' incidentally, are then given a wide choice of social and collaboration tools, from blogs through wikis to discussion groups, and more. They are also given a physical workplace which encourages planned and serendipitous encounters.
The astonishing thing about this company is that it was implementing these ideas and blending them with its traditional KM/content management systems while most companies were still trying to figure out the relevance of social networking. MindTree turns out to have been something of a pioneer.
By joining the dots and ensuring that the complete knowledge lifecycle is supported: from inception, to storage, to sharing, to reuse, it provides the KM world an intelligent and holistic way forward.

Salesforce/Twitter: genuine help or fake sincerity?

Interesting that Marc Benioff (boss of Salesforce.com) should choose to announce the addition of Twitter to its Service Cloud on Monday. Why? Because it won't be available until the summer. Part of me suspects that the reason was simply because Twitter is a very hot topic today and it might be tepid by June. The official reason, I think, is that the deal with Twitter had just been inked.

The news might have passed me by had we (Freeform Dynamics) not received an official announcement from the company. The covering letter said, "...enabling companies to search, monitor and join conversations taking place on Twitter..." Without being a Salesforce.com expert, I was worried that a whole bunch of sales types or, worse, machines would start trying to insert themselves into Twitter conversations.

In fact, the pitch is somewhat more genuine than that. It suggests that organisations can monitor Twitter (a free addition to the $995/month 'Service Cloud' which already provides access to a number of online services such as Google Search and FaceBook) for mentions and, when they relate to problems, do something about them. That something will end up as either a comment to the Tweeter with a link to a solution to their problem or, if lots of people have the same problem, a general announcement-type Tweet. (Or maybe a bunch of direct messages - I don't know if the Service Cloud can do that. Nothing, apart from the tedium, to stop the help desk people doing it though.)

All sounds pretty reasonable, right? Back there in Salesforce.com land, the client organisation will have a whacking great database of customers, prospects, queries and answers. Each can be clothed instantly with relevant Tweet threads. I quite often appeal for help online. If someone were to help me, and I said "hooray, it worked!" or similar, then this thread would be collected for future reference by support staff. A bit cheeky perhaps, but quite understandable. It expands the company's own knowledge base at little extra cost.

Getting a bit more sinister, it would be possible for a sales person with access to the Service Cloud to hoover up personal information about a prospect before making a call. ("Sorry to hear about your recent illness. How are you feeling now?") These things aren't impossible today, but because it's built right into the Salesforce system, it is actually quite powerful. A tremendous aid to fake sincerity.

And this is the point, isn't it? If the service is used for the genuine benefit of the customer, then people will welcome it. If, however, it's used to exploit the Tweeting public, then the backlash will be swift and unstoppable.

But who will the backlash be aimed at? Twitter for allowing access? The Salesforce customer for abusing the system? Or Salesforce itself for providing the Service Cloud?"

Any thoughts on that, Twitter?

Lotusphere mop-up; then I'll shut up

Rather than write a series of blog posts of ever-diminishing interest (for me and for you), I thought a final Lotusphere round up would make sense.

First up, Doug Heintzman. He's the director of Lotus Strategy. We talked about the market for collaboration software, top to bottom. I mentioned the bottom  last week. But, at the top, he talked about the Enterprise Adaptability practice: something that materialised after the last Lotusphere. The most interesting bit, for me, was the toolkit that it provides its practitioners for studying the social networking patterns in enterprise and using it to help build an ROI case. I asked him what parameters were measured, hoping to get a checklist for you, and was rewarded with a verbal finger wag. Something to do with the huge intellectual property value in the patterns that emerge. Drat and double drat. If you're interested in learning more, start here.

Okay. I've given up trying to find the next thing online. It was a brilliant use of the 'Crocodile Dundee in New York' scene where Dundee has headed for the subway to get out of Sue's life. She's dumped her fiancé and wants Dundee. The scene is the one in the subway where she wants to get a message to Dundee that she wants him back. Verbal messages are transmitted up and down the crowded platform until he clambers over the heads of the passengers for a reunion. Aaaah. You can see the clip on YouTube, but it hasn't got the IBM punchline. I tell you, if that's a real ad', aimed at real people, IBM/Lotus has hit a hole in one. Sean Poulley, the host of the session claimed that the nine collaborative tools being offered will be "competitively priced with meeting-only services". Interesting.

I'd wager that Casey Dugan was the most enthusiastic person at the event. She was showing off Beehive - a social networking site where people can reveal stuff about their personal lives as well as maintain professional connections. It has 50,000 users inside IBM so it is clearly of value to this substantial minority. It lives behind the firewall, which is less risky than public services. It's still a research project at the moment but you can grab more details here.

I think that's enough for one year about Lotusphere, except to say that some things made me unhappy. My Linux/Firefox  netbook wouldn't render my agenda properly. And I'd have liked a single sign on to the three different IBM services I was trying to use: the analyst site, the LotusLive site and the Lotusphere site. And, as for responsiveness, getting hundreds, maybe thousands of people trying to hit the access points and networks at the same time was a recipe for disaster. I gave up early and took to wandering round carrying bits of paper and having face-to-face conversations with real live people. Much more fun.

Now I'm taking a break. See you in a few weeks.

Dodging Stockholm Syndrome at Lotusphere

Someone was talking today about the Stockholm Syndrome in which hostages empathise with their abductors. Having just come back from Lotusphere I can understand that feeling.

You're surrounded by hordes of 'yellow blooded' delegates and IBM/Lotus folk who applaud and cheer at the drop of a hat. Sometimes to small nuances that totally escape the uninitiated, like me. I could cheerfully sit there sneering from my analysts' special seating area in the auditorium. But, when it came to talking to these genuinely enthusiastic souls, it was hard to remember that this was an organisation that had a particular job to do: to keep the faithful on board and to secure the interest of the rest of the world.

That it did the former, I have no doubt. The announcements came thick and fast. Given that Lotusphere happens once a year, it will be a while until all of the products and services are on general release. But the overall effect of the event was to persuade the faithful that Domino/Notes is a cracking platform, that it has a future, that it will simplify programming (did I hear by "500 percent"? I think I did) and that it will be possible to integrate all of the social software offerings into existing and future applications, making them a one-stop-shop for work, communication and collaboration.

What of the outsiders? Well, some deals have been put together to increase Lotus' reach and increase the customer's convenience. Salesforce.com, RIM - the BlackBerry folk, SAP, LinkedIn and others are all happily welding themselves to different parts of the Lotus infrastructure. There were others, of course and you can read about them on the IBM website.

But what about the size of organisations that can participate in the Lotus experience, and would they want to? This is where things get a little murkier.

Without question, Lotus is at its happiest with organisations that periodically write large cheques. And who can blame it? But it has ambitions to charge downmarket to hit organisations as small as, depending who you speak with, 1000, 500, 100 or 5 employees. That's quite a spread. But it becomes clearer when you look at the channels to market.

Again, IBM's comfort zones are selling direct or selling through systems integrators. The one thing that you can't miss at Lotusphere is what a massive industry owes its existence to the company's products. Consultants, integrators, third party software suppliers, even hardware makers, are only too happy to drink the Lotus Kool Aid and make money while providing valued services to their medium to large enterprise customers.

But Lotus needs to find a convincing route to the smaller organisations. It has, or soon will have, a bunch of offerings, in the shape of LotusLive Engage (Bluehouse as was) and various other versions of the software - Connections, Meetings and Events. These are variously abbreviated versions of the full blown equivalent on-premise offerings. And, in case you didn't know, all will run in the cloud. IBM's cloud. Again, there's more but that will do for now. The route to market is through intermediaries. Anyone with a bespoke requirement or an integration requirement will probably turn to their local reseller and a deal will be made. But the hoi polloi, assuming they realise the value of communication and collaboration, will go where exactly?

Lotus talks about being in discussion with telcos but we've seen many attempts over the past ten years for these to engage profitably at the low end. They have the relationship with clients through the telephone business but it's a big jump from selling lines and equipment to selling stuff with an intellectual content to a small business. I'm told that selling off the page has been a dismal experience so far. So either the customers will have to mature at their own pace and come knocking when they understand this stuff. Or someone has to get out there and engage with them effectively.

Enter stage left the hosting companies. The good ones are already used to providing high levels of advice and support online. They sell to small businesses. Perhaps this is where Lotus should be looking for salvation. SIs for people prepared to dig deep in their pockets and a lightweight semi-automated service provision for those with short arms.

Or, in the blizzard of information last week, did I go snowblind? Please correct me, if you feel so moved. At least I don't feel I'm suffering from Stockholm Syndrome.

The organisational social software paradox

Last week I reported on the shape of the enterprise social networking space with the help of Andrew McAfee's Berkmann Centre lunchtime presentation on the subject. This week I'll get a little closer to home and present you with a paradox you're going to have to resolve if you're thinking of introducing social networking into your organisation.

A few months ago, Freeform Dynamics and MWD joined forces to carry out research among 201 companies on the subject of collaborative computing. The respondents were roughly equally split between France, Germany and the UK. All organisations were at least 1000 employees and half of them were over 5000. Sixty percent of the respondents were IT-centric and forty percent business-centric. All had some responsibility for workforce communication and collaboration.

The research contained all manner of interesting stuff but, as promised last week, I'm going to take a couple of charts out which relate to risk. One of our questions centred around the unofficial use of collaboration software within the organisation. As you can see from the chart below, social software of the kind we were discussing last week has crept into most of these organisations to some degree. Over fifty percent of respondents report wide adoption while almost every organisation has at least some.

In the officially sanctioned figures (not shown), social media is in third place at a little under 25% but instant messaging remains bottom of the heap.

Now, I don't know if I'm being dim here, but if something is unsanctioned, it seems that people would need to get it in by stealth. This is easy enough to do with solo desktop software (if organisational desktop control is lax enough) but social media, by its very nature, needs more than one participant and a shared location in which participants can 'meet', either synchronously or asynchronously.

This being the case, it seems highly likely that at least a percentage of those interviewed must be using public services in order to achieve their social networking objectives. Some, of course, will have an in-house 'skunk works' server - rather as Euan Semple did when he was at the BBC - but this requires some degree of computer skill and, of course the authorisation of the IT department at least.

So, let's take a look at the second chart. This relates to the concerns of the respondents towards the use of public services for this sort of thing. Don't forget it includes the conferencing, communication and screen sharing applications mentioned in the first chart.

Security, compliance, user distraction and support overhead all rank reasonably highly when you aggregate 'major concern' and 'some concern'.

We clearly have a discrepancy between what people are doing and what their organisations would like them to be doing. No doubt the employees have their reasons for behaving in this contradictory way. I'd hazard a guess that they've found the perceived benefits outweigh the perceived risks. Within most organisations, I'd have thought it unlikely that people would adopt social software just so they can chat to their personal friends. (By the way, if you'd like to alarm yourself with a detailed run down of risks, take a look at this new report on Web 2.0 security from the European Network and Information Security Agency.)

I'll confess to a degree of bafflement and, if you are in one of these contradictory situations, I'd love to hear from you. Perhaps you can tell me whether things are as laissez faire as they appear or whether guidelines and controls have been put in place to minimise, or at least balance, risk. And, maybe, tell us how hard it is for your organisation to take social networking seriously and what efforts you're making to articulate the commercial benefits to the powers that be.

I look forward to hearing from you.

The knowledge worker and Enterprise 2.0

Always good to hear Andrew McAfee in action. He's the guy who coined the Enterprise 2.0 moniker a couple of years ago. He's an associate professor at Harvard Business School and, yesterday, he ran a lunchtime presentation and Q&A on "Enterprise 2.0: How Organizations are Exploiting Web 2.0 Technologies and Philosophies." The audience was a mix of students, faculty, journalists, analysts, bloggers, business folk and venture capitalists.

The subject matter was of particular interest to me this week, having already done a press interview, worked with some potential research clients/partners and prepared for a conference, all on a closely-related topic. It struck me as a good idea to listen in. Not least to get a reality check for my own thoughts. The tip-off, by the way, came through Elsua - an online pal who works for IBM - through Twitter, an increasingly popular web 2.0 micro-blogging tool.

The presentation, with minor adjustments, wasn't so different from what he was saying a couple of years ago. In fact, if this stuff is new to you, you will find value in his How to Hit the Enterprise 2.0 Bullseye blog post (November 2007). The bullseye in the headline means targeting the organisation but, in the body, it refers to his model of how a knowledge worker inside an organisation sees their connections to others. Because it focuses on people, it is immune to the shifts in technology. New applications can be added to and removed from the model without wrecking the basic insights it provides.

To keep it simple: at the heart are the people with whom we have strong ties - our colleagues, the people we work with, have lunch with and maybe socialise with; The next lots are those people we know - if we saw them in a pub we'd be happy to have a drink with them; beyond that, and this is where it gets interesting, are the people who would make potential colleagues, if only we knew about each other; and, finally, the outer ring contains the world of helpful people out there whose worlds are unlikely to collide with ours.

The strong tie group is unlikely to be the source of novel information or links to potential colleagues. They know each other too well. The weak ties are those most likely to lead us to new ideas and new opportunities. Enterprise 2.0 technologies don't cause these things to happen, but they can act as amplifiers of these natural processes. Wikis might be popular among strongly tied individuals while Twitter or Facebook might be used in both areas. The next ring cannot really be exploited without some Enterprise 2.0 technology, blogging in particular. McAfee talks about "narrating your work". Do this and with the help of regular search, tags or links from other sources it acts as a magnet to others who are interested in what you do.

The ring with no ties represents strangers. While having nothing to do with collaboration, it is a source of collective intelligence. McAfee ran us through some examples of prediction markets to show the usefulness of this ring. It boils down to aggregating the individuals' predictions of a particular outcome - presidential results, company performance, whatever. Closely linked to betting and not social at all. But remarkably accurate.

Sticking to the social part of the bullseye, McAfee said that the biggest fear of managers is that information would leak that shouldn't. He noted that email, photocopiers and USB sticks, among others, already provide plenty of ways to leak information. However social tools do increase the number of people who can see leaks, so the participative benefits of the Enterprise 2.0 world have to be weighed up against the risks of disclosure. Related to this, he mentioned that some companies 'close down' too much. Their use of social tools might be restricted to strong tie groups, foreclosing the possibility that someone else in the organisation might have something valuable to offer.

He claims to have begged organisations for horror stories relating to these technologies and says "the collection is empty". People inside organisations don't use this stuff to do nasty things. This is partly to do with the fact that they cannot participate anonymously and people already know how to behave.

I'm not sure that this is universally true, so next week I'll take a closer look at the risks and the remedies, especially when the outside world becomes part of the equation.