Sunday, 4 March 2007

Where do you stand on Enterprise 2.0?

I think its significant, in the context of the trends myself and others are tracking in the Enterprise 2.0 space, that there are number overlapping articles from ComputerWorld, Information Week and CIO magazine at the moment:

  • How IT Makes Johnny More Productive: Tech-enabled multitasking leads to productivity gains at the desktop, a new study shows - "one of biggest predictors of productivity is social networks — the people you communicate with over e-mail. Social network analyses have indicators of where you are in the network — whether you're central or peripheral. If you measure the shortest communication path between each pair of individuals, the number of times anyone else appears in that path gives you 'betweenness.' That means they’re in the thick of information flows, and it’s a good predictor of their productivity." [care of Jack Vinson] UPDATE: The paper behind this article is available for download.
  • Most Business Tech Pros Wary About Web 2.0 Tools In Business - "For all the mind-numbing buzz about Web. 2.0, most business collaboration and information sharing remains mired in endless e-mail strings and scheduled conference calls. More than half of business technology pros surveyed by InformationWeek are either skeptical about tools such as blogs, wikis, and online social networks, or they're willing but wary of adopting them."
  • Users Who Know Too Much (And the CIOs Who Fear Them) - "Users have a history of providing their own technology, but the capabilities of today’s consumer IT products and the ease with which users can find them is unprecedented... There’s a consumer technology out there for every task imaginable—and if there isn’t, there’s a tool that will let someone create it tomorrow. The era in which IT comes only from your IT department is over."

When will pull these articles together, there is a common thread and it won't surprise you - Elisa Graceffo, Microsoft's group product manager for collaboration and portals, sums it up well in the Information Week article:

"There's this tension between the IT department that wants to have this orderly, planned infrastructure, and you've got end users out there experimenting with all these different collaboration tools."

And the reason of course that users want these different collaboration tools is they help them to be more productive... isn't that what everyone want?

However, I still have some sympathy for "little guy" who comments on the CIO magazine article:

"Because I work for a medium sized non-profit, I’ve been able to escape a lot of the compliance issues my bigger siblings have faces, but it won’t be long now. Frankly, it scares me as I have few staff and fewer dollars. Now this article comes along to tell me - don’t worry about your corporate data, employee productivity, or the latest freeware screwing up the desktop - costing my staff time. It’s all part of the wonderful world of chaos IT! Let them do their chaos IT at home, where I don’t have to worry about fixing their screwups!"

But there is a counterpoint - which comes from a non-IT manager in another non-profit, Emily Turner, who approaches it as a Technology Stewardship issue, a concept I'm aware through Nancy White:

"There was no existing “IT Guy” to control how we used IT before I came along, nor do I think having one would have necessarily benefited us... Our organic way of collaborating and simple everyday working has fostered this more grassroots use of technology to develop ideas - people no longer feel like they have to shut their ideas down as unachievable, or feel they have to relinquish their control over them to strict technological requirements.

Social media tools are, of course, the best technology to use in cases like these. Perhaps my own self-training in figuring out these tools is the ideal background for integrating them into our everyday functioning."

I guess its all about perspective.

We Live in Exponential Times...

Some more thought provoking videos with information, knowledge and social media themes:

Did you know?

Re: Web 2.0 ... The Machine is Us/ing Us

This is response to the original The Machine is Us/ing Us.

Via my personal YouTube pimp, Luis Suarez, here and here.

Friday, 2 March 2007

MS Knowledge Network first release candidate now available

Just so you don't get the wrong impression that I'm completely obsessed with IBM Lotus, I thought you might like to know that Microsoft Knowledge Network for Microsoft Office SharePoint Server 2007 first release candidate is now available for download.

I'm watching both the Microsoft and IBM approaches to Enterprise 2.0 with great interest, particularly how they stack up against the bottom-up evolved wikis and other social software tools that have been sneaked in behind the firewall in growing numbers.

Care of Michael Sampson.

Thursday, 1 March 2007

Offline Web Apps - Please, Keep It Simple Stupid!

I noticed that my offline Web apps post got del.icio.us'd by Dion Hinchcliffe - he comments:

"Yep, offline capability is a key checklist for the next generation of Web apps, particularly for things like Web mail (when you're on the plane and have to get work done.)"

Hmm. Doesn't that assumes that inflight Web access will never be available or too expensive?

Anyway, when I'm on the road and I won't have Wifi access to the Internet I just download my personal email to my PDA, and my work email is already to sync'd on my laptop. Its already pretty easy.

Now this is not to say that I'm not convinced that offline won't be a key capability on the checklist as Hinchcliffe suggests, but I just see us cycling back into resource hungry, difficult to install and maintain, fat-clients that we went online to avoid in the first place... I just hope in all of this we remember to KISS.

PS Andrew - if you want to take your wiki with you right now, can't you just copy it with something like HTTrack?

Biffo between IT, users and the extended enterprise

Two sides of the current tension between enterprise IT and user-driven IT are represented in this post by Jeff Nolan and response from Mike Gotta.

Nolan says:

"here in the real world we are seeing examples of business units taking more control of their IT environments and telling corporate IT to go away"

Gotta responds:

"When there is a lack of trust, cooperation, shared ownership, sense of community and governance spanning business and IT, bad things happen. Enterprise 2.0 does not change that situation. Indeed, it could easily exacerbate it. Giving business units rights to do whatever they want is a governance issue... it all comes back to business/IT alignment and the continual engagement involving all parties that is necessary so we avoid the 'us' vs. 'them' mentality that really doesn't solve anything in the long run."

Meanwhile, over at Read/WriteWeb they introduce a third party - the Extended Enterprise:

"What is the Extended Enterprise (EE)?... The modern enterprise is no longer one, monolithic organization. Customers, Partners, Suppliers, Outsourcers, Distributors, Resellers, … all kinds of entities extend and expand the boundaries of the enterprise, and make 'collaboration' and 'sharing' important... Few of these Extended Enterprise stakeholders are inside the firewall. They don’t necessarily have accounts in the Enterprise IT network, posing challenges and creating friction in the workflow."

It's going to be a messy divorce ;-)

UPDATE: Who needs a CIO? Jeff Moriarty on the IT@Intel blog points out this post on the Long Tail blog and adds his thoughts on the debate:

"CIOs shifting from being innovators to being focused on Keeping The Business Running (KTBR). As a result, they have become more risk averse and are heading for a showdown with the newer generation of employees who have an expectation of just wanting a wide open pipe of connectivity and want IT to get out of their way."

Wednesday, 28 February 2007

A Big Day Out in Sydney looking at Social Software for Business

Tuesday was a busy day for me, getting out of the 'Gong early and up to Sydney where I started the day at Lotusphere Comes to You. The highlight of the morning was hearing and seeing a bit more about Lotus Quickr and Lotus Connections:

  • Mike Handes gave a great overview of Lotus Quickr, who described is a more interesting than talking about cricket at BBQs (ok, the Aussies aren't doing to well at the moment...) and explained how the different Quickr connectors, templates and services will make it "open and flexible". On the face of it, Quickr is a big improvement on Quickplace but on the other hand some of the views felt very familiar. Personally I'd like to see more things (if they aren't already there) like support for simple Web 2.0 ideas such tag clouds and more complex Web 2.0 functionality like "widgets". And while you're waiting for Quickr to arrive on an intranet (or extranet) near you, Mike suggested we take a look at the free Blog and Wiki templates for Quickplace available from SNAPPS.
  • The Lotus Connections concept ("Profiles,Communities, Blogs, Bookmarks, Activities") was also compelling and really suggests to me that IBM Lotus really do get this space. But to be honest I just want to get my hands on it to see how well it lives up to buzz in practice!

Later in the day, in a complete change of gear, I spent a bit of time chatting with James Matheson from specialist wiki consultancy, Saikore. There were two particular interesting parts to our conversation that I want to comment on here:

  • Firstly, the good news is that James feels that Australia has finally reached a level of maturity where wikis are beginning to achieve more main stream adoption. I personally hope this is part of a wider trend I've been watching coming to fruition, which will see more organisations adopting everything from wikis through to IBM Connections.
  • Secondly, some great observations about the essence of what makes an enterprise wiki a wiki, versus the wiki-like functionality appearing from the big software vendors like IBM and Microsoft. Some keywords for me that describe this are simplicity, solving specific business problems and being non-document centric. What this says to me is that the success of wikis in the business is more than just providing an edit button on every page and, on further reflection, why I don't believe tools like Jotspot are really a wiki because they are just too complicated (that doesn't mean they are bad by the way, just something different).

James doesn't have a blog as such, but check out the news page on his Website. I also found out that James made some contributions to the Wikipatterns site.

Later in the day I caught up with some old friends at Ernst & Young to see how "KWeb" was looking these days, before heading over to help out at the NSW KM Forum's first meeting of the year.

Phew.

Monday, 26 February 2007

Google vs Offline Web 2.0 Applications?

There is lots of buzz around the whole Google Apps thing at the moment, but an insightful observation from Josh Bernoff at Forrester Research:

"Google believes in a future where everything is connected all the time, and they're wiring up cities to help with it.  But this problem would be solved a lot faster if browsers ran apps, especially AJAX apps, offline. Then you could work on your gmail, your Google docs and spreadsheets, your calendar, in your browser. Offline browsing isn't new, but this is more complicated, because once you connected up again your apps would have to sync up -- the whole replication problem that Notes and Outlook take care of now. That's hard -- but not so hard that Google engineers can't figure it out, especially with some help from Firefox, Adobe, and others trying to weaken the Microsoft monopoly (see Rob Drury's post on this topic)."

This Mozilla Firefox offline applications thing is something I've been trying to get my head around too - we have a demo of sorts from Chris Double, showing Zimbra in offline mode, however incidentally there is an earlier example of this offline capability.

Considering the success of Web-based services and applications to date, I'm undecided at this stage about how important this is in the overall future of Web 2.0 - I mean:

  • If I wanted a fat client application connected to a server, I would still be using one;
  • Many of the benefits of social software come from providing simple access to common content that can be remixed, but offline mode is going to introduce the complexity of managing syncronisation conflicts in this shared data pool; and
  • It is built on the assumption of poor Internet access through a single device, rather than being always on, always connected through multiple channels.

I also think that I'm a little uncomfortable with the idea of browser-based offline applications is that it smells like we are reinventing the wheel. Think about this: I'm not quite enough of a geek to read through all the specifications Chris Double points at in his post, but I did read enough of the DOM Storage spec to see this:

"DOM Storage is the name given to the set of storage-related features introduced in the Web Applications 1.0 specification. DOM Storage is designed to provide a larger, securer, and easier-to-use alternative to storing information in cookies. It is currently only available in Mozilla-based browsers, notably starting with Firefox 2." [Emphasis added]

So, at the moment we have offline capability being built around the functionality of a particular fat client application (even if you make sound good by calling the browser the OS)... hmm, this all sounds a bit like (dare I say), Lotus Notes.

But either way, who ever wins out, are we just on the verge of replacing one monopoly with another?

Mashup News and the Difficulty Curve

No time to comment fully on this, but some good stories and articles about enterprise mashups:

  • Jackbe, who describe themselves as "a provider of Enterprise Web 2.0 software that combines Ajax and SOA with reliable, optimized Web connectivity to deliver Enterprise Mashups, Rich Enterprise Applications (REA) and next generation user-driven portals", have scored a great case study with the US Defense Intelligence Agency using its software. Reported in Computerworld.
  • Meanwhile, InfoWorld has a special report on enterprise mashups.
  • Finally, slow by steady E2.0 blogger Dion Hinchcliffe serves up a good analysis in two parts of the state of play by looking at the DIY space consisting of customisations, widgets and mashups.

Lots to read here, but I particularly like Hinchcliffe's take on the "Difficulty Curve":

This reminds me of some of the conversation I've had recently about mashups and "super users".

Honest Torrent

I blogged earlier in the month that Australian commercial TV is sticking its collective head in the sand about the disruption being generated by new social media technology. But I hear that Joost are busy signing up commercial content and now BitTorrent will be selling DRM protected TV shows and movies - from Wired:

"The BitTorrent Entertainment Network was set to launch Monday with films from Warner Bros., Paramount Pictures, 20th Century Fox, Metro-Goldwyn-Mayer and Lionsgate and episodes of TV shows such as '24' and 'Punk'd.'"

See, this could never happen in Australia. Whoops, forget that Internet thing is global ;-)

Technorati tags: , , , ,

Sunday, 25 February 2007

Software Patterns, the Old and the New

One of the reasons I started thinking about blog use cases yesterday was an indirect link between a piece by Michael Sampson and the Wikipatterns site that I noticed has got a few people excited.

Michael Sampson's point is to explain that outcome is more important than the tool, but that it can be affected not only by software functionality but also personal preferences towards a particular software tool:

"although the outcome quality of the coordinated effort may be similar for one technology vs. another, if you face the choice of turning the majority of people off by your choice of tooling .. that is, if there's a substantial difference between people's satisfaction with the process as influenced by tooling choices ... investigate different tools."  

In other words, if people hate product X, no matter how good it might be, then go with product Y or even Z because solution "elegance" isn't the same a business outcome. That's a good point.

Now this brings me to Wikipatterns:  There is nothing significantly new in the advice contained in Wikipatterns that we haven't already seen with issues around adopting earlier forms of collaborative software. But in the context of Michael Sampson's post, this doesn't change the value of Wikipatterns - its a very well executed site with clear explanations and guidance, all using the right jargon and addressing specific points of functionality in Wiki software.

So what's my point?

I want to reiterate that there is no wrong way of using collaborative and social media software tools, only a best fit with your objectives. And I don't care what you call it either. However it is a mistake to dismiss the experiences of the past because the language is different or the tools aren't as slick. For example, one of my favorite "pattern" resources has always been The who, what and why of knowledge mapping, which provides the following roles in making and using knowledge maps:

  • Map maker - creates the details and sets the usage pattern of the knowledge map
  • Map users - use maps in order to accomplish their tasks and to develop learning potential
  • Map innovators - alter existing maps through use, reuse and diffusion of innovation
  • Map champions - uphold the need for knowledge maps as providing a competitive advantage for the organisation

They sound like they could be very applicable to a Wiki, don't you think?

Similarly, we should not be afraid to draw on resources like Wikipatterns even if we don't think we are using a "Wiki" in the purest sense. These patterns are applicable in many other collaborative contexts.

But what I think is missing is that we do need to be clear about exactly what the new patterns really are, else the outcomes will be the same and it will leave some people wondering what the hype was all about.

Is Information Overload a Lifestyle Choice?

A new spin on information overload conversation, graduate university student Christine Wall is spending month experiencing life without any technology invented or widely available after 1950 as a research project. The media story on this experiment provides these interesting quotes:

"I literally feel I like I have 40 hours in a day. I realize how much time was sucked up with TV and ... the Internet and e-mail..."

and

"You can just see how addicted students are now [to email etc] and that they have the expectation things are going to be spoon-fed to them. ... Now, they feel like they can’t have a normal conversation. And by losing that skill, they become fearful of them. I feel like part of the reason to do this is we’re in this spiral that’s not good."

She is also blogging about her experiences, but is currently offline while she is living in 1950s mode.

Saturday, 24 February 2007

Why we need knowledge management... the warm and fluffy version

I hadn't seen this when I blogged this earlier today:

Care of Luis Suarez and many others.

PS I know that not everyone is an IBM Lotus fan, but I think you just need to enjoy this one without thinking about it too much ;-)

This is important: Not all blogs are equal

Thinking about some of my recent posts and the comments I've received, I've been considering the question, "What is a blog?"

I don't mean what is a blog in terms of attributes such as programming language used or how the content appears on the screen. I think we have some well established definitions to deal with those particular questions even if we want to argue about some of the finer points.

What I'm trying to consider is how blogs are used. This is a quick brainstorm of high-level blog use cases (rather than a fully refined list) that I'm playing with right now:

  • Data and information broadcasting - using a blog as a channel to broadcast information, particularly into an RSS feed for easy consumption.
  • WCMS replacement - using a blog application as an alternative to a traditional Web Content Management System.
  • Journals - a blog that is designed purely for the purposing of recording information or ideas, with either no audience or a specific reader in mind. Blogs in an elearning context are sometimes used in this way.
  • Groupware 2.0 - think of the activity centred blogs, as described by people like Rod Boothby. These are almost a hybrid of all of other use cases.
  • One-To-Many blogging - the classic example of a one-to-many blog is the CEO blog. The purpose of a one-to-many blog is communication, but using the blog style so that the message is more authentic and trustworthy. If they are used for good, then full marks to those executives who reach out to their employees and customers in this way.
  • Social blogging - as opposed to one-to-many blogging, social blogging is many-to-many and at its best becomes a hyperlinked conversation. An importance difference between one-to-many and social blogging is that the conversation should take place as peers - this means there are no experts and people can disagree with each other, making great conditions for wisdom of the crowds.

I want to point out right now that these are all legitimate uses for blog software, and anyone who tells you otherwise is either misguided or trying to sell you something you don't want :-)

However, in the same way that there is no right way to use a blog, it is important note that a blog may morph between different types over time (many people who want to be social bloggers often start out as a different type); further in the blogosphere we find an ecosystem exists where blogs of one type utilise blogs of other types for content (also think about the 1% rule here).

The multipurpose nature of blogs makes them exciting, but if we want to evangelize blogging by organisations (either inside or outside the firewall) then I think we need to understand the nuances of these use cases and the impact they might have on the desired or expected outcome.

Why we need knowledge management...

One of the reasons at least why we need knowledge management... from the UK's Mail on Sunday newspaper (and care of O'Reilly Radar):

"There at the side of the road are the first signs in the country specifically warning them to ignore the satnav. Owing to a fault in the electronic information system, many drivers are sent through the Hampshire hamlet only to find the lane narrows to 6ft and they get stuck."

This isn't the first time we've seen this kind of problem. I'm sure there are thousands of stories like this out there. And I'm sure that the more we improve the information system, the more we will find information gaps that get people in trouble.

Thursday, 22 February 2007

Social Software != Wisdom

Andrew Mitchell, via some comments, recently asked a whole series of questions about the use of social software (particularly RSS) within small-to-medium sized organisations (SMBs or SMEs).

I'm going to give my thoughts on Andrew's questions over a series of post (and in the meantime would welcome your comments and thoughts too), but the question I wanted to look at first was this:

"Within an organisation, how many people do you need to get the effects of Wisdom of Crowds, the Long Tail, etc? I don't think my company of around 250 staff would be enough."

I think it worth returning to conditions outlined in James Surowiecki's Wisdom of the Crowds for determining when a crowd can act smarter than an individual - they are:

  • Diversity;
  • Independence; and
  • Decentralisation.

If a crowd meets these conditions plus an appropriate aggregation mechanism exists that results in an action or decision, then you get the effect of the wisdom of the crowds.

Size isn't really a factor (obviously 1 or 2 people isn't a crowd!) but clearly the challenge for smaller organisation is effectively achieving all of the conditions outlined by Surowiecki. However, what smaller organisation probably need to think about is not being limited by the Enterprise 2.0 concept as "inside the firewall", but to connect the people they work with outside of their organisation directly into their internal knowledge network, perhaps using social software.

Of course if you can't or don't try to meet the conditions outlined above, it doesn't matter what software you use.

Tuesday, 20 February 2007

The slow death of Enterprise 2.0 on Wikipedia

Revisiting the Enterprise 2.0 (aka "Enterprise Social Software") entry in Wikipedia I noticed that, despite the HBS case study, the entry itself isn't actually getting any better.

The latest revision history has comments such as "hardly any content, no need to keep separate" and that the article shouldn't be "a link farm".

Unfortunately at the moment the article is less than 500 words (compared for example with the few thousand for KM) that hardly touch the sides of recent debate on this issue. The real shame here is that in Wikipedia is of course quite able to keep up with the debate, but clearly people have to be interested enough in the subject matter.

I've added some of my own content and others to help keep it fresh, but it really could do with more contributions. Otherwise, the content is so bad overall they might just as well have deleted it rather than this slow death.

One day workshop on organisational network analysis (ONA) from Optimice

Laurence Lock Lee, from Optimice, has let me know that they will be running a one day workshop on organisational network analysis (ONA) or if you prefer, SNA in Sydney on March 20th.

He explained that they are couching ONA, which is clearly an analytical technique, within a change management framework (they are still negotiating with their partners on this…so I can’t reveal details as yet).

They will be reviewing a selection of the 20+ ONA projects they have undertaken in a “lessons learned” manner, so no hiding here! There will also be a bit of hands on, where you get to do the fun bits in ONA... like playing around with the maps.

As a bonus the first 15 registrants will also get a free copy of Rob Cross and Andrew Parker’s book on “The Hidden Power of Social Networks”.

If you're a beginner in ONA or SNA, I highly recommend attending a course like this as while the technology of network mapping gets easier all the time, understanding the results is more of an art (on that note, check out my own Small World! (PDF, 89KB) article).

Monday, 19 February 2007

The Enterprise 2.0 Imperative

Care of Bill Ives, and published by WorkLight, a couple of IDC papers are available for download related to Enterprise 2.0, including one titled Getting Results by Empowering the Information Worker: What Web 2.0 Offers Beyond Blogs and Wikis (you need to register).

As Bill says, while he didn't learn anything new "that has not been discussed already by the enterprise 2.0 bloggers but the brief makes a nice executive summary written with conviction from a known source."

That makes up a little for the fact that while IDC are now warning that "those raised on the web will not tolerate the old ways and change will occur regardless of what the formal enterprise says", some of us have been watching that horizon for some time - check out the Intranet Imperative I wrote back in June 2005... I said then that:

"Of course while you can choose to ignore this imperative, be aware that technology has a habit of winning. You may find your users taking the path of least resistance (like returning to the dreaded network drive) or they will pick their own user-driven tools that will ensure they can get the job done."

Sunday, 18 February 2007

Breaking down silos

There has been a good bit of banter about Enterprise 2.0 going on between Andrew McAfee and Euan Semple that is worth following.

Most recently McAfee commented:

"what’s the real problem if some E2.0 environments are mutually inaccesible walled gardens?... The only honest answer is that we don’t really know yet, and maybe this kind of technology Balkanization will turn out to be no big deal within enterprises.  But I can think of two reasons why it might be a problem, or at least sub-optimal."

He then goes on to looks at impact of these walled gardens on emergence and what he calls, broadcast search.

This reminds me of a comment I made a while ago challenging the ease of implementing blogging, at a technology level, into a corporate environment. I have actually seen this happen in practice, where a blogging platform was introduced built using one technology that was completely inaccessible from the rest of the corporate IT environment, other than visiting the site with a Web-browser. I think it is still a big assumption from John Howard (not the Aussie Prime Minister!) who adds to the discussion that:

"Data no longer sits in a database hidden behind an opaque data access layer, it’s available as RSS and URLs, and can be linked too. To really make this stuff fly in an organisation you need an aggregation tool to close the loop."

Getting the aggregation tool in may be the stumbling block, rather than the individual social software applications.

The first step in creating a mash-up is...

Ok. I finally got the Teqlo public beta humming along. After registering again sans space in my username, I had only one more hurdle to cross - installing the Flash plugin into Portable Firefox. This almost had me stumped but a missing element on the Teqlo home page gave me a clue that I need one final piece before I could start to play.

Once you get in Teqlo, there isn't really a lot to see yet. As Rod Boothby has already explained that they "need more widgets", which they hope will emerge through 3rd party developers.

Now, my question is how easy it Teqlo to use?

  • Overall I didn't find it as intuitive as Yahoo! Pipes, which is another mashing tool I've been playing with - I was expecting Teqlo to be very drag and drop orientated, but instead it is more like select, select and drag.
  • At the moment you also have to have a good understanding of what widgets can interact with each other as there are (currently?) no visual clues about the potential relationships between each widget as you add them to the canvas.
  • I also get the feeling that writing a sophisticated application in Teqlo is going to be a bit like writing a sophisticated database in something like Microsoft Access or (dare I say it) Lotus Notes - the bit that often lets them down is the poor interface, i.e. it takes a bit of skill, time and effort to do it well.

So far Teqlo (or Yahoo! Pipes for that matter) hasn't convinced me that these tools will make everyone a programmer.

On the other hand, in the right hands Teqlo could well be the MS Access of Web 2.0 that puts Web-based application development into the hands of super users. In fact, a major benefit of the Teqlo approach could be, if they apply some kind of standards to 3rd party widget developers, is that it provides a safe Web 2.0 programming environment.