Contented Management laughing buddha logo

Contented Management

Contented Management

Information in a bear market

Dennis D. McDonald continues to propose interesting thoughts on information management. This one – on the importance of social media in post-merger organisations – struck a particular chord with me.

A previous project I ran was to implement an internal knowledge management portal for a company that had been through several rapid mergers of some pretty small companies into a pretty large one. The company’s success is based on its staff expertise and wealth of project experience, but the full range and depth of this knowledge lay fragmented across a few people from the various entities that constituted the new whole. As a consequence, the sales team didn’t know that they could use staff who’d already engaged with a particular client, or that there were case studies for similar projects including case studies and lessons learned. The wheel was being reinvented. It was obvious that some kind of networking tool that enabled staff to identify expertise in people and projects would lend the business a helping hand and could be implemented with relative ease.

Instead, the directors decided that a search engine that could span all the company’s file servers would be more cost-effective. But how many useful results did the staff get from keyword searches? For all the typical reasons – little classification, poor naming conventions, poor security, inappropriate technology – close to none. The content was there but the information wasn’t.

Just as art only becomes art once you place it in a gallery, content only becomes information when you identify it as useful. The quality of the information, like art, is debatable, but it has no chance of being used if you don’t suggest to people that it’s useful information. Following a merger, staff need to know: these are the kind of people who work here and this is what they know about. To find out more, ask them.

Yet even in the most obvious of cases for implementing simple information management tools, their raison d’être can be by-passed. The company in question didn’t implement a networking tool and nearly two years later still doesn’t know some of its clients, the skills of many of its staff or the scope of most of its past projects. Many staff have left. Yet is the company bothered? Absolutely not.

The directors simply changed the strategy. If the sales team weren’t paying attention to certain clients or types of projects, it’s because they weren’t important enough. The strategy dictated that employees focus on bigger and better in their portfolio, as befitted the newly-merged company status. Who needs the past when you have the future?

It’s a bullish policy in a bullish market, but when things inevitably turn bearish, there’ll be a scramble to avoid repeating the mistakes of previous engagements, find people with relevant knowledge, return to reliable clients who weren’t in the big league. By then, both employees and clients could be long gone, and gleaning information from fragmentary content may well prove impossible.

While your work is easy, information has little value. As soon as your work gets tough, it’s the people and companies with the information who’ll profit.

Updated: Alan Pelz-Sharpe has also written about ECM technologies and recession.

Philippe Parker on 27 March 2008

Contented Management

Missing the SharePoint

Let me firstly qualify this post by saying that I’m not inherently anti-Microsoft. I don’t use a Mac, I do use Microsoft Windows (even the mobile version) and Office and I’m using the beta version of Office Live Workspaces. But I just can’t fathom why people choose to use SharePoint.

As a pure document repository it is mostly harmless. It follows Microsoft security models so will only show users documents from file systems and folders they should have access to. Unless you’ve been unbelievably rigorous and consistent in your file naming and metadata conventions, however, its search will be utterly useless. Just search a MOSS intranet for “agenda” if you don’t believe me. The search is also hampered by some strange behaviour when looking at external systems with case sensitive URLs, so try before you buy. No wonder Microsoft have bought Fast.

There are some nice collaboration features: user homepages, instant messaging; but these are bound up in inaccessible HTML. So are the Web Parts, Microsoft’s equivalent of Java-based portlets. This is also true of many Java portals which are heavily dependent on JavaScript functionality and HTML table layouts.

There is a big difference between SharePoint and other portals, however. Java portal technology is built to the JSR standards, notably JSR168. This means that you can take pre-developed portlets and simply expose them through your portal. You can even send these to other portals through WSRP. But not with SharePoint. It doesn’t comply with Java Content Repository standards, so you’ll struggle to put develop a service oriented architecture around it. If you needed a single point of entry for web services that you can develop in .Net, you’d have to look at BEA’s AquaLogic, not SharePoint.

So what is SharePoint for? It doesn’t fit into a service oriented architecture, uses security models from file servers, doesn’t do federated search well and isn’t built to open standards. Do you really want to put that sort of technology at the hub of your organisation?

You can try out SharePoint through the Microsoft Online Customer Portal, although you’ll need a Windows Live ID.

Philippe Parker on , , | 25 March 2008

Contented Management

More enterprise myths

It’s true to say that enterprise is a loaded word: it means a lot more to some than to others. We have enterprise content management (ECM), enterprise search, enterprise portals, enterprise resource planning… People like Nicholas Carr have been railing against these all-encompassing applications for years now, questioning how applications that cost so much to install and configure can deliver tangible business benefit, particularly compared to smaller, more targeted systems. The Gilbane Group on the other hand dislike the term enterprise because they believe it’s pure marketing spiel, particularly in the case of content management where few vendors offer the full range of content management products.

It is of course possible to go to a single supplier and get the full WCM, DM, RM, DAM, JCR and IDM gamut of acronyms. The leaders are IBM and Oracle, but Day, Vignette and Open Text all have products covering the main functionality. You have to take care of course that just because the products are owned by the same company and are labelled as a single product family, this does not mean that they can actually talk to each other. Many is the client persuaded to implement a product portfolio from off the shelf, only to spend months and hundreds of thousands on systems integration.

Leaving aside the truth that vendors relate and the more palpable realities their clients are faced with, ask yourself this: why would you need an enterprise application for content management anyway?

Enterprise means not simply across your whole organisation but unique to your organisation. Your ECM will be different to someone else’s, with different security privileges, workflow, storage and retrieval requirements.

Except it’s not.

What you’re trying to do in your organisation is being attempted in every other organisation of a similar scale or vertical. All your competitors, all your partners, all your suppliers and clients will need to control their information and distribute it to the right people. And they want to do it in similar ways, which is why all these vendors are able to sell their content management technologies to so many clients. The thing is, if your requirements aren’t unique, do you need a system that’s unique?

Of course you don’t.

People like Andrew McAfee and JP Rangaswami have been using and writing about disruptive technologies for years. Technologies like wikis, blogs and tagging are disruptive because they upset standard business models and processes where you procure a single technology and then tell everyone how to use it. Under the disruptive model, you let people use a set of tools the way they find most productive. You can add anything to a wiki without it going through workflow, you use blogs instead of email, you use tags instead of a taxonomy. Depending on where you look, these technologies have been more or less successful.

But for me the issue is that it’s not blogs and wikis that are disruptive, it’s the enterprise technologies themselves. Why do organisations feel the need to procure these tools that few people know how to implement and even fewer know how to use? Why not just pick a few technologies that are out there already? The procurement and implementation of these systems actually disrupts the things your organisation is good at, often having a greater negative impact than the business benefits the system will eventually entail. Yes, an enterprise system gives you one butt to kick, but you still have to do some butt-kicking.
For example, why set up a massive LDAP directory that a bunch of systems administrators need to maintain, when you can use OpenID? If you used this to authenticate people, they can use the same username and password for their social life as their daily business. Isn’t this simpler for everyone? Why set up project team servers? Just let each project team set up a blogger account with a new blog for each project and restrict who can view it. They can use the same email address for their email, calendar, and even documents. And those documents could be shared as a wiki. Some of these technologies will work better than others, and there are of course security implications.

Your organisation does not need to control technology, it needs to exploit it. So before you procure a new CMS ask yourself:

  • Am I trying to do something that is already being done by some of my staff using existing tools?
  • Why can’t I extend those tools to support my business?
  • Do I really want to manage a new supplier, a new project and on-going support?

Isn’t it easier to view web technologies as a facility your enterprise makes use of, like roads or a rail system? Let your employees make their own way to work, don’t go out and buy a bus to round them all up in.

Philippe Parker on , , , , | 20 March 2008

Contented Management