Sunday, 15 April 2007

Reflections on mashing my Blogosphere

The little time I've spent online this weekend I've ended up spending time playing around with the My Cosmos Feed pipe I created. Its now humming along about as good as its going to be within the current limits of Yahoo! Pipes. Some of the issues I've had included:

  • Weird errors trying to save changes to my pipes, but a minor upgrade to the most current Firefox release appeared to fix the problem;
  • Strange formatting issues with RSS feed, but it looks like Feedburner has helped out there in the end in terms of getting a clean RSS feed into my RSS Reader; and
  • What appears to be a limit on the amount of XML data Yahoo! Pipes can consume out of the Technorati API (which is fair enough - I just didn't see any documented limits).

A reminder that these mashing tools are still not quite ready for the average computer user. Still, technical problems aside, I'm enjoying this new feed I've created and I've also started to use the My Cosmos Feed pipe to explore the cosmos around other bloggers.

For my next trick I might have a go at creating a Pipe to output data that can be used to create an instant blog network map. Stay tuned!

Saturday, 14 April 2007

Mashing my own personal Blogosphere

You might recall that last weekend I created some network maps of the blogosphere around my own blog. Well, that was all well and interesting but what can we with that information?

Some of the questions I've been thinking about are (and in part, considering the idea of "best of lists" vs dynamic lists):

  • How do I keep up with changes in my personal Blogosphere or "Cosmos"?
  • How will I read the posts appearing in my personal Cosmos?
  • How can I easily share a way to help other tap into their own Cosmos?

Well, in the end I turned to Yahoo! Pipes for help and I'm pleased to announce the release of my first useful published Yahoo! Pipe - its called My Cosmos Feed. The result is a mashup using Technorati, Yahoo! Pipes and Feedburner.

What it does is this: Input the URL for a blog into My Cosmos Feed and it generates an RSS feed that includes the most recent 3 posts from the other blogs that link to that blog, plus all the other blogs that link to the blogs linking to the original blog! To see how this works in practice you can check out, via Feedburner, the My Cosmos Feed for the ChiefTech blog.

But wait, there is more - if you want to create a My Cosmos Feed for another blog (including your own) then hop over to Yahoo! Pipes to create it. Note: You'll need your own Technorati API Key.

Thursday, 12 April 2007

Knowledge: Its transplantable, Jim, but not as we know it

When talking about Knowledge Management (KM) these days we often make the point that knowledge is in people's heads, and that early KM efforts failed because they assumed that it could be "captured" into a database. I mean, its not like you can transplant knowledge, right?

Well, maybe we are wrong in making some assumptions about knowledge - there is a TV show on ABC (in Australia) tonight, called Thanks for the Memories:

"Is it possible that in receiving a transplanted organ, a patient could also inherit some of their donor's memories and tastes as well?

In recent years several heart transplant recipients have reported unexpected side effects including memories, habits, desires and new talents they never had before."

Of course if you are skeptical... this is a phenomenon known as cellular memory that doesn't quite have everyone convinced. So it looks like I won't be starting up my new knowledge transplant venture after all. Just think, it would have been great for dealing with problems like the ageing workforce ;-)

Tuesday, 10 April 2007

Exploring my blog network map - Collection vs Connection

Since creating my blog network map over the weekend I've started to explore some of the new blogs that it has revealed. One blog I want to highlight from exploring the network so far is Uncommon Knowledge by Lucas McDonnell. The current post talks about a subject close to my heart, Collection and connection: does this relate to blogs?

"One of the endless information science/knowledge management debates is on the value of connection versus collection. For anyone unfamiliar with this debate, it’s basically this: is collecting information all in one place better than providing connectors among the people who share that information (or knowledge, if you like that word better). Or vice versa?"

Is social network analysis of blogs one way creating relevant and timely "collections" in the social space, rather than the lists that people love to hate? Particularly as this lists get out of date so quickly. Lucas - what do you think?

BTW I also want to say a quick hello to two people who dropped by and commented on my post:

ContentExchange (Koral) knocks another brick out of the enterprise IT wall

I almost wandered straight past this post about Salesforce.com's new hosted content management offering - on the face of it, ContentExchange, which is Koral rebadged, is just a simple content management system with some nice social software features, like tagging.

I think comparisons with Microsoft Sharepoint and EMC Documentum as reported in Read/WriteWeb are little overstated (there's actually a cheeky post on the Koral blog that suggests 8 of 10 collaboration vendors don't even use their own products), particularly as I don't see any records management functionality or true Web 2.0 capabilities in Koral. However, if we look at the bigger picture this is obviously a way for Salesforce.com to leverage their CRM beachhead into organisations and sell related hosted services. This has two impacts:

  • Its an easy way for non-IT functions in organisations to bypass the IT department by using a existing supplier with a good reputation (its going to be hard to block); and
  • Its a cheaper way to implement (potentially if the solution works) as  Software-as-a-Service (SaaS) disrupts how these content management solutions are traditionally implemented - Saasforce, a Salesforce.com implementation consultancy, commented recently that "How we differ from the big five consulting organizations is that we are focused on doing lots of short integration projects, whereas an Accenture or a BearingPoint wants to send in a school bus full of consultants into its clients for 18 or 24 months at a time."

Another point to consider is that if Salesforce.com is successful, then it also points to value being seen in managing content around specific business activities rather than across the whole of an organisation. So from one point of view all ContentExchange and similar services will create is yet another enterprise content silo - unless of course it really is an open, Web 2.0-based solution.

Monday, 9 April 2007

SNA Map of my blog - second edition

My blog social network analysis (SNA) map (really an egonet map) from a few days ago was ok, but I wasn't completely satisfied. Inspired by this other visualisation, I decided to try using the Technorati Cosmos API to extract some new data.

This new map (and one containing all the data) looks quite different and overall I think its a more interesting map, however I still have some issues:

  • One of the limitations of both approaches is that I'm still only using incoming links (or rather, number of unique blogs linking to each blog), where as I would like to use both outgoing and incoming links;
  • The other frustration is that I still needed to clean up the data from Technorati to remove duplicates blogs, either with different domain names or links to specific blog posts (I'm not the first to notice this) - I suspect the best thing to do would be to create my own startup blog search site and spider it myself; and
  • I need to find a better publishing tools for the map - Many Eyes's network visualisation tool has very limited functionality compared to the desktop SNA tools I normally use, which makes it difficult to explore the network.

In my blog egonet, these are the top 20 most popular blogs based on the number of other blogs that link to them as reported by Technorati (that's number of unique blogs, not number of links):

www.elsua.net (37 incoming blogs)
www.anecdote.com.au (30 incoming blogs)
www.innovationcreators.com (28 incoming blogs)
www.fullcirc.com (26 incoming blogs)
www.mcgeesmusings.net (25 incoming blogs)
chieftech.blogspot.com (24 incoming blogs)
fastforwardblog.com (24 incoming blogs)
billives.typepad.com (23 incoming blogs)
blog.jackvinson.com (22 incoming blogs)
confusedofcalcutta.com (18 incoming blogs)
www.sdownes.co.uk (17 incoming blogs)
www.rossdawsonblog.com (17 incoming blogs)
www.michaelsampson.net (17 incoming blogs)
www.edbrill.com (17 incoming blogs)
engineerswithoutfears.blogspot.com (10 incoming blogs)
www.jasonkolb.com (7 incoming blogs)
mitchell.wordpress.com (6 incoming blogs)
planetkm.org (6 incoming blogs)
www.craigbellamy.net (6 incoming blogs)
rcd.typepad.com (5 incoming blogs)

Also, here are the top linkers within this network ("real" blogs only, again number of unique blogs, not number of links):

listics.com (18 outgoing blogs)
www.langemark.com (15 outgoing blogs)
intranetblog.blogware.com (12 outgoing blogs)
www.lucasmcdonnell.com (10 outgoing blogs)
billives.typepad.com (9 outgoing blogs)
chieftech.blogspot.com (9 outgoing blogs)
www.gerryriskin.com (8 outgoing blogs)
www.duperrin.com (8 outgoing blogs)
www.edu2do.com (7 outgoing blogs)
www.greenchameleon.com (7 outgoing blogs)
fastforwardblog.com (7 outgoing blogs)
mikeg.typepad.com (6 outgoing blogs)
c21org.typepad.com (5 outgoing blogs)
enterprise2rave.com (5 outgoing blogs)
www.fullcirc.com (5 outgoing blogs)
www.davidmaister.com (5 outgoing blogs)
www.mindthis.net (5 outgoing blogs)
www.zoliblog.com (5 outgoing blogs)
www.elsua.net (5 outgoing blogs)
jisi.dreamblog.jp (4 outgoing blogs)

Now to the technical stuff... If you're interested in know how I pulled all this together, these are the tools I used:

  • Technorati's API for the link data
  • I wrote an Microsoft Excel macro to automatically download data from Technorati using the API;
  • I also used Microsoft Access to help deduplicate and tidy up data; and
  • Many Eyes for visualisation.

I was surprised how easy it was to use Excel to access the API - basically I wrote a script that built a URL with the correct parameters for each blog and then just "opened" it. The data was then saved into a master table. Once I wrote the script, getting the data was quick compared to cleaning up the data.

BTW If you're interested in SNA, you might like to take a look at this article, Small World! (PDF, 89KB).

Saturday, 7 April 2007

Just for fun - a SNA map in Many Eyes of my blog

Its a long weekend public holiday in Australia for Easter, so as a bit of fun(!) I've created an SNA map in ManyEyes of the blogs and other sites around my ChiefTech Blog. There are two maps:

Now, a word of caution - and don't shot me over this - I should explain that this data has come out of Google incoming link data; it would just have taken to long for me to pull the data together otherwise. I had a choice of spidering my own data (no thanks) or using some other search engines but Google simply worked out to be the quicker of the options. If you have any better ideas for gathering this link data, let me know!

So these maps are really based on the incoming links that Google thinks are worth collecting. However, I thought that would be one way of filtering some of the rubbish out of the data anyway! In fact, its lucky that my blog isn't too popular as this would have taken a lot longer to put together :-)

I'm still exploring this data myself but in the meantime let me know what you think:

  • Are you in my blog neighborhood but perhaps we haven't said "hello"?
  • How does you blog neighborhood compare to mine?
  • What other patterns can you see?

Friday, 6 April 2007

Living on the Web

I'm currently digesting a very new report from CSC's Leading Edge Forum (you might remember that CSC is my day job right now) called Harnessing Web 2.0: Enterprise Strategies for Living on the Web by Doug Neal.

You can already read a summary of the report by John Milan on the Read/WriteWeb blog - picking up on the example of British Petroleum, he comments:

"'Living on the Web' is a fascinating study - not so much by recognizing trends and needs of the internet and business, but because it comes from a group of big business thinkers dedicated to big business issues. What makes it powerful is actual examples of big business changing - in this case British Petroleum."

One of the interesting things I found in this report it that it doesn't restrict itself to what many people are talking about in the Web 2.0 space and organisations - e.g. Social Media and Enterprise 2.0 - but actually looks at the broader spectrum of how we manage IT and why current approaches need to change in the context of Web 2.0. This puts a refreshing new perspective on the Enterprise 2.0 adoption debate (which by the way, I see as a narrower issue that Web 2.0 in the enterprise) and shows that while it doesn't have to be an adversarial process, it will require change.

IBM and Consumer Products

A few days ago I blogged about some of the other big IT vendors offering Web 2.0 flavoured solutions and I asked:

"considering that one of the themes of Web 2.0 has been consumer driven innovation, I wonder how well these large vendors will be able keep up with the fast paced evolution of Web 2.0"

I now wonder if I was picking up some weak signals from somewhere, as the following day Luis Suarez also blogged about this same issue, but focusing on IBM and discussing if it should play in the consumer space - Luis argues that companies playing in the consumer space have an advantage in getting their products accepted in the enterprise space:

"All of those different companies that have been experimenting in the consumer market about how they can leverage social computing for their own offerings are soon going to be ready for the next stage, which is bringing together all that innovation into the enterprise world and continue to shake the ground further of how interactions are taking place. Their main key advantage at this stage? Well, the fact that they already have got a massive, and successful, critical mass of knowledge workers making use of those tools in their own private time. And now they would probably want to make use of them extensively at their own workplaces. This is something that most large enterprises out there will have to struggle with, and big time! Convincing their knowledge workers that what they have to offer to them, and their customers, is better than whatever they have been using all along for many months / years is going to be a hard sell, a very tough one, indeed, so ignoring the consumer market at this point in time and in the near future may not be the right approach to things.

Time will tell, but something that has been going in my mind for a while is that same Web 2.0 in the consumer market is what got us to the stage where we are now, so instead of just fighting against it I think it would be a whole lot more productive to actually embrace it and take it on to the next level. As I said, to me, that is where the main challenge is, and what will help differentiate those companies that will survive the next wave of Internet interactions and those which will fail along the way."

Again, talking about weak signals, I made some similar comments last year specifically about Lotus Notes:

"Unfortunately the real challenge that Lotus Notes faces from an Enterprise 2.0 platform is that it isn't a consumer technology - the trend we have seen is Web 2.0 technologies coming from the outside into organisations and with only few exceptions this is unlikely to happen for Lotus Notes."

I don't want to turn this into a debate about Lotus Notes, because it isn't. This issue affects any type of software that has feet in both the consumer and enterprise camps

There have been related posts by James Governor, Mike Gotta and Luis has also posted the following follow up with links to other related articles that are well worth reading.

Its speaks... but nothing unexpected

We've all been wondering about Ray Ozzie, but at least he has made an appearance in the blogosphere via an interview in Knowledge@Wharton (BTW the fact that you need to scroll past about three screens of intro to get the meat of the interview probably says something about Ozzie's lack of presence outside of the Microsoft campus these days).

Ozzie is given the opportunity to pitch some ideas about the future of Software-as-a-Service (SaaS) and future computing architectures, he says:

"I don't believe a single model is going to solve all problems. Computers within an enterprise, for example, are very tethered. In the enterprise model, it might be that running applications off a service with a high bandwidth connection to that desktop is the perfect thing. Some professionals are highly mobile and the best architecture for them is to have things delivered to a mobile device and replicated up to the service.

In the docs and spreadsheets realm, I believe there are certain uses of spreadsheets in particular, where the sharing model [enabled by] using it up on a service could be really useful. I think that there are other scenarios where you want it on your laptop...

...Adobe is a great example. Flash is a rich client; it's rich code delivered to the edge. It's not a centralized model; it's a decentralized model. It just happens to be tethered to the service.

If anybody has a software and services model, it's Adobe, because of that rich [Flash Player] applet that they extend the browser with. The more they enhance that, as you can see in their Flex and Apollo plans, the more it becomes this unified software and service vision...

...Most web pages have JavaScript in them. That's code that is delivered to the client and it has the lifetime of the browser instance you're using. Flash -- what is that? Well, it involves enhancing the browser runtime by downloading code. But it tethers those enhancements to the service and the lifetime of those things is still within the browser. With Apollo, maybe you can make the lifetime that of the user on that device. They have increased the lifetime from the browser instance to the PC."

Other than being very complementary about Adobe's strategy, the mention of the Adobe Apollo model is worth considering in light of current conversation about it and the offline Web-apps debate. However, I find neither clarity or anything revolutionary in the Ozzie interview about where we are going to end up. For example:

  • I'm not sure I agree that we can't develop a single model to accommodate both "tethered" and "mobile" computing needs at the same time.
  • He suggestions that 1st generation SaaS "really just meant browser. Second generation means weave together hardware, software and services to accomplish a specific solution", but again this dismisses the whole ease of deployment issue and lack of vendor lock-in (from a technology platform perspective) that the browser provides.

So, he either has nothing to say or doesn't want to reveal his cards just yet. Nick Carr comments:

"Ozzie doesn't say anything unexpected, but he provides a through and often subtle explanation of his view of the future of software and of Microsoft."

Yep. Nothing to see here, people. Move along.

UPDATE: More commentary on the interview from Dan Farber.

Thursday, 5 April 2007

Bridging the gaps between intranets, innovation and Enterprise 2.0

The FASTForward blog continues to roll along, and I have to admit that there are still some good posts coming down the line. This recent post about innovation by Paula Thornton was almost perfect in challenging the assumption that Enterprise 2.0 is all about the technology - but then she says:

"Enterprise 2.0 provides necessary but insufficient means by which to facilitate the potential of individuals to innovate. The potential can easily surpass Knowledge Management initiatives, which were doomed by edict as a misnomer. There is no value in managing knowledge, an intert collection of bytes. The value is in facilitating human potential."

Unfortunately Thornton appears to be falling into her own hole by suggesting that Knowledge Management (KM) is all about managing bytes. That's a first generation KM idea that and no reflection of current ideas in this space. Now, I know I have said some of this before, but we should careful when try to compare Knowledge Management with Enterprise 2.0 and likewise Enterprise 2.0 with Intranets. In this respect its a little unfair of Thornton to pick on James Robertson's article about Building innovative intranets - I actually interpreted this as being about the concept of continuous improvement that needs to happen to keep an intranet relevant (something I've written about myself in The Search for the Perfect Intranet [PDF, 108KB]).

Getting back to Thornton's point - and she concludes that:

"I suggest that it is not Enterprise 2.0 that is threatened by this renaissance, it is the survival of the current IT model that is in question."

If I had one criticism of James' article (and my own for that, in hindsight) is that it still places responsibility for innovating the intranet with the "intranet team". In the words of Euan, if you are heading down the Enterprise 2.0 road then IT and intranet teams both need to learn how to get out of the way of the stuff that matters to the end users so they can innovate...

So here is a different perspective - rather than creating a wedge, what we really need is a way to bridge the gap between those focused on running IT and intranets with Enterprise 2.0.

In fact James Robertson has a second piece published at around the same time, Three fundamental purposes of an intranet, that reminded me of one of my favourite papers by Dick Stenmark, titled Information vs. Knowledge: The Role of intranets in Knowledge Management (PDF, 425KB). In this paper Stenmark introduces a "multi-perspective view of the intranet" consisting of information, awareness and communication (which he later expanded to include a fourth dimension, collaboration) - very similar to James' content, communication and activity idea. Stenmark concludes in this paper:

"When facilitating KM initiatives, information technology environments such as intranets may be utilised to establish a virtual meeting place where communities of practice can engage in dialogue and collaboration. Actions such as information creation, information seeking, and information interpretation can successfully be performed in these environments. To facilitate this, intranets must be design to support not only the informational aspects but also include people by making salient networks of users with similar interests and allow these to communicate and collaborate. I therefore argue the intranet must be viewed from both an information perspective, an awareness perspective, and a communication perspective."

From a management point of view, Knowledge Management, Innovation, Enterprise 2.0, even intranets and information technology are just tools used in organisations to achieve an end. Management helps us to frame these ideas in, dare I say, manageable chunks so we can understand and apply them. Its not perfect or holistic, but it is human. So Stenmark has helped to bridge the gap between intranets (information) and Knowledge Management. Can we do the same with Enterprise 2.0?

I think we can - add together Stenmark with recent concepts like McAfee's S.L.A.T.E.S., the Wisdom of the Crowds and earlier ideas like the Cluetrain Manifesto and even Tom Davenport's Human Centered Information Management then we have some pretty good bridge building resources in our management toolkit already.

And this brings me back to one of my questions, does how we do it matter more than what we do?

(Sorry, couldn't resist the tool metaphor...)

Online offline is really still just offline

TypePad hosted blogs are down at the moment and missing action. At first I thought it was some kind of DNS problem or even that our Aussie Internet links to the rest of world had been cut... but no, its some kind of outage.

Its a little unfair at the moment to point the finger at TypePad, as other services have their problems from time to time. And of course, some of the interest in offline Web-apps has come from issues of reliability. But at the end of the day an offline online Web-app is still offline.  The most important point is that you can't "communicate" - and for many knowledge workers this is what work is all about.

So, while offline online gives us some security we still need a fundamental change (or rather ongoing evolution) toward some kind of Web-OS that has allows us to not only work offline from time to time, but to have redundancy so we can keep communicating.

Technorati tags: , ,

Cognitive load theory and being PowerPointless

More evidence that PowerPoint is, well, PowerPointless:

John Sweller, from the university's faculty of education, developed the "cognitive load theory".

"The use of the PowerPoint presentation has been a disaster," Professor Sweller said. "It should be ditched."

"It is effective to speak to a diagram, because it presents information in a different form. But it is not effective to speak the same words that are written, because it is putting too much load on the mind and decreases your ability to understand what is being presented."

If you're interested in more depth, I noticed that Anecdote picked up on some links to the original research at the University of New South Wales which summarises some key points about "Cognitive load theory":

  • Working memory is only limited when you’re learning new information. Once information is in long-term memory, it can be brought back to working memory in very large amounts.
  • In a classroom situation, only limited material is going to be retained, unless notes are taken or handed out.
  • PowerPoint presentations can backfire if the information on the screen is the same as that which is verbalized, because the audience’s attention will be split between the two.

However I've been avoiding death by PowerPoint for years and I don't agree that we need to ditch PowerPoint completely; we just need to use it with caution by planning the whole presentation, rather than just creating a PowerPoint.

Tuesday, 3 April 2007

Do BEA, Oracle, etc really get Web 2.0?

I must admit I've been focused more on following the efforts of vendors like IBM and Microsoft at one end and start ups like Teqlo, but it looks other vendors such as Oracle and BEA are also offering enterprise Web 2.0 inspired "solutions" (yeah, I know sound odd doesn't it?):

  • BEA recently launched its Pages, Ensemble and Pathways collection of tools that promises to let users "Create it, Mash it, Manage it and Discover it"; and
  • Oracle's WebCenter offers "a set of integrated Web 2.0 services into a new generation of context-centric, composite applications."

I hear that Oracle is actively using social software like wikis internally, however, considering that one of the themes of Web 2.0 has been consumer driven innovation, I wonder how well these large vendors will be able keep up with the fast paced evolution of Web 2.0. And what happens if or when the bubble bursts?

The other question is whether these Web 2.0 offerings from large established vendors really offer a true Web 2.0 experience inside the firewall, or are they just mixing existing SOA approaches with user friendly interfaces?

I guess if it achieves the same end, does it really matter?

Technorati tags: , , ,

Sunday, 1 April 2007

Enterprise 2.0 and Records Management

I've talked a few times recently with people who are trying to reconcile Web 2.0 and Enterprise 2.0 technologies with issues in organisations related to records management. Well it looks like Google have done it again and solved this problem with Google Paper:

"Now in Gmail, you can request a physical copy of any message with the click of a button, and we'll send it to you in the mail."

As the name suggests, Google Paper is the smart way of backing up email as physical record. At this stage it looks like Google Paper is only available via Gmail, but imagine we'll soon see it added to the whole of the Google office suite - hopefully this will include Google Reader as I'd love to keep paper copies of the stuff I read in the blogosphere. After this I'm sure it only a matter of time before enterprise software vendors catch up with a similar offering.

I really think this idea is going to make adoption of Enterprise 2.0 so much easier. What do you think?

Hat tip to Read/WriteWeb.

Thursday, 29 March 2007

Saving E2.0's Soul

I've always been a fan of Tom Davenport and was disappointed that when he was last in Australia I ended up being elsewhere, so I didn't get to hear him speak in person. Its also a shame that Davenport doesn't really blog; not quite as bad as Ray Ozzie, but I feel the blogosphere doesn't appear to hold much attraction for him. So in some respects we shouldn't be surprised by his suggestion that Enterprise 2.0 is more likely to be the "next small thing". Commenting on the vision put forward for E2.0, Davenport says:

"Such a utopian vision can hardly be achieved through new technology alone. The absence of participative technologies in the past is not the only reason that organizations and expertise are hierarchical. Enterprise 2.0 software and the Internet won't make organizational hierarchy and politics go away."

Mike Gotta - following Davenport and a response from Andrew McAfee - adds this analysis:

"I have a slight disagreement with Andrew McAfee that these tools are radical departures from previous generations of communication and collaboration technology. I see these technologies more as a natural progression. Tools emerging under the category of social software are benefiting from common application, infrastructure and network services that were not mature in the eighties and nineties. There was a reason e-mail was the "killer app" 15 years ago. A store-forward model was the only viable design given unreliable end-to-end networks with limited bandwidth. There was a reason a platform such as Lotus Notes was such a huge hit in the market."

I want to put a different spin on Davenport's perspective. Firstly, he thinks that the next big thing will really be in the area of business analytics - however, I think he failing here to see what the impact Web 2.0 and other related technologies will have in this space. More on that another time maybe, but think about mashups and "Data as the Intel inside".

But the main issue I'm sure Davenport has is that he probably feels he has seen and written about this all before. One of my favorite Davenport pieces is his 1994 HBR article, Saving IT's Soul: Human-Centered Information Management. In it he presents a manifesto for building information systems that focus on how people use information, rather than machines. He suggests that human centred information management should:

  • Focus on broad information types;
  • Emphasize information use and sharing;
  • Assume transience of solutions;
  • Assume multiple meanings of terms;
  • Continue until desired behaviour is achieved enterprisewide;
  • Build point-specific structures;
  • Assume compliance is gained over time through influence; and
  • Let individuals design their own information environments.

Pretty good for 1994 don't you think? No wonder he thinks E2.0 is old hat. But Tom - don't give up on E2.0... we need your help to save its soul too!

Wednesday, 28 March 2007

You heard it here first... the online desktop vs offline Webapp debate

For a while I thought I was just some crackpot blogger questioning the value of offline Webapps, but I feel a little better now that Read/WriteWeb have entered the debate with a couple of posts today:

  • It started with this post, Adobe Apollo - On A Collision Course With Web Browsers - "It appears that, intentionally or not, Adobe is on a collision course with IE, Firefox and the rest of the Web Browsers. Firefox has already said it is looking to add support for offline applications into its next version. If this happens, it will be bad news for Apollo - because Firefox users are not going to switch. IE plans in the same space are not clear, but we can be certain that if offline mode for web applications takes off, then there will be support in IE."
  • And was followed by this, Point/Counterpoint: Which is better, an offline Web App or an online Desktop App? - "This is a point/counterpoint argument, with John Milan taking the position that online desktop apps are better, while Richard MacManus argues for offline web apps."

Now that I don't feel like such crackpot (at least for asking the question), I'll put forward a couple more poorly thought out ideas for you to think about:

  • In the longterm the browser is dead, and I think the question is more about offline Webapps that work across multiple operating systems vs online operating systems - in a way I see Adobe Apollo actually challenging the value of the underlying operating system;
  • In the longterm the offline vs online doesn't matter, the future (Web 3.0?) will be peer-to-peer - I don't actually want to worry about synchronisation, I just want to access my data when I need it, from where ever I am and from what ever device I'm using... so lets actually separate the client from the data even further.

OK. I'll crawl back in my cave now. Switch off the lights please.

The Seven Step Radical RSS Reading Seminar... not really ;-)

I knew this was going to happen at some point... Attensa have posted a series of posts starting here, then here, here and here providing some advice on good RSS reading practices

Its all good advice, but I particularly like this point:

"Don’t be Afraid to Delete, and Don’t Feel Guilty About It

Give yourself permission to ignore things that don't look threatening or critical. It’s ok to delete articles that aren’t relevant."

I'm sure its only a matter of time and we'll soon see people offering courses along the lines of The Seven Step Radical RSS Reading seminar ;-)

Wondering What Wiki Will Work?

All this talking and thinking about wikis over the last few days, following from a NSW KM Forum meeting on this topic, has got me looking again at some of the wiki options out there. One useful source is WikiMatrix, which currently helps you to choose and compare 84 different wiki software options.

Wandering around the different options I began to think about what would the best approach be for someone who wants to get started with exploring wikis inside the firewall, particularly if you operate in a more restrictive IT environment or simply don't have the technical resources? Well, here are a couple of ideas:

Another issue might be that your IT department wants you to use an existing enterprise platform. An interesting discussion thread I came across in WikiMatrix is a request to add Sharepoint 2007 to the list. Apparently they need - I wonder if someone from Microsoft will step up to the plate? I wouldn't mind seeing something about the IBM Lotus options too, as there are some wiki templates for Notes and Quickplace available too.

Have fun!

Apply for the "CoP" job

More proof that knowledge management is alive, well and succeeding in some organisations - here is a great opportunity for someone passionate about Communities of Practice (CoPs):

"You will help to optimise the operation of our overall portfolio of CoP, as well as contribute to the development of the strategy, governance and operational models. Key components include providing direct assistance to CoP Coordinators and Sponsors, identifying success stories, developing education and training processes, facilitating the capture of explicit knowledge and raising the level of awareness of CoPs"

You have until April 14, 2007 to apply and can work in Perth, Brisbane or Salt Lake City!

Tuesday, 27 March 2007

Reflections on last week's masterclass and the learning experience

Well, I'm back in Australia again. I actually spent the weekend in Canberra and had the opportunity to visit Questacon - an "interactive science and technology Centre" - and it was a nice reminder about the importance of play and discovery in helping children and adults alike in learning about technology and science. It reminds me of a comment from one participant in last week's masterclass about the value of attending who said it wasn't just about hearing some new ideas, but having a chance to think and discuss the issues.

Another participant also commented on my blog that:

"having an open-ended ending is interesting (though not new), but requires certain maturity (in the learners) and understanding that the learners are able to come to a sensible conclusion themselves."

A good point. Just like Questacon, the masterclass is just the beginning of a learning experience and there maybe new skills and knowledge we need to develop along the way. I know there is interest in this already and I look forward to continuing this learning conversation online with you.

Wednesday, 21 March 2007

Currently in Singapore

I'm currently in Singapore with no time to blog really, respond to comments or even keep up with my RSS feeds. Very quickly:

Saturday, 17 March 2007

Wikis and blogs at Accenture, Westpac and others

In the AustralianIT section of The Australian newspaper, a story interviewing some large organisation in Australia about their use of Web 2.0 technologies:

"Accenture is using wikis and blogs both internally and to talk to clients. Executives as far up the command chain as the company's global chief operating officer use blogs to communicate with staff.

The practice is already having an impact on the use of voicemail in the company and it is also starting to supplant long established collaboration tools."

An analyst interviewed for the story also commented that:

  • It will come down to a choice between web-based communications and vendor backed collaboration tools such as Microsoft's SharePoint suite.
  • It will be at least another 18 months before wikis come into widespread use within corporate environments.

Greater than the sum of the parts

This is a great presentation, in terms of both style and content, about the value of social software by Tom Coates at the Future of Web Apps conference in San Francisco in September last year. I don't have anything to say about it really but I wanted to book mark it for future reference :-)

Social software in organisations: Nature or nurture?

One of the messages coming through about using social software inside organisations (what many of us are calling Enterprise 2.0) is that it is easy to use, and therefore easy to adopt. I recently commented on Dave Snowden's blog in response to his post about "social computing" that while I thought his theory was sound he had made some assumptions about the technology, in particular this issue of ease of use. Dave in turn responded that:

"I have yet to find a social computing tool I could not pick up and use. Learning is experimentation, on line help, web sites. The includes learning how to blog and use a whole range of tools. If you have counter experience or cases please let me know as it would surprise me to find them."

Well, if you want broader evidence than my own experiences of information technology in organisations, all you have to do is look a little harder at the case studies - for instance in the recent BusinessWeek special report on wikis, they mention this:

"The experience of Nokia and Dresdner Kleinwort offer insight into how to nurture the use of a radically new technology to change the way organizations work. Clearly, not everyone recognizes the value of wikis right way. The initial efforts at Dresdner, for example, confused employees and had to be refined to make the technology easier to use. More important than tweaking the technology was a simple edict from one of the proponents: Don't send e-mails, use the wiki. Gradually, employees embraced the use of the wiki, seeing how it increased collaboration and reduced time-consuming e-mail traffic."

Confused employees... I thought this stuff was so easy that everyone could just pick it up and use? Actually, I don't see this as a negative comment against social software, but I do think we have become a little confused between the simplicity of social software and the concept of ease of use. Wikipedia's definition of ease of use is this:

"Ease of use refers to the property of a product or thing that a user can operate without having to overcome a steep learning curve. Things with high ease of use will be intuitive to the average user in the target market for the product. The term is often used as a goal during the design of a product, as well as being used for marketing purposes. Put simply, things with "high ease of use" are easy to use.

However, some experts distinguish ease of use from ease of learning, especially when the design of a product involves a tradeoff between the two goals, or between ease of use and other goals such as security."

I believe what makes social software easy to use is its simplicity. But this doesn't make them universally easy to learn without some help to get over that initial inertia. This is something I've blogged about before and I don't see anything different in the pattern of innovation with enterprise social software, except that the inherent simplicity of the tools and the prior experience of some users using social software on the Web all aid the rate of adoption.

It is also important to note that adoption of social software on the Web is different from the adoption of social software in organisations - there are different motivators and barriers to use at play. In this respect both "social software" and (worst still) "social computing" are poor terms in this context. I grant you that Enterprise 2.0 has some problems, so if you prefer a less loaded term then I would suggest "enterprise social software". But the positive thing about the term Enterprise 2.0 is that does hint at a broader change that needs to take place for social software to be successful inside the firewall, and its not just having easy to use software... so a bit of both nature and nurture is required.

Tuesday, 13 March 2007

Spotting the Emperor's new clothes?

There are lots of conversations going on right now about Enterprise 2.0, but how much is just wistful thinking? In a recent post of mine, straight shooter Matt Moore challenged the hype by commenting:

"I have yet to hear of it actually [flattening and decentralising] in most organisations. It provides opportunities for that to happen but only to the extent senior management encourage this or at least do not actively prevent it."

Earlier Ross Dawson had also challenged Euan Semple about his adoption "philosophy" vs that of Andrew McAfee; Ross puts forward a view similar to the issues raised by Matt:

"I count myself as a true believer in Enterprise 2.0, but I’ve seen enough of organizations to know that the status quo has enormous power, and making good changes happen is never easy. In particular, unstructured implementation of social media tools in organizations will yield only a fraction of the value of a planned one. Yes I believe in emergence, but leadership is required to create fertile fields."

Later Andrew McAfee chips in, with a valid point, that in some organisations the approach taken by some to simply "plug in a wiki" or use a Web-hosted service isn't an option:

"The only reason I don't completely agree here is that I think Euan is assuming that in this scenario managers and IT departments are not blocking these tools at the firewall --  they're not precluding employees from using these technologies while at work... I've been in many offices where I couldn't check gmail, and it's not hard at all to imagine that many companies will try to keep employees from putting company data beyond the firewall on servers hosted by Socialtext, Zoho, Google, 37 Signals, or any of the other collaboration service providers."

Meanwhile, Bill Ives shares a new Enterprise 2.0 success story on the FASTForward blog and Dion Hinchcliffe suggests the following:

"What's a likely sweet spot for applying Enterprise 2.0 inside the firewall?  Keeping adoption of your preferred tools simple within the complex landscape of your organization so users won't prefer theirs; flatten your network as much as you can, open your systems using simple, open standards, and push the tools out fast (the network effect is pronounced with these tools so speed does matter).  Make Enterprise 2.0 as simple as humanely possible for your organization in this framework, but no simpler. "

So who is right? Well, who said there had to be a right answer? Perhaps the answer is all of the above.

Saturday, 10 March 2007

Its new but not difficult, right?

...but while some find it as easy as plugging their wiki into the network, Michelle Laurie's progress isn't so magical:

"Basically, I have 50 people from over 30 countries that need to work together for the next four years and will be meeting together at the end of March.  In preparation, I made the WIKI with links to information about the meeting, a survey they need to complete and a contacts page which they can fill in for example.  So far, five of the fifty have contributed.  On a positive note, I trained a colleague from DRC (Congo) by phone and he seemed to get it.  I think there may be a need for one on one training with people in order to ensure they are grasping the concepts.  Its new but not difficult.  At present I feel there is potential but not fuly convinced it will work."

Sounds like to me that the wiki isn't the problem here, but same old virtual teaming problems we already know about.

Another Wiki Case Study from Dan Bricklin: Thomson Learning

Dan Bricklin has recorded another wiki case study (MP3 podcast), this time with Thomson Learning. A separate write up of their experiences is also available, but its worth listening to Bricklin's interview for more background. In summary, the approach at Thomas Learning was to plug a laptop running Linux and Twiki into the network and let it grow from there (ok, slight simplification).

I say Knowledge Management, you say Enterprise 2.0 - but that's wrong

Is it me or just the feeds I'm reading, but the word "knowledge management" (KM) is appearing more frequently (and not just as a tag), particularly in the context of Enterprise 2.0 (E2.0). In fact I just noticed that a Technorati WTF on KM has appeared this week.

The E2.0 debate about adoption looks like the catalyst, but also I suspect the talk about IBM Lotus' new software announcements (and to a lesser extent MS) in this space has also fueled interest.

Its great to see people talking about the links between experiences with KM adoption with E2.0. In fact, the speed at which we are traveling along the hype curve to get to this point is quite amazing. But, before we get too carried away and find ourselves in the same position of confusing knowledge management and information management I suggest we all read Wilson's case against KM again, and also my own take on this issue.

Just as social software does not equal wisdom, E2.0 does not equal knowledge management. E2.0 simply provides KM with some new tools that can help with the KM problem of participation, including but not limited to social media (and that's great!). In fact, while James Robertson suggests we abandon the term "Knowledge Management System" from a planning perspective, I actually like the fact that the term is vague - a KMS should be any kind of information system you use to achieve a KM objective (I should add that I agree with James' central theme about buying branded KM systems). On the other hand, E2.0 represents a cross over between a KMS and just a part of a wider Web 2.0 trend that is also moving inside the firewall at the same time. Inside the firewall, Web 2.0 will provide:

  • New ways to support collaboration both inside and between organisations (also a benefit for KM, but not limited to KM);
  • A new approach for developing and deploying enterprise applications, and access to enterprise data (hmm, starting to get away from KM here) - for example, see Why "Super Users" are the new programmers; and
  • Better techniques for providing rich user environments that make software easier to use.
  • ...and there are probably more.

More importantly, KM is alive and well and for next generation KM the addiction to information technology is under control:

  • Concepts like Communities of Practice (CoPs) and Storytelling can all work without information technology; and
  • Social Network Analysis (SNA) uses computing power as a means to an end.

E2.0 ("enterprise social software") is different from KM because:

  • It is all about information technology - it does not and can not exist without it; and
  • It appears to have the power to change the shape of organisations, while KM typically tried to improve what was there or provide a way to tap into the back channel.

So, if you you are trying adopt E2.0 the question is are you trying to change the organisation for E2.0 or do you want E2.0 to change your organisation? I'll leave the final word to Euan.

Monday, 5 March 2007

Second year running! Enabling Knowledge Management with Technology Masterclass in Singapore

I'm just a couple of weeks away from heading back to Singapore for the third time to run my Enabling Knowledge Management with Technology Masterclass, with Ark Group Asia.

Like any of the seminars or workshops I run, I like to make things as interactive as possible and one of my favourites parts of the masterclass where I "debunk" the data > information > knowledge concept. It builds on some of the ideas I wrote about in an IDM article called, Knowledge Management: How to separate the wheat from the chaff (PDF, 108KB).

So with the increased interest in Enterprise 2.0 (something I already cover in the masterclass), I welcome other perspectives on the link between KM and Enterprise 2.0 - here are some recent ideas:

  • Bill Ives - "Enterprise 2.0 is more complex than knowledge management but it raises many of the same issues, only more so, and we can learn from its mistakes."
  • Martin Cleaver - "Knowledge Management as a discipline provides frameworks for understanding some of the dynamics of the big picture: from a strategy standpoint building the types of capital, from the individual, group and organizational levels. Much of KM theory was developed way before this Web 2.0 stuff came along yet many products and practitioners are unaware of just how many KM aspects have been reinvented in Web 2.0."

I agree - Enterprise 2.0 can be informed by our experiences with KM, but Next Generation Knowledge Management (NGKM) does not equate to Enterprise 2.0. Why? Because fundamentally you don't need technology for KM... but in some circumstance technology can help or even be a critical success factor. For example, large distributed organisations.

But, I'd love to know what you think - does Knowledge Management = Enterprise 2.0?

PS For those of you in Australia, I've been discussing with another conference company about running a shorter version of my masterclass locally - so stay tuned and keep your fingers crossed for details later in the year.

Inconceivable that Sharepoint-based social software won't keep improving

More on Enterprise 2.0 capabilities in MS Sharepoint (aka "MOSS 2007" - I hate that name...), Mike Gotta comments on Lawrence Liu's Report from the Inside - Lui tells us:

"As I stated quick emphatically during my "SharePoint Collaboration and Community Tools" session at the European SharePoint Conference last Tuesday, the wiki functionality in WSS 3.0 was not designed to compete directly with best-of-breed wiki products like SocialText, but rather, it's the integration of a plethora of collaboration and community features that make WSS 3.0 and MOSS 2007 best of breed as a whole...

...I believe that the built-in wiki functionality is sufficient for a very large percentage of our customer base, and many customers have indeed standardized on the SharePoint wiki as part of their overall standardization on SharePoint as the enterprise collaborative application platform. More and more SharePoint customers who want advanced wiki functionality are looking to the specialized wiki ISVs like SocialText to provide it with an integrated user experience in SharePoint by way of 3rd party webparts."

Gotta responds:

"An interesting perspective on how Microsoft views best-of-breed wiki technology versus what is currently available in MOSS 2007 / WSS 3.0. My gut feel though is that this is a "window dressing" (no pun intended) statement. It is inconceivable to me that the next major release of SharePoint Products & Technologies would not dramatically improve its core wiki engine and application capabilities (ditto for blogging and tagging/bookmarking)."

PS If you click through, don't get too excited about Liu's presentation - most of it was a live demo apparently...